07 — Next Paste-Ready Prompts

The concept patch is applied. The next tiers are each gated by a named blocker. Six self-contained prompts; each begins with state recovery + Hard Gate 0 and carries its own forbidden list. Default next step = Prompt 1 (external critique) ∥ Prompt 2 (council adjudication).

---

Prompt 1 — External critique of the concept patch

MISSION: COUNCIL_CRITIQUE_ONE_ROOF_CONCEPT_PATCH_ROUND4
Read-only. Recover knowledge/dev/design/one-roof-governance-concepts/ (00–03) + the 7 patched canonical docs (registries-pivot-os-agency 00/04/06/07/08/12 + iu-mow-mot-event-foundation-design.md) + this report package.
Attack: (a) does any concept-patch section smuggle in apply/owner-binding/technical design? (b) does the count>1 dual-sense (M-DEF-10) actually hold on the Registries-Pivot drill surface, or does the UI sense leak governance obligations? (c) is SB-3 surfaced everywhere "no fixed axis array" is claimed, or is there a residual hidden hardcode? (d) does the new concept canon itself read as a second governance roof / island? (e) is any blocker quietly treated as solved?
Return a defect list with severity + required fold; recommend GO / CONDITIONAL GO / NO-GO for proceeding to the apply/substrate tier.
Forbidden: PG/Directus/Qdrant/Nuxt mutation, enactment, version bump, approval, technical design.

Prompt 2 — Council adjudication of the 8-item decision surface

MISSION: COUNCIL_ADJUDICATE_ONE_ROOF_DECISION_SURFACE_ROUND4
Read-only. Recover concept-canon doc 03 + Round-4 doc 02.
For each of C-1 (object-edge table), C-2 (APR action-type bundle), C-3/OP-B (IU owner), C-4 (review_decision adapter), C-5 (GOV-MOUT/render owner), C-6 (shareable-personal boundary), H-1 (enactment phase), H-2 (OP-B ratification): present the recommended default + risk + alternatives; request RULE/DEFER. Produce a draft-minutes decision record per item.
Forbidden: enactment, approval creation, PG mutation, version bump, self-approval.

Prompt 3 — OP-B IU owner assignment council packet

MISSION: DECIDE_OP_B_IU_OWNER_ROUND4
Read-only. Recover concept-canon doc 02 §3 + Round-4 doc 05. Produce a council decision packet for OP-B: confirm/adjust owner-per-scope (policy→COUNCIL, substrate/health→KG-SYS+SIV, exec→DOT, render→MOUT interim TTL, law→NRM-SYS) and rule on C-4 (review_decision adapter vs full Đ32). Include live evidence (no GOV-IU agency; owner_ref free-text; conformance_status='open' all 219; 54-cmd island; iu_three_axis_envelope 3 axes). Draft minutes only; do NOT bind ownership into governance_registry, do NOT enact. This UNBLOCKS the IU surface/owner-binding tier and SB-3 (IU technical design).
Forbidden: PG mutation, approval, enactment, version bump.

Prompt 4 — Substrate design for SB-1/SB-2/SB-3 (design + read-only rehearsal)

MISSION: DESIGN_GOVERNANCE_SUBSTRATE_SB1_SB2_SB3_ROUND4
Design-Only Macro Mode. Read-only PG; BEGIN..ROLLBACK rehearsal only if necessary; NO committed DDL/DML.
SB-1: design the 4 apr_action_types + handler/council-review wiring.
SB-2: design the additive governance_object_ownership table (prove no migration risk to the 8 live agency→law edges).
SB-3: design the IU Axis Registry + generic iu_axis_value store + demote iu_three_axis_envelope to a hot-cache projection (prove a 4th axis becomes data, not DDL).
PRECONDITION for SB-3 commitment: OP-B decided (Prompt 3). Deliver DDL drafts (uncommitted) + rollback scripts + read-only rehearsal log + apply-readiness gate.
Forbidden: committed DDL/DML, enactment, approval, production mutation.

Prompt 5 — Content-only law cleanup + registration (L-1/L-2)

MISSION: CONTENT_ONLY_LAW_CLEANUP_AND_REGISTER_ROUND4
Read-only survey + DRAFT-only law-text corrections (no enactment, no version bump, no normative_registry write — DRAFT packet only).
L-1: Đ36 v4.0-vs-v5.0 authoritative version; Đ45 strip ban_hanh=false leftover; Đ37 v3.3 text reconciled to live columns + capability JSON.
L-2: prepare normative_registry DRAFT rows for Đ20, Đ23, Đ44(draft), Đ45. Output a ratification packet for the human enact phase. Do NOT write to normative_registry/law_catalog/governance_docs.
Forbidden: enactment, version bump, registry write, approval.

Prompt 6 — Governance-coverage scanner / DOT technical design (GATED)

MISSION: DESIGN_GOVERNANCE_COVERAGE_SCANNER_DOTS_ROUND4
PRECONDITION: concept patch accepted (Prompt 1 GO) + SB-1/SB-2 substrate design accepted (Prompt 4). Design-only + read-only rehearsal.
Design the 6-layer coverage detector + scan/propose/apply/audit DOT family (reuse Đ19 orphan scanner + Đ35 DOT pattern + GOV-SIV); add dot_coverage_required rows (governance.coverage/classification/pivot/axis/iu) for SB-8; design the anti-spam path (coalesce_key/cooldown/summary/emit-ceiling) against live template_gap=182,378; design the inventory-completeness reconciliation (governance twin of birth-orphan). NO committed DOT, NO production scan emit.
Forbidden: committed DOT/scan, event emit, PG mutation, enactment.

---

Sequence: Prompt 1 (critique) ∥ Prompt 2 (council adjudication) ∥ Prompt 3 (OP-B) ∥ Prompt 5 (law cleanup) → Prompt 4 (substrate design, after OP-B for SB-3) → Prompt 6 (scanner design, gated on Prompt 1 + 4) → [human enact phase H-1].

If a reviewer downgrades the concept patch: fold the exact objections into the concept canon clause cards (do not restart), re-run the critique, re-issue the verdict.