KB-280F

10 — Law Mapping, Forbidden Compliance & Self-Review (2026-05-28)

5 min read Revision 1
law-mappingforbidden-complianceself-reviewiusuperbundledieu30dieu32dieu37dieu392026-05-28

10 — Law Mapping, Forbidden Compliance & Self-Review

1. Law mapping

Branch Governing law(s)
A pilot adoption Đ32 approval, Đ30 reversibility, Đ31 audit/integrity, Đ35 DOT
B candidate registry Đ0-G birth, Đ36 collection, Đ37 governance, Đ28 template, Đ7 assembly, layer3-information-law
C KG enrichment (LIVE) Đ39 IU/KG (provenance-or-quarantine), Đ38 IU, Đ30 reversibility, information-atom-law (8 relation atoms)
D design recon Đ31 integrity (doc truth ↔ live truth)
E P-pub Đ32 approval, publication vocab, Đ31
F prod review_decision Đ32 approval (no bypass), Đ31 audit, cutter_governance privilege wall
G human-org-role Đ37 (orthogonal human layer = Đ37-H draft), Đ28 template surfaces
H gate board Đ0-G + Đ32 + Đ37 (factory birth gates)

2. The one live change — safety dossier

  • Object: iu_relation (60 rows, 0 triggers, not Directus-managed) + new view v_kg_edges_all.
  • Operations: 5 additive nullable columns + 1 read-only security_invoker view + GRANT SELECT to read role.
  • Method: dress-rehearse (BEGIN..ROLLBACK, cols 14→19→14 proven) → COMMIT → fresh-connection verify.
  • Post-state: 5 cols present; view=2259 edges; data rows unchanged (iu219/rel60/edges2199); gates all_safe=true, never_flip_intact=true.
  • Reversibility (Đ30): DROP VIEW + DROP COLUMN ×5, one statement each, no dependent data.
  • Audit (Đ31): COMMENTs on view + 2 columns record origin/date/rollback.
  • Why lawful additive, not "đẻ rơi": iu_relation is an existing governed object; adding nullable columns + a derived read-only projection is maintenance of an existing object, not birth of a new collection. No new born collection was created (those stayed authority-pack precisely to honor Đ0-G/Đ32).

3. Forbidden compliance (§13 of macro) — VERIFIED

Forbidden Status
No 4 Mothers runtime ✅ none
No Nuxt/UI ✅ none
No Directus mutation ✅ none (no directus_* table touched)
No Qdrant/vector write ✅ vector_sync_enabled=false, never_flip intact
No unsafe P-pub hard-block ✅ P-pub stayed authority-pack (S1 warn only proposed)
No production review_decision shortcut ✅ authority-pack only; no agent mint
No allow_no_review_decision=true ✅ false throughout
No vector_sync_enabled=true ✅ false throughout
No gate left open ✅ gate_tx=0; no fn_iu_gate_open called
No hidden second SoT ✅ view reads existing SoTs; no IU→universal_edges migration
No law enactment ✅ Đ37-H is a draft
No final OSS/tool selection ✅ none made

4. Acceptance criteria check (§15)

  • Branches A–I completed or precisely deferred ✅
  • Safe live assembly attempted where justified ✅ (KG, committed + durable)
  • Candidate Registry materially beyond "absent" ✅ (reuse map + DDL + birth sequence, doc 02)
  • KG materially beyond "design only" ✅ (LIVE-APPLIED, doc 03)
  • Pilot adoption package operator-usable ✅ (doc 01)
  • 4 Mothers gate board explicit ✅ (doc 08, G1–G4)
  • ≥10 high-quality prompts ✅ (doc 09, exactly 10, all large/open-goal)
  • No unsafe mutation ✅ Overall: PASS.

5. Corrections vs prior memory

  • Prior bundles recorded iu_relation as "lacking provenance/confidence" — now resolved live (5 Đ39 columns added this run).
  • iu_create.ppub.enforcement_mode confirmed absent (must be created for staging) — consistent with prior, now re-verified.
  • governance_registry confirmed 5 rows, no factory rows — factory registration is a 4-Mothers gate (G4).
  • cutter_governance confirmed not visible to readonly role (privilege wall real).
  • review_decision confirmed absent in public (lives in cutter_governance).

6. Underload check (§16)

This bundle exceeded prior bundles by performing the first safe live assembly (KG), producing implementation-ready DDL (3 new + 5 reuse registries), a serious draft law (Đ37-H with 2 tables + matrix + Directus map), an operator-usable pilot package, an explicit 4-gate board, and 10 large prompts. Not a survey: it built and committed a real foundation. The package is a control tower for the next phase.

7. Final verdict

PASS. One safe, authorized, reversible live change (KG). All other unsafe branches delivered as implementation-ready authority/design packs. 4 Mothers gated on G1–G4, each with an unblock macro. Vector OFF, never-flip intact, no gate left open, no hidden SoT.

Back to Knowledge Hub knowledge/dev/reports/architecture/iu-pilot-cr-kg-recon-authority-live-assembly-superbundle-2026-05-28/10-law-forbidden-and-self-review.md