11 — GO/NO-GO: Return to RP Cleanup

Decision: NO-GO (RP cleanup remains paused)

The minimum safety net is fully authored with exact apply/rollback + operator handoff, but none of it is live (Agent channel is read-only; no DDL/filesystem write). Per the macro's strategic intent — "do not return to RP until this minimum safety net exists OR is fully packaged with exact operator handoff" — the package condition is met, but the safety net is not yet operational, and two activation steps require external authority.

What must be true before RP GO

Gate	Status	Owner action
P1 detector views live (v_birth_orphan/phantom/coverage_status)	authored, not applied	apply sql/01_detector_views.sql (safe, read-only, instant rollback)
P2 filesystem snapshot loaded + reconciled	authored, snapshot uncollected (channel-blocked)	run collect_dot_bin_inventory.sh, apply sql/02_filesystem_reconciler.sql
P6 preflight guard live + returns clean for criticals	authored, not applied	apply sql/06_preflight_guard.sql; fn_assert_safe_for_dot_action() must not raise
P4 backlog triaged (26 pivot, 54 iu, 82 zero-birth)	ledger authored	run fn_backfill_scan(), decide each row
dot-pivot-update reaches GOVERNED_READY	classified NOT_VALID_DOT	register via governed registrar (admin creds), birth, onboard (ospa≥1)
Governance gate OPEN (ospa ≥ 1)	CLOSED	human L2/L4 ratification

Blockers (with the exact missing authority)

1. No DDL/filesystem write channel for the Agent → all apply steps are operator handoff.
2. Admin creds absent → cannot register dot-pivot-update via the governed registrar (same blocker the prior RP macro hit).
3. ospa = 0 (governance gate CLOSED) → row-level governance onboarding cannot complete; needs human L2/L4 (ospa ≥ 1).
4. Legacy backlog unclassified → Stage-2 birth-gate blocking must stay off until P4 triage done.

Minimum-viable GO path (fastest safe)

Apply P1 + P2 + P6 (all read-only / dedicated staging — safe, reversible), load the FS snapshot, confirm fn_assert_safe_for_dot_action() is clean for critical families (synthetic phantoms accepted), and treat governance onboarding (P5) + gate Stage-2 (P3) as follow-on tracks. At that point RP read/classification work can resume under preflight; RP mutation still waits on creds + ospa.