GPT Review — Nuxt Template Laws vs 4 Mothers Master Design

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

Documents read directly / searched

• knowledge/dev/laws/dieu28-display-technology-law.md
• knowledge/dev/laws/dieu28-trien-khai/appendices/d28-nuxt-ui-assembly-governance-appendix-draft.md
• knowledge/dev/design/v0.6-iu-4mothers-event-foundation-rev2/* via search
• Related D28/P3D reports and Nuxt factory/template records via KB search

Verdict

NO_CONFLICT_BUT_NEEDS_TEMPLATE-BINDING_PATCH_BEFORE_FINAL_APPROVAL

There is no fundamental conflict between Điều 28 / Nuxt template law and the current 4 Mothers design. In fact, 4 Mothers should be implemented as higher-level products/templates governed by Điều 28.

However, Master Design Rev4 should add one small patch before final approval: explicitly bind MOW/MOT/MOIT/MOUT UI surfaces to the Điều 28 design_templates / product-from-template / whitelist / coverage-scanner regime.

Key law points from Điều 28

1. Nuxt only renders from registered templates in PG.
2. No template = no UI.
3. A new UI instance = INSERT config, not new Nuxt code.
4. Template lifecycle requires checklist/test/birth/DOT-health before active.
5. design_templates is the template SSOT.
6. Routes/components outside registry are violations.
7. Coverage scanner target: 0 route/component outside registry.
8. Nuxt can read Directus API, render templates, and submit payloads, but cannot contain business logic, query PG, or coordinate submit logic.

Appendix A additional points

1. No bespoke UI / no local workaround.
2. If shared module/template lacks capability, stop and amend/repair the shared module.
3. Product-from-template registry is mandatory.
4. Route resolution must be registry/config-driven; hardcoded maps are forbidden.
5. Directus permission and field allowlist must exclude unsafe fields.
6. Nuxt code changes require authorization, custom-code registry, rollback, and smoke verification.
7. Mutation/config changes must go through DOT/API, not manual clicking.

Compatibility with 4 Mothers

Compatible mapping:

• MOW Hierarchy Canvas => a registered display template/product family under Điều 28.
• Personal JFT Dashboard => registered template/product family.
• MOT Task Envelope => registered task template surface under Điều 28.
• MOIT Form Renderer => registered form template family under Điều 28, using MOIT registry/config and backend input gateway.
• MOUT Reference/Report Renderer => registered output/reference template family under Điều 28.
• Governance Cockpit => registered dashboard/ops template family.
• AI/Agent Ops Console => registered ops template family.

4 Mothers may define business meaning and binding contracts, but cannot bypass Điều 28 template lifecycle.

Gap requiring patch

Master Design Rev4 says Nuxt is shell-only and UI is config-driven, but it does not yet explicitly state that every 4 Mothers UI surface must be a design_templates registered template/product with product-from-template registry, whitelist, coverage scanner, lifecycle, and DOT-template-health.

Required patch

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

Required content:

1. Map each 4 Mothers UI surface to Điều 28 template/product family.
2. Add rule: no MOW/MOT/MOIT/MOUT UI route/component exists unless registered in design_templates and product registry.
3. Add rule: Nuxt code is limited to reusable renderer templates; all instance behavior comes from PG config/registry.
4. Add rule: if MOW/MOT/MOIT/MOUT needs new UI capability, first check existing template; if insufficient, amend/create shared template under Điều 28 lifecycle — do not create bespoke page/component.
5. Add route resolution rule: MOW/MOT/MOIT/MOUT routes resolve by registry/config, not hardcoded maps.
6. Add coverage scanner rule: all routes/components for 4 Mothers must be covered; target 0 outside registry.
7. Add template test gate: 5/5 template tests + checklist before active.
8. Add Directus/Nuxt permission and field allowlist rule, especially for governance cockpit and staging input/audio/attachments.
9. Add custom-code authorization if a new renderer template is unavoidable.

Non-conflict conclusion

4 Mothers do not replace Điều 28. They sit above it:

• Điều 28 owns UI template/display law.
• 4 Mothers own application/process/task/form/output semantics.
• Nuxt renders registered templates only.
• PG/registry remains SSOT.

Recommendation

Run a small document-only patch before final approval:

IU_4MOTHERS_MASTER_DESIGN_D28_TEMPLATE_BINDING_PATCH_DOCUMENT_ONLY_*X

No implementation.