Reference implementation · Planes & primitives
The engineering stack is how empty-channel authorization ships: Foundry, Control, Gate, and Verify planes; circuit binaries; entropy pools; hash streams; and verification harnesses. This page is engineering-facing: link Math and Fundamentals for Shannon, not the other way around.
Integrity tools · authorization thesis
Read the four bands top-to-bottom (Foundry, Control, Gate, Verify) with chips for twin compile, nonce ledger, eight-stage gate, and adversary harness. Side callouts separate computational sealing tools from the empty-channel authorization thesis. Takeaway: the stack ships integrity machinery that makes the Channel Zero claim operable.
Four products, one authorization plane. Foundry mints identity into circuits. Control registers, ledgers, and observes. Gate enforces. Verify attacks your deployment the way an adversary would.
Four authorization planes
Read top-to-bottom through Foundry (mint twins), Control (registry and ledger), Gate (request boundary), and Verify (adversary harness). Each band is a different ops job that ships the same proof family. Takeaway: the product stack separates integrity tooling from the empty-channel authorization thesis.
Manufacturing
Mint identity: compile per-identity circuit binaries into cohort packages that ship licensed and air-gapped. Gates and Control consume those packages for one-shot proofs - not a store of reusable secrets.
Control
Revoke and lifecycle: activate, deactivate, reserve, and burn circuit handles in one registry and durable nonce ledger. Gate consults Control so replay and post-revoke proofs fail under the reference architecture.
Enforcement
Enforce on the request path: proxy, SDK middleware, MCP wrapper, or sidecar runs the same ordered checks - bind the request, spend the nonce, then allow or deny. Per-endpoint policy chooses which routes require a valid envelope.
Assurance
Prove before production: customer-runnable attack suite exercises Gate reject stages - replay, binding mismatch, post-burn reuse - and produces conformance evidence on your deployment.
Full catalog on Products.
Each theme below is an operational property of the system unless noted otherwise.
Timing (τ), embedded seed material, and BLAKE3-XOF streams give engineering integrity, fresh keys, sealed pools, auditable derivations. These are computational sealing tools. They are not, by themselves, the empty-channel authorization claim.
A minimal circuit binary with embedded constants, CLI and self-test harness, and deterministic interfaces. Identity ships as compiled capability, not a password row. Twin compilation details live on Twin circuits.
An AEAD-sealed entropy pool bound to the binary, with integrity failure detection. Starved or tampered entropy voids ceremony assumptions; see Claims for model scope.
Session-ephemeral keystreams for sealing and transport-adjacent crypto. Useful for confidentiality of payloads; orthogonal to whether the authorization transcript carries secret-relevant information.
Notation for freshness and private maps: τ, φ. Entropy pool as a glossary term: entropy pool.
Per-identity binaries, cohort packaging, and air-gap-capable Foundry minting: high level only. No manufacturing step lists. Identity is a compiled twin pair that agrees on membership without exporting a reusable credential on the channel. Deep dive: Identity in twin circuits. See also: How Rosario works.
Eight fixed checks run on every untrusted request before application logic. Stage 5 (burn-before-validate) is why replay dies. Full order lives on Security, not duplicated here.
How a Gate decides
Read the pipeline left-to-right: each Gate stage checks binding, freshness, and burn order before allow. Gold highlights burn-before-validate so replay dies at the ledger, not after crypto. Takeaway: enforcement order is part of the security claim, not a UX detail.
Customer-runnable attack suites exercise reject stages before production traffic does. Why classical families miss the model: Why classical attacks fail. Product: Verify.
Technology Reference explains planes and primitives. Protocol integration, SDKs, and quickstarts live on Developers. Scope on Claims; axioms on Axioms.
Demo UIs teach visually; shipping validation runs against compiled twins; see Claims for model scope.
