GPT Cross-Law Review Before 4 Mothers Design Approval — MP-D23..MP-D28

Date: 2026-05-28 Reviewer: GPT Council via Web Connector fallback

Sources checked

• Hiến pháp v4.6.3 / constitution search results including NT13 PG First and NT14 execution traceability.
• Điều 7 Assembly First.
• Điều 28 Display / Template Law v2.0.
• Điều 28 Appendix A — Nuxt/UI Assembly Governance draft.
• Điều 36 Collection Law v5.0 draft and collection protocol principles.
• Điều 37 Governance Organization Law v3.3 search context.
• Điều 29 Classification Collection Law v2.0 search context.
• Master Design Rev4 docs for IU/4 Mothers/Event/Governance.

Verdict

NO_FATAL_CONFLICT_BUT_PREAPPROVAL_CROSS_LAW_PATCH_REQUIRED

The 4 Mothers design does not fundamentally violate the Constitution or existing laws, but before final approval it should receive a cross-law patch to prevent downstream implementation from creating bespoke UI, unregistered collections, duplicate ownership, or object/collection sprawl.

Main risks found

R1 — Điều 28 template binding not explicit enough

Every MOW/MOT/MOIT/MOUT UI surface must be a registered Điều 28 template/product. The current design says Nuxt is shell-only but does not strongly bind every 4 Mothers surface to design_templates, product-from-template registry, whitelist, coverage scanner, template lifecycle, and DOT-template-health.

R2 — Collection/object birth governance not explicit enough

4 Mothers create many object families and eventually many tables/views/registries. The design must explicitly state that every new collection/table/view/registry spawned by MOW/MOT/MOIT/MOUT must go through Điều 36 / Birth Registry / collection_registry / species mapping / governance_role / lifecycle / health checks. Otherwise the system may produce orphan tables or wrong-chuồng entities.

R3 — Object model for the Mothers is not formalized enough

MOW, MOT, MOIT, MOUT are not merely modules. They are governed object factories. The design should classify each Mother and each generated artifact as entity species/object type with owner law, lifecycle, collection home, relations, and permissible creation path.

R4 — Điều 37 organization/permission boundary needs stronger binding

The design has permission-filtered visibility, but it should explicitly bind MOW/MOT/MOIT/MOUT surfaces and generated objects to Điều 37 jurisdiction, roles, delegation, governance queues, and backend permission filter. This is important because the same UI pattern exposes radically different slices to staff, department leads, and super admin.

R5 — NT14 execution traceability needs a matrix

Constitutional execution traceability requires mapping words to runtime artifacts. The final design should include a traceability table: requirement -> object/collection/template/event/DOT/health check -> verify gate. This prevents law/design text that cannot become DDL/config/DOT/verification later.

R6 — Assembly First object explosion risk

Mothers can generate many artifacts. The design must include a create-vs-reuse decision tree before any new registry/table/template is proposed. Reuse/extend existing table, view, registry, template, or DOT first; create new only if proven necessary.

Required patch set

MP-D23 — Điều 28 Template Binding for 4 Mothers UI Surfaces

Bind every UI surface to design_templates, product-from-template registry, whitelist, coverage scanner, 5/5 template tests, checklist, lifecycle, DOT-template-health, and custom-code registry when unavoidable.

MP-D24 — Điều 36 Collection/Object Birth Protocol for 4 Mothers Artifacts

Every object/table/view/registry generated by MOW/MOT/MOIT/MOUT must declare collection_registry, species mapping, governance_role, owner law, lifecycle, relation matrix, birth path, health check, and rollback/retire path.

MP-D25 — 4 Mothers as Governed Object Factories

Formalize each Mother as an object factory, not a free module: what it can create, what it cannot own, which law owns each child object, and how child object lifecycle/audit is governed.

MP-D26 — Điều 37 Organization / Permission / Jurisdiction Binding

Bind all UI visibility, proposal queues, governance cockpit queues, and generated objects to organization scopes, roles, jurisdiction, delegation, and backend permission filters.

MP-D27 — Constitutional 14/NT Execution Traceability Gate

Add a cross-law traceability matrix for MP-D23..MP-D26 and existing 4 Mothers surfaces: requirement -> PG registry/table/view -> Directus exposure -> Nuxt template -> DOT/API mutation path -> event/queue path -> health/verification gate.

MP-D28 — Assembly-First Reuse Decision Tree for Mother-Generated Artifacts

Before creating new tables/templates/registries, require a decision tree: existing table/view/template/registry? extend? adapter? view? paper-only new? survey required? The default is reuse/extend, not create.

Recommendation

Run a document-only cross-law patch before final approval:

IU_4MOTHERS_MASTER_DESIGN_CROSS_LAW_OBJECT_TEMPLATE_COLLECTION_PATCH_DOCUMENT_ONLY_XHIGH

No implementation. No schema creation. All objects paper-only until survey/approval.