ZAPTM: Zero Trust AI-Managed PQC
A post-quantum migration is not one cryptographic step: it is key generation, distribution, verification, rotation, revocation, and audit, forever. ZAP orchestrates that lifecycle into one governed workflow so the operational burden does not fall on people doing it by hand.
One governed workflow
What each step does
Generate a key pair
ZAP generates a lattice key pair with hedged signing and runs a FIPS 140-3 pairwise-consistency test. A pair that fails the test is withheld, not shipped. The honest error is “keypair withheld,” not “retry.”
POST /api/keypair/generate
→ { "status": "ok", "kem_fingerprint": "e12909c9306d8cff",
"dsa_fingerprint": "675dd26f85a653d3" } // sample fingerprints, illustrativeDistribute the public key
The public key is published to a locator service and shared with named recipients. The private key never leaves the node that generated it.
POST /api/keypair/upload { "recipients": ["team@group.local"] }
→ { "locator": "qre7b5ylN4RTs4wAXthNTS8OO4VCKkdyJqC8ANiXDDo" } // sample locatorVerify before trust
Every signature is checked with verify-after-sign before it is relied upon; recipients verify first. A mismatch surfaces at the AEAD tag, not as a decryption oracle.
Audit continuously
Generation, rotation, and revocation are recorded in a hash-chained, signed log so the compliance posture is provable rather than asserted.
Live console
A live ZAP console connects to a running key-management node. In this public demonstration the controls are shown as disabled affordances. This page does not generate or manage real keys.