D28 Checkpoint — Nuxt/UI Display Requirements Before Technical Design
D28 Checkpoint — Nuxt/UI Display Requirements Must Precede Technical Design
Date: 2026-05-08
Recorded by: GPT-5.5 Thinking / Incomex Hội đồng AI
Status: Requirement checkpoint — discuss with User before technical design finalization
User directive
Before beginning or approving technical design for Nuxt/UI display mechanisms, GPT/Opus/Agent must first discuss and pass a detailed display-requirements layer.
User will provide a requirements sketch when ready. GPT/Opus must then convert it into a detailed requirements/specification package for Điều 28 Nuxt/UI display governance.
Core principle
Nuxt UI must not be designed ad hoc per feature.
The system must define standard interface/template types first, then each display need must use an existing template type by rule.
If a new interface pattern is needed, it must go through a formal template design process before use.
Requirements for UI types and display rules
→ template/khuôn standardization
→ technical design
→ code/tooling implementation
Required content to define before technical design
The requirements/specification package should define at least:
- What types of Nuxt interfaces exist or are allowed.
- For each interface type, what use case it is for.
- For each interface type, which standard template/khuôn renders it.
- Which data source shape each template expects.
- Which fields, actions, filters, status, badges, relationships, and timeline patterns are allowed.
- How to choose the correct template for a new display need.
- What is forbidden: bespoke UI, feature-specific pages, duplicated business logic, hardcoded maps, unsafe field exposure.
- What process is required to create a new template type.
- What process is required to extend an existing template type.
- What machine-verifiable smoke tests prove the display is correct.
- How Directus permissions and field allowlists interact with UI templates.
- How legacy Nuxt views are classified and migrated.
Implication for current generated-map work
Generated table map design may continue as read-only design review, but final technical design/implementation should not be approved until the display requirements discussion is complete or explicitly scoped as a supporting infrastructure step under Điều 28.
The current route-map issue is a Table Module infrastructure gap. It must be integrated into the broader display-governance requirements, not solved as a one-off notification or registry-table patch.
Reminder to GPT
When the current Agent/Opus work reaches a natural review point and before approving technical design/implementation, remind User:
This is the point to discuss the Nuxt/UI display requirements package before finalizing technical design.
Do not let the workflow jump directly from inventory/design mechanism into code.
Current P3D state to preserve
table_registry_id=21
permission_id=1483
tbl_event_outbox.status=draft
notification_display=paused
implementation_allowed=false
nuxt_edit_allowed=false
One-line checkpoint
Before Nuxt technical design is finalized, discuss and codify standard display requirements: interface types, template selection rules, new-template approval process, allowed display behavior, and automated verification.