07 — Rollback Plan

Nothing was committed this run, so there is nothing to roll back now. The rollback path is nonetheless staged and proven for the authorized commit.

Rollback artifact

sql/rollback_f6_ownership_seed.sql — DELETE FROM governance_object_ownership WHERE created_by='F6_OWNERSHIP_SEED_COMMIT';

Why it is safe and exact

• governance_object_ownership has 0 triggers (verified live this run) → DELETE causes no cascade, no event emit, no system_issues write.
• The seed is tagged with a unique created_by key → the DELETE targets exactly the 30 seed rows and nothing else.
• Idempotent: if the seed was never committed (current state), the DELETE removes 0 rows and leaves baseline (gap 210) intact.
• Self-asserting: the script verifies 0 seed rows remain post-delete.

Reversibility ledger

State	ownership	gap	how to reach
Baseline (now)	0	210	current
Seeded (post authorized commit)	30	0	commit_ready_f6_ownership_seed.sql (gated)
Reverted	0	210	rollback_f6_ownership_seed.sql

Rollback readiness: STAGED and PROVEN-REVERSIBLE.