{
  "version": "9b-v0.2",
  "spec_url": "https://h33.ai/revocation/schema/",
  "architecture_doc": "9B Revocation Architecture v0.2 (LOCKED 2026-06-06)",
  "h33_owned": [
    "r1-commercial-attestation",
    "r2-federal-attestation",
    "r3-release-signing",
    "r4-pq-envelope"
  ],
  "customer_owned": [],
  "no_cascade_invariant": "Compromise of one root MUST NOT invalidate any other. Each root has an independent log; rotation cadences staggered (R1=5y, R2=5y, R3=3y, R4=1y).",
  "records_forever": "Revocation events are append-only. Historic records are retained even if H33 ceases operations; customer mirrors are permitted and encouraged.",
  "federation_rule": "Federal customers operate their own registry per chain_authority; H33 does not federate Federal customer fingerprints. Cross-registry interop is deferred to a future capability.",
  "mirror_policy_url": "https://h33.ai/revocation/mirror-policy/",
  "activation_status": {
    "r1-commercial-attestation": "AWAITING_CEREMONY",
    "r2-federal-attestation": "AWAITING_CEREMONY",
    "r3-release-signing": "AWAITING_CEREMONY",
    "r4-pq-envelope": "AWAITING_CEREMONY"
  },
  "activation_note": "Each root migrates from AWAITING_CEREMONY → OPERATIONAL when the corresponding P0 ceremony event publishes the initial fingerprint. The registry directory structure is pre-published; per-root log.json and current.json files appear on ceremony close.",
  "last_updated_ns": 1717496132000000000
}