06 — Minimal Blocker Closure Plan

Smallest next action, not the backlog. RP cleanup reduces to ONE external-authority blocker; RP/IU resume reduces to ZERO blockers.

Blocker R0 (only one for RP cleanup) — register/birth dot-pivot-update

• What: lawfully register+birth the already-authored, rollback-proven dot-pivot-update, then run its dry-run→--commit path to fix the 3 composition mismatches.
• Owner: operator/admin holding dot-dot-register (Directus-API) credentials.
• Evidence it's the only RP blocker: doc 02 (other 3 dims non-RP); doc 04 (no substitute); doc 01 (3 targets born).
• Tool: dot-dot-register → governed dot_tools row + birth → dot-pivot-update --auto-from-species (dry-run) → --commit.
• Guard before: dot_pivot_update_not_governed=1 BLOCK; fs_dot_file_no_registry=16.
• Guard after register/birth: dot_pivot_update_not_governed→0; fs→15. (orphan/phantom unchanged — non-RP.)
• Rollback: registration reversible (governed retire); composition --commit has authored BEGIN…ROLLBACK rehearsal + rollback proven.

Non-RP global-hygiene items (do NOT reopen for RP)

54 dot_iu_command_catalog → owner taxonomy + creds. 5 pivot collisions → owner + composite-unique design (one-way door). 6 phantoms → owner retire/restore + retire mechanism. 15 non-cleanup FS scripts → registrar creds. OSPA=0 → human L2/L4 seed.

RP/IU resume — zero-blocker path (Path 3)

Resume miếng-thông-tin work on the live v_rp_classification_governance_map. No credential, approval, or mutation required. Guard impact: none. Rollback: n/a (read-only).

One-line summary

Smallest blocker for RP cleanup = one credential (dot-dot-register). Smallest blocker for RP/IU resume = none.