Architecture

Freebird is organized around a client, an issuer, and a verifier. The client blinds and finalizes; the issuer applies admission policy and signs/evaluates; the verifier validates and consumes replay state.

• Protocol overview — implemented V4 and V7 paths.
• Trust boundaries — service, metadata, admin, and storage boundaries.
• Data flow — request and redemption sequence.
• Storage model — keys, registries, Redis, and local state.
• Deployment modes — development and production topology.

The older architecture summary remains a useful cross-reference. Security goals, assumptions, and non-goals are authoritative in the threat model; operational requirements are in the production deployment guide.