GPT Final Approval — D28 Generated Table Map Design Prompt rev2

Date: 2026-05-08
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Reviewed: knowledge/dev/laws/dieu28-trien-khai/prompts/d28-generated-table-map-design-review-prompt.md rev2

Verdict

APPROVED FOR DISPATCH.

Rev2 correctly incorporates all nine GPT patches and is now fit for Agent design review. This approval is for read-only VPS reverify + design recommendation only, not implementation.

Accepted rev2 fixes

• Agent must recommend preferred design, not merely list options.
• Live table_registry data and schema inspection added.
• entityType is correctly framed as a data/design problem, not just a code problem.
• Row-by-row classification is mandatory.
• Client/server generated module import safety is included.
• Build-time credential strategy is included, with no secrets in report.
• Draft handling for tbl_event_outbox and chicken-egg smoke/publish issue is included.
• Drift verification is concrete: generate mode, --check, hash/header, CI/deploy verification.
• Report fields include blockers, recommendation, and next pack.

Dispatch instruction to Opus/Agent

Đọc và thực hiện prompt:

knowledge/dev/laws/dieu28-trien-khai/prompts/d28-generated-table-map-design-review-prompt.md

Mục tiêu:
VPS-focused reverify + design recommendation for Option C generated table maps.

Scope:
READ + DESIGN + RECOMMEND ONLY.
No implementation.

Agent must:
1. Reverify the three hardcoded map files on VPS SSOT.
2. Inspect live table_registry data and fields read-only.
3. Classify all table_registry rows.
4. Design generated table map mechanism.
5. Recommend preferred entityType strategy, credential strategy, build timing, draft handling, drift verification, rollback.
6. Upload design doc and review report.

Expected outputs:
- 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

Hard boundaries

no_nuxt_edit=true
no_file_creation_on_vps=true
no_directus_mutation=true
no_pg_mutation=true
no_publish=true
no_deploy=true
no_implementation=true
no_secret_in_report=true
read_and_design_only=true

Additional operational clarifications:

• SSH/cat/grep/find/read-only shell commands are allowed.
• Directus GET only is allowed.
• Do not run commands that generate files, install packages, start builds, or change git state.
• Do not print token values, .env contents, cookies, or credentials.
• When checking scripts/package.json, inspect only command definitions; do not execute build/generate scripts.
• If a command would require secret exposure, skip and report BLOCKED_SECRET_REQUIRED.

Required design emphasis

Agent must pay special attention to:

1. Whether entity_type should become explicit registry data in a future schema pack.
2. Whether Phase 1 can safely use current hardcoded map as a seed while moving toward registry-owned entity_type.
3. Which rows belong to registry entity routes versus workflow/admin/index pages.
4. Whether one pure static generated module can be imported by both client/SSR and server API code.
5. How tbl_event_outbox can be route-smoked while still draft.
6. How CI/deploy detects generated-map drift without human/manual smoke.

Do not proceed beyond design

Do not:

• create the generated map file;
• write generator/verifier scripts;
• edit tableIdMap;
• edit collectionMap;
• edit relations.get.ts;
• publish tbl_event_outbox;
• resume P3D notification display;
• write implementation prompt yet.

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

Next after Agent report

1. GPT/User/Opus review generated-map design report.
2. If design is accepted, Opus drafts implementation prompt.
3. Implementation still requires separate GPT/User approval.

Final status

prompt_rev2=APPROVED_FOR_DISPATCH
scope=VPS_REVERIFY_PLUS_DESIGN_RECOMMENDATION
implementation_allowed=false
nuxt_edit_allowed=false
p3d_resume_allowed=false