13 — Final Summary

Status: PARTIAL — Execution mode: EXECUTION_MODE

This macro moved the system from "alarm system installed" to "alarms being cleared lawfully." The one alarm that could be cleared without fabricating data, inventing a mechanism, or using missing credentials was cleared; the rest are precisely classified and routed to the exact owner/admin/design authority that can clear them.

What changed live (production directus)

• 22 pivot_definitions birth rows created (PIV-001..019, 020, 021, 102) via the proven fn_birth_registry_auto('code') mapping (species=catalog, comp=atom, role=governed), tagged dot_origin='BACKFILL:birth-orphan-remediation-2026-06-03'. Reversible (doc 11).
• birth_orphan_critical_active: 80 → 59.
• Designed maintenance side-effects only: 27 pivot_results.needs_refresh, meta_catalog counts.
• No business CONTENT mutated. No deletes. No hidden rows. No guard exceptions added.

What stayed report-only (with exact, evidenced reasons)

Workstream	Outcome	Why
A dot_iu_command_catalog	BLOCKED_WITH_EXACT_REASON	identity undecidable (no species/role/canonical code) + registrar creds absent
B pivot_definitions	22 born; 5 collision-blocked	structural: birth_registry unique on entity_code alone vs pivot_results
C 6 REAL_MISSING	classified; not mutated	no lawful retirement mechanism exists; retire-vs-restore = owner
D 16 FILE_NO_REGISTRY	all classified; not mutated	governed registrar creds absent; live tools (no blind quarantine)
E dot-pivot-update	stays blocked	full lawful path incomplete (by design)
F gov bridge / OSPA	OSPA human-gated; bridge deferred	ospa=0; naive row-bridge = ~6.7M noise gaps
G Stage-2 gate	no activation	no family clean; forbidden on unresolved backlog
H preflight	NO-GO (4 BLOCK)	guard fails closed; not overridden

New findings this macro

1. birth_registry global-unique-on-entity_code defect prevents birthing 5 pivots whose codes are shared with pivot_results. Fix = composite unique + trigger ON CONFLICT change (owner/design).
2. No birth-retirement mechanism exists (all 1.12M rows status born; no retire function/convention) — so the 6 phantoms cannot be lawfully retired until one is designed.

Completion-contract check

• Live safety-net checkpoint read & confirmed ✅
• All live checks done ✅
• All 4 BLOCK dims remediated-or-classified with row/file-level evidence ✅
• iu_cmd lawful status ✅ (BLOCKED + packet) · pivots durable status ✅ · 6 phantoms durable ✅ · 16 files durable ✅ · dot-pivot-update stays blocked ✅
• Stage-2 readiness explicit ✅ · preflight before/after recorded ✅ · RP decision explicit (NO-GO) ✅
• PARTIAL because credential/owner/design approvals block the remaining live remediation; all safe branches completed; every remaining blocker has an exact owner/action.