Proof and documentation

ZAP: Zero Trust AI-Managed PQC Seal (Lifecycle Walkthrough)

What the ZAP key-lifecycle workflow governs, the standardized algorithms it uses, the assurance practices it follows, and the honest limits of this static walkthrough.

Open the live demonstration

DEMONSTRATION. This is a walkthrough of the ZAP workflow. The on-page controls are illustrative affordances, not a live key-management console, and any fingerprints or locators shown are SAMPLE values, not live credentials. This content is drafted for a client-facing proof and has passed the publishability firewall (NOUS, 2026-10-27).

What it is

ZAP is a governed workflow that manages the full life of post-quantum keys: generate, distribute, verify, rotate, revoke, and audit. The demonstration page walks through that lifecycle one step at a time so a reader can see what each stage does and where the Zero Trust policy gate sits. The live console that performs these actions runs inside an authenticated enclave, not in this public page; here the controls are shown as disabled affordances and the page generates or manages no real keys.

What this proves to you (plain English)

Moving to post-quantum cryptography is not a single switch you flip once. It is key generation, distribution, verification, rotation, revocation, and audit, repeated for every identity, forever. The operational burden of doing that by hand is where real deployments break down. ZAP's point is that this entire lifecycle is one governed, automated workflow with an audit trail, so the day-to-day work does not fall on people and the compliance posture can be shown rather than asserted. This page proves the shape of that workflow and the governance model; it does not perform live key operations in your browser, and it is explicit about that.

Standards and parameter set

  • Key establishment: ML-KEM-1024, NIST FIPS 203, security category 5. Encapsulation key and ciphertext 1,568 bytes each, shared secret 32 bytes. FACT (FIPS 203).
  • Digital signatures: ML-DSA (CRYSTALS-Dilithium), NIST FIPS 204. FACT.
  • Symmetric layer: AES-256-GCM; hashing with the SHA-3 / SHAKE family, FIPS 202. FACT.
  • Assurance practices referenced: FIPS 140-3 pairwise consistency test on key generation, and FIPS 203 implicit rejection on decapsulation. FACT (named standards).
  • Context: NIST standardized ML-KEM (FIPS 203) and ML-DSA (FIPS 204) in August 2024. Federal post-quantum migration is directed under EO 14412 and OMB M-26-15. FACT (public record).

Correctness evidence (concrete, verifiable)

What the walkthrough asserts about the ZAP stack, graded honestly. These describe the governed stack ZAP manages; they are NOT cryptographic operations performed in this static page.

  • Generate with a self-check: key generation runs a FIPS 140-3 pairwise consistency test, and a pair that fails the test is WITHHELD, not shipped. The honest error is "keypair withheld," not "retry." INFERENCE (describes the ZAP stack per our internal build records; not executed on this page). The FIPS 140-3 pairwise consistency requirement is itself a FACT (named standard).
  • Distribute without exposing the secret: the public key is published to a locator and shared with named recipients; the private key never leaves the node that generated it. INFERENCE (stack design; not executed on this page).
  • Verify before trust: every signature is checked before it is relied upon (verify after sign), and recipients verify first. INFERENCE (stack design; not executed on this page).
  • No decryption oracle: a bad ciphertext is not reported as an explicit decryption failure. Under FIPS 203 implicit rejection, decapsulation of an invalid ciphertext returns a pseudorandom secret, and any mismatch surfaces one layer up at the AEAD authentication tag. This removes the decryption-failure oracle that an explicit reject would create. FACT (FIPS 203 implicit rejection is standards-correct behavior); INFERENCE that the ZAP stack preserves it (per our internal build records).
  • Audit continuously: generation, rotation, and revocation are written to a hash-chained, signed log so the compliance posture is provable rather than asserted. INFERENCE (stack design; not executed on this page).

Honesty caveats stated plainly:

  • This page performs NO live cryptography. There is no byte-identical round-trip, no verify = TRUE / tamper = FALSE result, and no NIST Known-Answer-Test comparison on this page. The claims above are architectural descriptions of the enclave stack, not results computed in the browser.
  • The controls (generate, upload, view audit log) are intentionally disabled affordances. Real key operations run inside the enclave on an authenticated node under an XQ Zero Trust policy gate.
  • Any fingerprints or locators displayed are SAMPLE, illustrative values, not live credentials.

Measured performance

Omitted. This demonstration does not report measured timing, throughput, or transport-overhead numbers, so none are claimed here.

Client FAQ

1. Does this page manage real keys? No. It is a walkthrough. The controls are disabled affordances and the page generates no real keys. Real operations run inside an authenticated enclave under a Zero Trust policy gate.

2. Why is ZAP a workflow and not a single tool? Because a post-quantum migration is a lifecycle: generate, distribute, verify, rotate, revoke, and audit, for every identity, continuously. ZAP automates and governs that whole loop so the operational burden does not fall on people by hand.

3. What happens if a bad key pair is generated? It is withheld. Key generation runs a FIPS 140-3 pairwise consistency test, and a pair that fails is not shipped. The honest signal is "keypair withheld," not a silent retry.

4. What stops an attacker from probing decryption errors? The design follows FIPS 203 implicit rejection: an invalid ciphertext yields a pseudorandom secret rather than an explicit decryption-failure message, and any mismatch is caught at the AEAD authentication tag. That removes the decryption-failure oracle.

5. Where does the private key live? On the node that generated it. Only the public key is distributed, by a locator, to named recipients. The private key does not leave its node.

6. How is compliance demonstrated rather than claimed? Generation, rotation, and revocation are recorded in a hash-chained, signed audit log, so the posture can be shown and checked rather than taken on assertion.

See it run

This documentation stands behind a live demonstration.