15 — Next Prompts (≥6 paste-ready)

Each is self-contained, read-only-or-author-mode by default, no-self-approval, evidence-first.

---

Prompt 1 — Claude Desktop / Cowork critique of THIS audit

Read the KB package knowledge/dev/reports/architecture/full-stack-governance-alignment-audit-registries-pivot-grouping-2026-05-31/ (docs 00–16). Act as an adversarial governance reviewer. Challenge specifically: (1) Is "Option 4 — split ownership by object type (Council=policy, SIV=health, DOT=exec, MOUT=render)" actually superior to a single GOV-COUNCIL owner, given Đ37 §4.12(d)? (2) Is the claim "no table in the system has owner_gov_code, so bind relationally" a correct reading, or should a governed-object binding column be introduced system-wide (patch P3)? (3) Are display_policy / registry_pin / phantom correctly classified as LAW_GAP DEFER, or is there an existing law clause that already covers them? (4) Does assigning the classification domain to GOV-COUNCIL (a deliberative body) create an operational bottleneck? Cite exact docs/laws. Output: agreements, disagreements with evidence, and any missed island risk. Do not propose implementation.

Prompt 2 — Law/design patch drafting (author-mode, NO enactment)

Author-mode only, no enactment, no self-approval, zero PG mutation. Using doc 14 of the governance-alignment package, draft the full text of: P1 (Đ31 phantom definition, source_model-aware), P2 (Đ24/Đ29 ungrouped display ceiling), and P-PIN (pin/watch clause). For each: cite the host law's existing section numbering, write the clause in the law's Vietnamese house style, list the additive PG objects (columns/issue-types/event-types) it authorizes, and the Đ32 approval authority required to enact (council_review). Produce a council ratification packet with an exact paste-ready sign-off block. Save to knowledge/dev/reports/architecture/registries-pivot-law-patches-draft-<date>/. Do NOT INSERT into normative_registry. Do NOT create approvals.

Prompt 3 — Governance owner / capability ratification (read-only verify + author packet)

Read-only. Verify live in PG (db=directus, role context_pack_readonly): (a) governance_registry has no agency with domain in ('classification','classification.label','classification.species','pivot'); (b) law_jurisdiction primary owners for those domains (expect Đ24/Đ26); (c) governance_relations has zero agency→object edges; (d) governance_audit_log row count. Then author (NOT execute) the Đ37 §4.12(d) Council decision packet that assigns: classification+classification.label/.species → GOV-COUNCIL, pivot → GOV-SIV, with the exact governance_registry INSERT/UPDATE + governance_relations agency→law edges + governance_audit_log minute, all as a reviewable SQL plan wrapped for BEGIN..ROLLBACK rehearsal only. Specify the approval_requests(request_type, action, target_collection, risk_level) needed and the quorum per Đ32 §4.2. Do NOT run the writes; do NOT create approvals; rehearsal plan only.

Prompt 4 — PG design/rehearsal for the governed grouping framework (BEGIN..ROLLBACK only)

Read-only + BEGIN..ROLLBACK rehearsal only (no commit, no self-approval). Target db=directus on contabo. Rehearse, never persist: (1) the per-species ungrouped-ceiling reference table (Đ24 pattern, default 50, CHECK>0), seeded from live species, reporting how many leaf lists exceed it; (2) the relational ownership binding (governance_relations agency→object edge) IF patch P3 widens target_type — otherwise prove domain-ownership suffices; (3) new issue_types (pivot_missing, count_integrity_failed, classification_required) + event_types as INSERTs inside a rolled-back tx, confirming Đ45 register-before-emit. Report PRE/POST row counts == and idle_in_transaction==0. Cite doc 05/11/14. ROLLBACK everything; commit nothing.

Prompt 5 — Registries-Pivot UI correction after governance alignment (Đ28, no hardcode)

Read-only audit + author-mode fix plan, no Nuxt deploy. Against the LIVE /knowledge/registries-pivot route and its Nitro endpoints (server/api/registries-pivot/*, server/utils/rpGatewayDb.ts): (1) confirm zero count math / hardcoded CAT-* / grouping arrays in the Vue+endpoints (Đ28 NT-D1/D3, Test-4 "100% Nuxt = PG"); (2) confirm every displayed group is PG/pivot-backed or explicitly marked PIVOT_MISSING/CLASSIFICATION_REQUIRED/DATA_MISSING; (3) assess the direct-pg Pool vs PG→Directus→Nuxt convention and draft the Đ41 API-exception approval text (doc 14 P7) OR the plan to add view PKs and route via Directus. Output a fix plan + the acceptance test list (Đ30 Playwright). Do NOT edit code, do NOT deploy, do NOT retire legacy routes.

Prompt 6 — DOT grouping scan/propose/audit implementation spec (Đ35, author-mode)

Author-mode only, no DOT registration, no approvals. Per doc 08, write the full Đ35-compliant spec for the grouping/pivot-coverage DOT set: dot-grouping-scan (A, read-only, op=health/classify), dot-grouping-apply (B, mutating, op=update/classify, paired_dot=dot-grouping-scan, approval=Đ32), dot-pivot-declare (B) ↔ dot-pivot-health (A), dot-classification-stale-audit (A). For each: the 11 dot_tools fields, mutating/reversible flags, dot_coverage_required(domain×operation×tier) entry, paired test (dot-XXX-test smoke), backup/rollback (Đ35 §6.2), fn_log_issue failure path, and the new_dot approval_requests it requires. Mark which require president vs council vs auto per risk. Do NOT POST to dot_tools; do NOT create approvals; spec only.

Prompt 7 (bonus) — Close the governance audit loop + register missing laws

Read-only verify + author-mode plan. (1) Confirm Đ20/Đ23/Đ45 are absent from normative_registry but present as KB docs; draft the P-REG INSERT plan (with kb_path, status, doc_level) for GOV-NRM-SYS to enact. (2) Confirm governance_audit_log has only 1 row; draft the P6 plan to wire DOT-GOV-VERIFY/DISCOVERY (Đ37 §6) writes + attach Council ownership minutes. (3) Draft P-DRIFT: a side-by-side of enacted Đ37 v3.3 columns/CHECKs vs the live governance tables, recommending canonical vocabulary. Author only; no INSERT, no enactment.