background gif
eni6ma

Reference implementation · Planes & primitives

Engineering stack

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 planes

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

ENI6MA Foundry

The minting appliance. Compiles per-identity circuit binaries into cohort zips (licensed, air-gappable).

  • · Cohort production
  • · Per-identity binaries
  • · Air-gap capable

Control

ENI6MA Control

Registry, durable nonce ledger, and visibility. Activate, revoke, reserve, burn (the control plane Gate consults).

  • · Circuit registry
  • · Nonce ledger
  • · Burn and access logs

Enforcement

ENI6MA Gate

The flagship. Proxy, SDK middleware, MCP wrapper, and sidecar form factors that enforce the eight-stage order.

  • · Per-endpoint policy
  • · Burn-before-validate
  • · Request-bound envelopes

Assurance

ENI6MA Verify

Customer-runnable attack suite. Exercises the Gate the way an adversary would (before production traffic does).

  • · Adversary harness
  • · Reject-stage coverage
  • · Conformance evidence

Full catalog on Products.

Core architecture themes

Each theme below is an operational property of the system unless noted otherwise.

Cryptographic pipeline

operational

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.

ENI6MA.CIRCUIT binary

operational

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.

Entropy pool manager

operational

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.

Two-way hash stream

operational

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.

Twin compilation & cohorts

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.

Gate enforcement touchpoint

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.

Security · Gate product

Verify / adversary harness

Customer-runnable attack suites exercise reject stages before production traffic does. Why classical families miss the model: Why classical attacks fail. Product: Verify.

Developers door

Technology Reference explains planes and primitives. Protocol integration, SDKs, and quickstarts live on Developers. Absolute claims stay model-scoped on Claims; axioms on Axioms.

Demo UIs teach visually; shipping validation runs against compiled twins; see Claims for model scope.