00 — README FIRST

Macro: REGISTRIES_PIVOT_DOT_PIVOT_UPDATE_AUTHOR_REGISTER_CLEANUP_AND_UI_HANDOFF Date: 2026-06-03 · Prod DB: directus · Prod mutations: 0 (byte-identical entry==exit)

One-paragraph result

The blocker the previous macro surfaced — no DOT tool could update classification fields on an existing pivot_definitions row — is RESOLVED. A new governed DOT tool, dot-pivot-update, was authored to the conventions of the live DOT framework, deployed to /opt/incomex/dot/bin/, and proven end-to-end on production via BEGIN..ROLLBACK: the 3 deterministic composition fixes (PIV-001/016/021) each drive the mapping view from mismatch → match, committing nothing. A bug found during rehearsal (inactive-row guard) was fixed and re-verified. The actual commit is HELD because the governed registration path (dot-dot-register, Directus-API) requires admin credentials absent from this environment — a real access blocker. Production pivot_definitions fingerprint is identical at entry and exit: 70d6df05501a7de91e24b848168c5b03.

Verdict: PARTIAL (tool built + proven; commit + registration staged for credentialed operator)

Objective	Result
A — author dot-pivot-update	✅ done, deployed, proven
B — registration	⏸ staged (creds absent — governed path is dot-dot-register)
C — clone/rollback rehearsal	✅ done on prod via BEGIN..ROLLBACK (0 mutations)
D — deterministic cleanup	⏸ HELD pending registration; commit is a 1-command operator step
E — naming/retire packets	✅ 12 naming (council) + 2 retire (already inactive)
F — anti-drift suite	✅ live-validated; v_rp_classification_health paste-ready
G — UI/API handoff	✅ contract + badges + L2 banner + JSON
H — RP roadmap	✅

Read order

01 state+preflight · 02 tool design · 03 registration · 04 rehearsal · 05 cleanup execute/hold · 06 naming+retire · 07 anti-drift · 08 UI/API · 09 roadmap · 10 go/nogo · 11 self-review.

The single remaining blocker

Directus admin credentials (for dot-dot-register) are not in this agent's environment. With them, an operator runs two commands (dot-dot-register then apply_composition_fixes.sh --commit) to register the tool and apply the 3 fixes. See artifacts/register_and_commit_packet.sh. No L2 Governance rollout is involved — RP classification needs no L2; the L2 gate remains CLOSED and out of scope.

Forbidden compliance: FULL

No manual UPDATE; no direct INSERT/DELETE on pivot_definitions; no L2 rollout; no event/system_issues/os_proposal writes; no UI/Nuxt/Directus/Qdrant mutation; no law/version change; no manual dot_tools INSERT (governed path only); no naming auto-ratification; no governance island; no gap=0 claim; no clone-as-prod.