GPT Review — D28 Generated Map Design and UI Requirements Gate

Date: 2026-05-09
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Reviewed:

• knowledge/dev/laws/dieu28-trien-khai/design/d28-generated-table-map-design.md
• knowledge/dev/laws/dieu28-trien-khai/reports/d28-generated-table-map-design-review-report.md
• knowledge/dev/laws/dieu28-trien-khai/reviews/opus-review-d28-generated-table-map-design-2026-05-09.md
• knowledge/dev/laws/dieu28-trien-khai/requirements/d28-nuxt-ui-display-requirements-checkpoint-2026-05-08.md

Verdict

Agent design accepted. Opus review accepted.

But do not proceed to implementation prompt yet.

This is the right point to pause and begin the User-led Nuxt/UI display requirements discussion, as previously recorded in the D28 requirements checkpoint.

Why pause now

The generated-table-map design is no longer just a small routing fix. It touches the foundation of how Nuxt resolves and renders registry-backed UI.

Before wiring this into implementation, User requested that we define the higher-level UI/display requirements:

interface types
standard templates/khuôn
selection rules
allowed behaviors
new-template creation process
automated verification

Therefore the next step is not code and not implementation prompt. The next step is requirements drafting under Điều 28.

Assessment of Agent design

Agent met the design prompt requirements:

• VPS path corrected:
  • /opt/incomex/docker/nuxt-repo/web/
• VPS reverify completed.
• 3 hardcoded map areas confirmed:
  • tableIdMap 18 entries;
  • collectionMap 20 entries;
  • relations.get.ts mirror 14 entries, drift confirmed.
• table_registry schema inspected:
  • 17 columns;
  • no entity_type column.
• 21/21 rows classified.
• Design recommendations provided.
• No implementation, no mutation, no secret leakage.

Accepted technical recommendations as candidates

These recommendations are technically sound and may be used later after requirements are settled:

entityType strategy: E4 Phase 1 → E3 Phase 2
script: web/scripts/generate-table-maps.ts
output: web/generated/table-maps.generated.ts
credential: build token via NUXT_DIRECTUS_SERVICE_TOKEN
build timing: prebuild + committed generated file + CI --check
draft handling: default exclude draft; use --include-draft or force_include for preview/smoke
import: pure static module, safe for client/SSR/server

However, accepting them as design candidates is not implementation approval.

Important data-quality flags

These should be tracked but not fixed in the requirements discussion unless needed:

• tbl_modules_list.collection='tasks' likely incorrect; probable future data-fix pack.
• tbl_workflow_timeline shares workflow_steps collection with tbl_workflow_steps; needs disambiguation policy.
• relations.get.ts map drift will be eliminated by generated map if/when implemented.

UI requirements gate is now active

Per checkpoint:

knowledge/dev/laws/dieu28-trien-khai/requirements/d28-nuxt-ui-display-requirements-checkpoint-2026-05-08.md

This is the point to ask User for the display-requirements sketch.

GPT should now say to User:

Bây giờ đã đến điểm phù hợp để bàn bộ yêu cầu/quy hoạch hiển thị Nuxt trước khi viết implementation prompt.

Directive to Opus — next action

Do not write implementation prompt yet.

Instead, Opus should prepare a requirements-capture scaffold in KB after User gives the sketch.

Proposed future document path:

knowledge/dev/laws/dieu28-trien-khai/requirements/d28-nuxt-ui-display-requirements-spec-draft.md

This spec should be drafted from User requirements and should cover:

1. Allowed Nuxt interface/display types.
2. Purpose and use cases for each type.
3. Which template/khuôn renders each type.
4. Data shape and source for each type.
5. Fields/actions/filters/badges/status/timeline/relationship display rules.
6. Template selection decision tree.
7. New-template creation gate.
8. Template extension gate.
9. Forbidden patterns.
10. Machine-verifiable smoke tests.
11. Permission/field allowlist interaction.
12. Legacy classification and migration rules.
13. How generated maps and table_registry support the display rules.

Only after this requirements spec is reviewed should Opus revise the D28 appendix/design and then draft implementation prompt.

Do not do yet

• Do not write D28 generated-map implementation prompt.
• Do not edit Nuxt.
• Do not create generated map file.
• Do not publish tbl_event_outbox.
• Do not resume P3D notification display.
• Do not fix tbl_modules_list.collection yet.
• Do not add entity_type column yet.

Current P3D state remains

table_registry_id=21
permission_id=1483
tbl_event_outbox.status=draft
notification_display=paused
implementation_allowed=false
nuxt_edit_allowed=false

Final status

agent_generated_map_design=ACCEPTED_AS_CANDIDATE
opus_review=ACCEPTED
implementation_prompt_allowed=false
ui_requirements_discussion_required_now=true
next_action=USER_PROVIDES_NUXT_UI_DISPLAY_REQUIREMENTS_SKETCH