07 — Future Activation Plan

What a future macro may safely run, in strict order, and what each step is still gated on. Nothing here is run by this mission.

7.1 The staircase (each step gated; none auto-follows)

Step	What runs	Mutation?	Gated on
F-0 (this pkg)	readiness + boundary design	none	— done
F-1 read-only dry-run	Seam-A SELECT expression + gap logic over 3 collections, via query_pg	none	operator go; doc 05 G-1..G-10
F-2 rollback-only dry-run	seam wiring + draft ruleset inside BEGIN..ROLLBACK; verify path	none persisted	F-1 PASS
F-3 rollback rehearsal of seam wiring	CREATE OR REPLACE both seams onto real sources, verify counts bounded, ROLLBACK	none persisted	F-2 PASS; acyclic-screen
F-4 ratified seam wiring (COMMIT)	COMMIT the collection-grain inventory seam	persistent (additive view)	L2+L4 ratification + governance owner sign-off
F-5 small seeded run	seed a draft ruleset + ≤3 owners (test classification), run coverage logic, verify	persistent test seed (justified)	F-4; explicit inert-test-seed authorization
F-6 event-type activation	flip one governance event type active=true	activation	ratification + per-type authorization
F-7 first real emit	emit one coalesced governance event with heartbeat	production activation	F-6; T7 router ready; owner sign-off

Production activation = F-4 onward. Everything ≤ F-3 is reversible/no-persist and is the only thing a near-term macro should attempt.

7.2 What the next macro may run (recommended)

Only F-1 (read-only dry-run), optionally followed by F-2 (rollback-only) if F-1 is clean. These prove the coverage path with zero persistence and zero emit. F-3+ wait for explicit further authorization; F-4+ wait for ratification.

7.3 Required verification at each step

• F-1/F-2/F-3: entry==exit (doc 05 §5.3); counts unchanged; 0 emit; 0 issue; idle_in_transaction=0.
• F-4: post-COMMIT, inventory seam returns the expected bounded row set; gap view correct; os_proposal_approvals still the gate of record; rollback script updated to drop the wiring.
• F-5: seeded rows match the test classification; removable; coverage verdict matches hand-computed expectation.
• F-6/F-7: event registered before active; active before emit; emit coalesced; heartbeat present; no notification storm.

7.4 What no future macro may do without the one gate

Activate event types (F-6), emit (F-7), register/run DOTs, start a background worker, run a full birth_registry sweep, write os_proposal_approvals, or COMMIT any governed act — all remain behind L2 council + L4 sovereign ratification.

7.5 Rollback rehearsal as a first-class future step

Before any COMMIT (F-4), a dedicated rollback rehearsal (F-3) must prove the inert-restore path: wire the seams in a transaction, verify, then confirm ROLLBACK returns them to WHERE false and all counts to baseline. This is the same discipline that produced the accepted substrate.

7.6 Future activation plan verdict

ACTIONABLE. A 7-step staircase with explicit per-step gates; the near-term macro is bounded to F-1 (read-only) ± F-2 (rollback-only); production activation (F-4+) is firmly behind the unsolved ratification gate; each step has named verification and a rollback rehearsal precedes the first COMMIT.