ROOT0 / PERSIST CORTEX / CRYPTOGRAPHIC MEMORY

12 · KEY LIFECYCLE DIODE

ACTIVATE → ROTATE / REVOKE · independent witnesses · immutable history

THE NEXT SECURITY BOUNDARY

                         PAST                      PRESENT                        FUTURE
                         observes                   deserves                       reserves
                            |                          |                              |
WITNESS A                  [A0] ───────────────→ [A1] ─────────────────────────→ [A2]
WITNESS B                  [B0] ───────────────→ [B1] ─────────────────────────→ [B2]
WITNESS C                  [C0] ───────────────→ [C1] ─────────────────────────→ [C2]

KEY LIFECYCLE       ACTIVATE(key1) → ROTATE(key1→key2) → ... / REVOKE(keyN)
                                                        |
                                              previous signatures preserved

RECEIVER 0ROOT     PIN(key1) → BLOCK(key1)           (independent Git append)
                                                        |
                                   Old signatures still replay. New receipts denied.

                          ONE WAY.  APPEND ONLY.  THREE INDEPENDENT WITNESSES.
                                        NO VOTE.  NO QUORUM.

Rotation needs detached signatures from BOTH the old and incoming Ed25519 keys, plus an authenticated GitHub actor. Emergency revocation is explicitly labeled an account-authorized recovery decision, not a forged signature from the lost key. Key history is append-only and old signatures remain historically verifiable.

TOPH · SOURCE KEY-LIFECYCLE VERIFICATION

Public key registryLOADING
Key lifecycle SHA chainLOADING
Historical events0
Current lifecycle tipGENESIS
Active independent witness keys0

Witness lanes

A
UNASSIGNED KEY
B
UNASSIGNED KEY
C
UNASSIGNED KEY

0ROOT.AI · INDEPENDENT RECEIVER POLICY

Separate pinned public keysLOADING
Permanent key BLOCK journalLOADING
Keys blocked for future receipts0
Independent history tipGENESIS

Independent BLOCK decisions in the Hallway do not rewrite TOPH or historical 0root checkpoint receipts. Until a receiver key is separately pinned, it cannot admit signed checkpoints. Revocation is not a vote or a retrospective deletion.

Verification boundary

TOPH: new checkpoint must use an ACTIVE key.
0ROOT: new anchor must use a PINNED key
       and must NOT be independently BLOCKED.

Existing anchors continue to verify with retained
historical pins, including rotated/revoked keys.

A/B/C report independently. No quorum.

KEY EVENT HISTORY

No key changes recorded.

INDEPENDENT BLOCK HISTORY

No blocked keys recorded.

MANUAL, AUTHENTICATED OPERATIONS

Read Gate 12 operating and incident recovery protocol · TOPH key lifecycle append workflow · Hallway independently blocked key workflow.

TOPH immutable key history · Hallway independent key BLOCK history · Gate 11 distributed checkpoint receipts.

All operations require explicit authenticated GitHub Actions dispatch. These public HTML files never receive a private signing key, GitHub token, or private memory. Source commits are not proof that the manual workflows have run successfully.