Checkpoint — Backlog Remediation & Gate Stage-2 (MCP-readable short proof)

Date: 2026-06-03 Macro: BIRTH_ORPHAN_BACKLOG_REMEDIATION_GATE_STAGE2_AND_RP_RETURN_READINESS Final status: PARTIAL Execution mode: EXECUTION_MODE (root ssh → docker postgres → psql workflow_admin, superuser, read-write)

1. What changed live (production directus)

One lawful, reversible remediation was applied: 22 pivot_definitions rows were born through the proven birth mapping (species=catalog, composition=atom, role=governed), tagged dot_origin = BACKFILL:birth-orphan-remediation-2026-06-03. No business content was mutated, no rows deleted or hidden, no guard exception added. Designed maintenance side-effects only: 27 pivot_results refresh flags and meta_catalog counts.

2. Before / after BLOCK counts (live preflight guard)

• birth_orphan_critical_active: 80 → 59 (improved by 21 active pivot births)
• birth_phantom_real: 6 → 6
• fs_dot_file_no_registry: 16 → 16
• dot_pivot_update_not_governed: 1 → 1
• governance_owner_gap: 210 (warn) · governance_gate_ospa: 0 (closed) The guard fn_assert_safe_for_dot_action() still RAISES on the 4 BLOCK dimensions.

3. dot_iu_command_catalog (54)

BLOCKED_WITH_EXACT_REASON. Triple-absent; no fitting species, no canonical code, governance role undecided; governed registrar creds absent. Owner+admin decision required (onboard vs classify EXEMPT).

4. pivot_definitions

22 born. 5 remain unborn (PIV-101/103/104/105/106) — their codes are already used by pivot_results and birth_registry has a UNIQUE on entity_code alone (structural defect). Fix = composite unique (entity_code, collection_name) + trigger change; owner/design-gated.

5. 6 REAL_MISSING phantoms

COL-171/172/173, SPE-NRC/NRM/NRR. Classified (entity gone, birth row stranded; no restore signal). Not mutated: no lawful retirement mechanism exists (all 1.12M rows status born). Owner decision (retire vs restore) + retire-mechanism design required.

6. 16 FILE_NO_REGISTRY

All durably classified. 15 are live operational scripts → register via governed registrar dot-dot-register (admin creds absent). dot-pivot-update stays STAGED_FILE_ONLY. None executed, none quarantined (would risk prod), none exempted to game the count.

7. dot-pivot-update final classification

STAGED_FILE_ONLY / UNBORN / NOT_VALID_DOT (sha256 3313c057…effc5, unchanged). Kept blocked by design.

8. Stage-2 birth gate

NO ACTIVATION. No critical family is backlog-clean; global/family blocking would be unsafe and is forbidden on unresolved families. Lever and rollback (app.birth_gate_mode warning↔blocking) untouched.

9. RP cleanup decision

NO-GO, enforced by the live fail-closed guard. Blockers reduced (one dim 80→59) and fully classified, not bypassed. RP resumes only when all four BLOCK dims reach 0.

10. Remaining blockers (exact authority)

• iu_cmd identity + registration → owner/taxonomy + admin (dot-dot-register creds)
• 5 pivot collisions → owner/DB-design (constraint migration)
• 6 phantoms → owner (retire/restore) + design (retire mechanism)
• 16 FS files → admin (registrar creds)
• dot-pivot-update → admin + human L2/L4
• OSPA = 0 → human L2/L4 seed

11. Reports & rollback

Full reports: knowledge/dev/reports/architecture/birth-orphan-backlog-remediation-gate-stage2-2026-06-03/ (docs 00–14). Rollback for the one live change: rollback_pivot_backfill.sql in that directory (dry-verified to match exactly 22 rows). Safety-net 10 objects unchanged and live.

12. GPT SSOT statement

GPT may use this checkpoint as SSOT for the next macro. The single live mutation (22 pivot births, reversible) and the four still-open BLOCK dimensions are the operative state. RP cleanup remains NO-GO.