GPT Final Approval — D28 Generated Table Map Implementation Prompt rev6

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

Verdict

APPROVED FOR DISPATCH.

Rev6 correctly adapts Phase 1B implementation to the actual VPS/container runtime model discovered by Agent.

This approval authorizes only Phase 1B implementation:

generated table maps
replace three hardcoded map consumers
verify inside Nuxt container
commit host-side if safe

It does not authorize deploy, live route smoke, tbl_event_outbox publish, Directus mutation, PG mutation, or P3D resume.

Why rev6 is accepted

Rev6 fixes the rev5 environment-model mismatch:

• runtime commands now execute via docker compose exec into Nuxt container;
• env vars are read from actual container injection;
• tsx, nuxt, and node_modules are used inside container;
• host no longer needs web/node_modules;
• no package install is needed;
• git operations remain host-side where the repo is tracked;
• bind mount verification is included.

Accepted key safeguards

• Infrastructure preflight verifies service name, working dir, mounts, binaries, env, and git cleanliness.
• Mount-through test uses temporary .mount-test and cleanup is required.
• Runtime commands run inside container.
• Host git remains source of commit/diff truth.
• No deploy.
• No live route smoke.
• No Directus mutation.
• No PG mutation.
• No tbl_event_outbox publish.
• No table_registry mutation.
• No container restart.
• No package install.
• No lockfile change.
• No secret/token/URL printing.
• Boolean-only build-log secret scan.
• Expected file whitelist enforced.

Dispatch instruction to Opus/Agent

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

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

Scope:
D28 Phase 1B only — container-exec generated table-map implementation.

Agent target:
claude-go or equivalent agent with VPS SSH + docker compose + git access.

Hard boundaries:
- NO_DEPLOY=true
- NO_LIVE_ROUTE_SMOKE=true
- NO_DIRECTUS_MUTATION=true
- NO_PG_MUTATION=true
- NO_PUBLISH_EVENT_OUTBOX=true
- NO_CHANGE_TABLE_REGISTRY=true
- NO_SECRET_IN_CODE_OR_LOG=true
- NO_PRINT_ENV_TOKEN_URL=true
- NO_PACKAGE_INSTALL=true
- NO_NPX_AUTO_INSTALL=true
- NO_LOCKFILE_CHANGE=true
- NO_CONTAINER_RESTART=true
- NO_DOCKER_COMPOSE_RESTART=true

Expected report:
knowledge/dev/laws/dieu28-trien-khai/reports/d28-generated-table-map-implementation-report.md

Upload report even on PASS, PARTIAL, FAIL, or BLOCKED.

Operational reminders for Agent

1. Replace <NUXT_SERVICE> and <CONTAINER_WEB_DIR> only after verifying them from docker-compose / container state.
2. If mount-through test fails, STOP and report; do not write implementation files.
3. If mount-through test writes .mount-test, always attempt cleanup, even on failure.
4. If generated file or script creation causes unexpected git diff, STOP before commit.
5. If lockfile changes, STOP.
6. If build log secret scan fails, do not paste log content into report and do not commit.
7. If CI check cannot be finalized due unknown GitHub secret, report PARTIAL with follow-up, not PASS.
8. If typecheck/build fails due import alias, fix import path once if clearly safe, then re-run verification.
9. Do not deploy or run live route smoke in this pack.

Expected changed files

Only these files may change:

web/scripts/generate-table-maps.ts
web/generated/table-maps.generated.ts
web/pages/knowledge/registries/[entityType]/index.vue
web/config/detail-sections.ts
web/server/api/discovery/relations.get.ts
web/package.json
web/.gitignore only if needed
.github/workflows/* only if needed

No lockfile changes.

Status interpretation

• phase1b_status=PASS: implementation committed and local/container verification passed, with no required blocker.
• phase1b_status=PARTIAL: implementation committed but CI token/check or another non-fatal automation follow-up remains.
• phase1b_status=BLOCKED: preflight/runtime/environment issue prevents safe implementation.
• phase1b_status=FAIL: implementation attempted but verification failed and was not acceptable.

Next after Agent report

1. GPT/User/Opus review implementation report.
2. If PASS/PARTIAL acceptable, next pack is likely deploy + live route smoke.
3. Only after deploy/smoke PASS, resume P3D Phase 1C:
   • route smoke for event_outbox;
   • publish tbl_event_outbox if appropriate;
   • complete notification display checkpoint.

Current P3D state to preserve

table_registry_id=21
permission_id=1483
tbl_event_outbox.status=draft
notification_display=paused
primary_goal=information_unit_text_as_code_infrastructure

Final status

prompt_rev6=APPROVED_FOR_DISPATCH
scope=PHASE_1B_GENERATED_MAP_IMPLEMENTATION_CONTAINER_EXEC_NO_DEPLOY
agent_dispatch_allowed=true
deploy_allowed=false
live_route_smoke_allowed=false
p3d_resume_allowed=false