Canonical state
Core determines ECZ-ID state. Website copy, a copied badge or a cached JSON file is not canonical truth.
LONG-LIVED EVIDENCE & CRYPTOGRAPHIC AGILITY
DESIGN EVIDENCE SO SECURITY CAN EVOLVE WITHOUT REWRITING ACCOUNTABILITY.
Long-lived machine evidence may need to survive changes in algorithms, platforms and cryptographic standards. ECZ-ID separates canonical state, integrity metadata and re-verification so the security mechanisms around evidence can evolve without pretending a current website page proves a particular future cryptographic implementation.
CURRENT CLAIM BOUNDARY
Cryptographic agility is the design principle. Specific post-quantum deployment claims require implementation evidence.
This page deliberately does not claim that ECZ-ID currently signs every record with post-quantum algorithms, that quantum computing makes trust decisions, or that cryptographic integrity certifies the truth of an underlying real-world assertion.
Integrity
Hashes, anchors, signatures and retention mechanisms can protect recorded evidence integrity. Integrity does not automatically establish the truth of every source assertion.
Agility
Evidence formats should allow cryptographic mechanisms and standards to evolve without changing the accountability meaning of Identity, Authority, Intent, Decision, Receipt and Re-check.
Re-verification
Current public proof belongs in Resolver and should be re-checked at the time of reliance rather than treated as permanently valid.
Resolver ↗FUTURE-RESILIENT, NOT FUTURE-PRETENDING
Preserve the security objective without overclaiming the implementation.
ECZ-ID can evolve its cryptographic and ledger mechanisms as standards and threat models change. A specific algorithm, signature mode or post-quantum deployment should only be described as live when production evidence supports that claim.