GPT Review — 23-P3D4 Prompt rev1 with User Law Clarification

Date: 2026-05-08
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Reviewed: knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d4-directus-exposure-design-review-prompt.md rev1

Verdict

Rev1 is directionally correct, but do not dispatch yet. Rev2 required.

Opus correctly strengthened the prompt toward Assembly First and read-only inventory. However, the User clarified additional non-negotiable boundaries that must be explicit before P3D4 runs:

1. Directus must be DOT-driven 100%; Directus UI is for viewing only.
2. Users do not edit content in Directus; target operation is automated.
3. Nuxt code is absolutely forbidden; Nuxt is only a display/assembly layer reading Directus.
4. Future Nuxt display, if ever needed, must follow existing TreeView pattern: 2-column folder/file + file detail, or 3-column TreeView if detail complexity requires it.
5. P3D4 must read the Constitution and relevant laws first so directives do not violate established rules.

Accepted rev1 points

• P3D4 is design review + inventory only, not implementation.
• No PG mutation.
• No Directus mutation.
• No Nuxt code.
• No Codex dispatch without user approval.
• Inventory is read-only.
• Assembly First is treated as mandatory.
• Recommendation note output path is correct.

Required rev2 fixes

P1 — Add mandatory law pre-read section

Before the P3D4 files, Agent must read relevant law documents. Add a section at the top:

0. Mandatory law pre-read

Required documents:

• knowledge/dev/laws/constitution.md
• knowledge/dev/laws/law-07-assembly-first.md
• knowledge/dev/ssot/data-connection-law.md
• knowledge/dev/laws/dieu38-trien-khai/data/p10b-d28-fix-package/candidate-units-r2.json or a rendered Điều 28 / display-law source if available
• knowledge/dev/laws/dieu44-trien-khai/design/23-p3d-ui-boundary-directus-nuxt-assembly-note.md

Purpose:

• Constitution / architecture: PG is source of truth; Directus is gateway; Nuxt is gate/display.
• Law 07: PostgreSQL first, Directus existing capabilities second, Nuxt existing UI third, code last and only with approval.
• Data connection law: application/gate must not bypass Directus to connect PG directly.
• Display law / Điều 28: UI must follow existing display patterns, including TreeView conventions.

If any law source cannot be read, Agent must STOP and report which source is missing.

P2 — Add Directus DOT-only boundary

User clarified: Directus must be DOT-driven 100%.

Patch hard boundaries and design questions:

Directus configuration/exposure must be DOT-first/DOT-only when implementation is later approved.
Directus UI is for view/inspection only.
No manual Directus UI content operation.
No manual Directus UI configuration mutation.
P3D4 may inspect Directus read-only only.
Future implementation, if approved, must produce a reviewed DOT/change package rather than ad-hoc UI clicking.

P3 — Clarify user does not operate content in Directus

Add explicit rule:

Human users may view/monitor notification state through Directus/Nuxt exposure, but they should not edit IU content through Directus UI. IU content operations remain automated through PG functions/Agent workflow.

If mark-read for human is considered, it must be reviewed separately as a controlled action, not free-form Directus editing.

P4 — Strengthen Nuxt prohibition and TreeView standard

Add:

Nuxt code is forbidden in P3D4 and should not be proposed as the primary path.
Nuxt is only a display assembly layer reading Directus.
If a future human-facing display is ever approved, it must use existing Nuxt assembly patterns:
- default: TreeView 2 columns — folder/file list + selected file/detail;
- if necessary: TreeView 3 columns for additional detail;
- no new business logic in Nuxt.

This should appear both in hard boundaries and in the output design note requirements.

P5 — Tighten Directus inventory wording

Rev1 allows Directus API read-only. Keep it, but clarify:

• read-only inventory is allowed;
• no Directus configuration mutation;
• no Directus UI clicking to create/change anything;
• no Directus content operation;
• inventory must report what was inspected and how it remained read-only.

P6 — Change next_required_pack wording

Rev1 says:

next_required_pack=P3D4_IMPLEMENTATION (nếu recommend A/B/C) hoặc DEFERRED (nếu D)

This is too implementation-forward. Patch to:

next_required_pack=P3D4B_DIRECTUS_DOT_EXPOSURE_PACKAGE_REVIEW

if recommend A/B/C, or:

next_required_pack=DEFERRED

if recommend D.

Implementation must require a later reviewed DOT/change package, not direct implementation.

P7 — Add explicit output compliance checklist

The design review note must include a compliance section:

Constitution/Law compliance
- PG source of truth: PASS/FAIL
- Directus DOT-only: PASS/FAIL
- Directus UI view-only: PASS/FAIL
- User no content editing in Directus: PASS/FAIL
- Nuxt no-code/no-business-logic: PASS/FAIL
- Existing TreeView assembly path respected: PASS/FAIL
- No direct PG from Nuxt: PASS/FAIL
- No Codex dispatch: PASS/FAIL

P8 — Adjust recommendation options

Current options A-D are acceptable but should mention DOT and TreeView constraints.

Patch options:

• A: PG view + Directus read-only collection via DOT/change package first.
• B: Directus endpoint/flow backed by PG functions only if DOT-supported and reviewed.
• C: staged approach — read-only board first, mark-read later as controlled action.
• D: defer implementation if DOT/Directus inventory shows risk.

P9 — Report evidence must include law compliance

Final report requirements should include:

law_preread=PASS
constitution_checked=PASS
assembly_first_checked=PASS
directus_dot_only=true
directus_ui_view_only=true
user_no_directus_content_edit=true
nuxt_treeview_standard_documented=true
no_nuxt_code=true
no_nuxt_business_logic=true
no_direct_pg_from_nuxt=true

Directive to Opus

Patch P3D4 prompt rev1 to rev2 with P1–P9.

Path:

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d4-directus-exposure-design-review-prompt.md

Do not dispatch after patch. Return for GPT/User review.

Hard boundaries for rev2

• No dispatch.
• No PG mutation.
• No Directus config mutation.
• No Directus content operation.
• No manual Directus UI changes.
• No Nuxt code.
• No Nuxt business logic.
• No proposal that makes Nuxt a source of workflow logic.
• No direct PG from Nuxt.
• No Codex dispatch without user approval.
• No Hermes production start.

Summary

P3D4 rev1 is close, but rev2 must explicitly incorporate the Constitution/Law pre-read, DOT-only Directus rule, Directus UI view-only rule, user no Directus content-edit rule, and Nuxt TreeView/no-code boundary. This prevents future sessions from drifting into UI/config code-first work.