00 — README First

Macro: REGISTRIES_PIVOT_RETURN_MINIMAL_GUARD_CLOSURE Date: 2026-06-03 Final status: PARTIAL → RP_BLOCKED_MINIMAL (RP cleanup) + Path 3 no-mutation resume available (RP/IU work) Execution mode: read-only verification (query_pg, prod directus); cleanup path = BLOCKED_EXTERNAL_AUTHORITY Live mutation: NONE.

What this macro was and was not

This was not an infrastructure build. Per owner direction, the pre-birth permit system and the dot_tools enforcement pilot are now owner-gated future work, not the next execution priority. This macro answered one question: what is the minimum lawful path back to Registries-Pivot cleanup, without weakening the safety net or pretending the platform is clean?

Headline conclusion

1. The global guard's 4 BLOCK dimensions are mostly NOT RP blockers. Of the 59 orphans, 54 are dot_iu_command_catalog (different family, untouched by RP cleanup); the 6 phantoms are collection_registry/entity_species codes; 14 of 16 FS files are unrelated ops scripts. The only RP-cleanup-relevant blocker is the tool itself — dot-pivot-update is UNBORN / NOT_VALID_DOT.
2. The 3 RP cleanup targets (PIV-001, PIV-016, PIV-021) are already BORN and governance-attached. They are NOT among the 59 orphans. The 5 unborn pivots (PIV-101..106) are a separate birth-collision problem, not cleanup targets.
3. No substitute tool exists. No registered/born pivot or matrix DOT can update composition_level/species/registry_group on an existing pivot_definitions row.
4. RP cleanup (the 3 composition fixes) is BLOCKED on one external authority — registrar credentials to lawfully register/birth dot-pivot-update. Smallest blocker.
5. RP/IU ("miếng thông tin") work can resume now via Path 3 — the live classification view surfaces truth; the 3 mismatches are flagged-but-non-blocking accuracy items.

Document map

00 readme · 01 live state + checkpoint confirmation · 02 global vs RP-specific risk · 03 RP-scoped guard (paste-ready, not applied) · 04 dot-pivot-update vs tool path · 05 RP state + mutation need · 06 minimal blocker closure · 07 return-to-RP packet · 08 next macro/handoff · 09 final summary · 10 GPT MCP-readable checkpoint.

Hard guarantees honored

Global guard fn_assert_safe_for_dot_action not weakened; no accepted exception added; dot-pivot-update not executed/registered/called valid; no manual psql RP UPDATE; no pre-birth permit applied; no birth-gate flip; no birth_registry constraint change; no OSPA fakery; prod left byte-identical.