Rollback Plan — TKT-OBJ-225..441 Governance Fold

Trigger

Any post-fold verification failure, or owner/GPT instruction to revert.

Backups (pre-fold, byte-exact)

• registry JSON: sha256 54a950b3344646ad5fdd44b51c3837403c25b9a9da0fc98a2b8ccd8e283b15cb (rev20)
• registry MD: sha256 f2e19a073c3aa274274ffc6dd4ddc053452fb263c761f97999ada47319619f4b (rev22)
• 00-index: sha256 6d3b22a13caccd82856c052b72c6aece5e6fa6499151ce0af5f63e41af5ca181 (rev114)

Method A — restore backup (authoritative)

update_document each canonical path with the pre-fold backup content. Re-fetch and confirm sha256 equals the pre-fold pin above. This returns the registry to its exact rev20/22/114 content (KB revision counter advances, content reverts).

Method B — reverse patch (equivalent, proven)

Apply each fold patch in reverse (new_str → old_str), in reverse order. Simulation in rollback-evidence.json shows this reproduces the pre-fold content byte-exact for all 3 files.

Safety

Rollback touches ONLY the 3 canonical governance files. No production, no implementation execution, no REAL_RUN/QT001/cutover. Source addenda and all T1/T2/Codex artifacts are untouched either way.