01 — Live State & Checkpoint Confirmation

All figures read live from prod directus via query_pg (read-only), 2026-06-03.

1. Safety-net objects — all LIVE (10 + RP view)

Detectors v_birth_orphan, v_birth_phantom, v_birth_coverage_status; reconciliation _recon_dot_fs_inventory, v_dot_fs_reconciliation, v_dot_registry_no_file, v_dot_pivot_update_status; guard _preflight_accepted_exceptions, fn_preflight_guard(), fn_assert_safe_for_dot_action(); RP v_rp_classification_governance_map. Both guard functions exist, no-arg.

2. fn_preflight_guard() live output

• birth_orphan_critical_active 59 critical BLOCK
• birth_phantom_real 6 high BLOCK
• birth_phantom_investigate 0 medium WARN
• fs_dot_file_no_registry 16 high BLOCK
• fs_snapshot_present 287 high PASS
• dot_pivot_update_not_governed 1 high BLOCK
• governance_owner_gap 210 medium WARN
• governance_gate_ospa 0 info CLOSED

4 BLOCK dimensions — identical to all three prior checkpoints. No drift.

3. Orphan breakdown (v_birth_orphan)

• dot_iu_command_catalog 54 (NOT RP family; free-text command names)
• pivot_definitions 5 (PIV-101,103,104,105,106 — unborn, entity_code collision) critical_family = {dot_tools, pivot_definitions, dot_iu_command_catalog}; reason NO_BIRTH_ROW.

4. RP cleanup targets vs collisions (disjoint sets)

PIV-001 molecule→atom (BORN, target) · PIV-016 atom→meta (BORN, target) · PIV-021 atom→molecule (BORN, target). PIV-101/103/104/105/106 unborn (collision, NOT targets). The cleanup targets all have birth rows; fixing them does not require birthing PIV-101..106.

5. dot-pivot-update (v_dot_pivot_update_status)

on_disk true · sha256 3313c057…effc5 (unchanged) · in_registry false · born false · STAGED_FILE_ONLY / UNBORN / NOT_VALID_DOT.

6. Conclusion

Live state == checkpoint state exactly. No mutation since last macro. Accepted current state in the macro brief is confirmed true against live prod.