09 — Next Registries-Pivot Prompt

Date: 2026-06-03. This is the exact prompt to resume the Registries-Pivot workstream. It is the first RP macro (M1 / P0) from design doc 13. It is design/rehearsal-first, BEGIN..ROLLBACK, no commit, no production governance dependency.

Preconditions

• RG1 (human ratifies RP Master Design v0.1) should be in place; if not yet ratified, run M1 as a pure read-only rehearsal labeled "pre-RG1 dry run" and do not present results as accepted.
• This macro is gated by RG, NOT by the governance ospa gate — it can proceed independently of the governance production rollout.
• Read this handoff package (docs 00–08) FIRST.

Paste verbatim into a fresh Agent session

MISSION: REGISTRIES_PIVOT_COUNT_INTEGRITY_READONLY_REHEARSAL

Effort: xhigh. Mode: READ-ONLY rehearsal. No COMMIT. No production mutation.

Context / resume:
- Read the governance->registries-pivot handoff FIRST:
  knowledge/dev/reports/architecture/one-roof-governance-to-registries-pivot-final-handoff-2026-06-03/
  (esp. 04-forbidden-assumptions: clone-proven != production-live).
- Registries-Pivot source of truth (design v0.1):
  knowledge/dev/design/registries-pivot-os-agency/ (docs 00-13).
- Target reference numbers: doc 05 (pivot-only counting + accounting invariant; the live FAILED rehearsal) and doc 13 (M1 spec).
- Standing constraints: no-hardcode; every count pivot-backed or PIVOT_MISSING; additive + BEGIN..ROLLBACK + soft-retire; live verification beats old report.

GATE0 (before deep work):
1. Confirm production live state read-only: query_pg(database=directus) -> note ospa, gap, axis/topic absence. Do not depend on any gated/clone interface.
2. Confirm the clone/psql BEGIN..ROLLBACK probe channel works for the rehearsal (ssh contabo -> docker psql role), OR run the rehearsal as a read-only SELECT-only construction if no rollback sandbox is available. Never COMMIT.

GOAL:
- Stand up v_count_integrity over the LEAF set as a BEGIN..ROLLBACK read-only rehearsal.
- Prove it reproduces doc-05 numbers (drift_rows, phantom-side, orphan-side, net_gap) and never blind-SUMs rollup rows.
- Every count must be pivot-backed (pivot_count/pivot_query) or explicitly PIVOT_MISSING.

EVIDENCE:
- Rehearsal SELECT output == doc-05 table.
- ROLLBACK clean (entry == exit; prove with before/after counts).
- A short report to KB: numbers reproduced, any drift vs doc-05 explained, PIVOT_MISSING cells listed.

FORBIDDEN:
- COMMIT; any write to meta_catalog / system_issues / event_outbox; Nuxt change; any count not pivot-backed.
- Treating clone evidence as production truth; depending on governance ospa-gated features.
- Production/clone mutation; DOT/UI/Directus/Qdrant mutation; approval/law/version change.

COMPLETION:
- PASS = v_count_integrity reproduces doc-05, rollback clean, report published, no forbidden action.
- PARTIAL = blocker stated exactly.

NEXT AFTER M1: M2 REGISTRIES_PIVOT_ADDITIVE_SCHEMA_AND_PIVOTS_DRESS_REHEARSAL (after M1 + Dieu32 packet).

Why M1 is the right resume point

• It is the lowest-risk RP step (read-only rehearsal), re-establishes the count-integrity ground truth that everything else (M2 schema, M2.5 API, M4 UI, M6 implement) builds on, and is independent of the governance production gate.
• It satisfies RG2 (count-integrity rehearsal accepted) on the RP readiness gate path.

RP roadmap reminder (doc 13)

RG1 (ratify) → M1 → M2 (+Điều32) → M2.5 → M3 (council) → M4 (UI preview) ∥ M5 (pin) → M6 (implement, after all RG) → M7 (notification/cleanup). DEFER: ghost detection (Qdrant), IU/KG pivots.