KB-240D
C1 W7 pre-apply — 09 after snapshot (before==after) + rollback 2026-06-23
2 min read Revision 1
c1w7after-snapshotbefore-equals-afterrollbackb5
09 — B5 · After Snapshot + Rollback
After snapshot (governed RO query_pg, db=directus, re-queried this run)
| Metric | Before | After | Δ |
|---|---|---|---|
| apr_action_types total | 14 | 14 | 0 |
| apr_action_types unimplemented | 10 | 10 | 0 |
| authorize_build_step.handler_ref | unimplemented | unimplemented | none |
| governance_build_authorization | 0 | 0 | 0 |
| approval_requests total | 230 | 230 | 0 |
| approval_requests (authorize_build_step) | 0 | 0 | 0 |
| dot_tools total | 309 | 309 | 0 |
| dot_tools dot-c1-* | 0 | 0 | 0 |
| dot_agent_api_contract | 2 | 2 | 0 |
| table_registry | 21 | 21 | 0 |
| directus_collections | 164 | 164 | 0 |
before == after for all 11 governed metrics. Every delta = 0 and expected (zero mutations).
Rollback
- Governance DB: nothing to roll back — 0 mutations.
- VPS filesystem: nothing to roll back — 0 writes to
/opt/incomex. - KB: the only writes were evidence documents (preflight package + this Phase C package). These are evidence-zone records, not governance state; if retraction is desired, delete the documents under the two report paths. They do not affect production.
Rollback plan for a FUTURE governed apply (reference, not executed)
- Handler deploy:
patch_ops_codekeeps.bak-{session}; restore via atomicmvof the backup. handler_refbinding: paired migrationdown(reset tounimplemented).dot-c1-grant-issue: DOT retire/rollback via the DOT lifecycle (dot-rollbackfamily / DOT-062), removing thedot_tools/catalog row.
B5: before == after confirmed.