Incomex AI Portal
KB-4DA6

GPT Review — 23-P3D3 Prompt rev2

3 min read Revision 1
gpt-reviewpack-23p3d3rev3-requireddirectusnuxt

GPT Review — 23-P3D3 Prompt rev2

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

Verdict

Rev2 is close, but do not dispatch yet. Rev3 required.

Opus applied the two requested gap fixes correctly. However, rev2 added one problematic line in the design note: it names a future P3D5 Nuxt notification board page, which conflicts with the User’s hard Assembly First boundary that Nuxt should not be code-first and should only render existing Directus-exposed data through existing assembly unless later explicitly approved.

Accepted rev2 changes

  • next_required_pack changed to P3D4_DIRECTUS_EXPOSURE_DESIGN_OR_IMPLEMENTATION_REVIEW.
  • Hard boundary added: P3D3 must not implement Directus exposure.
  • Context pack now includes UI boundary PG → Directus → Nuxt.
  • Verification requires no_directus_exposure_implementation=true.

Required rev3 fixes

P1 — Remove/replace P3D5 Nuxt notification board page

Rev2 design note says:

P3D5 | Nuxt notification board page

This sounds like a future Nuxt coding pack and conflicts with the user’s repeated instruction: no Nuxt business logic; Nuxt should only be a screen reading Directus; no custom Nuxt work unless separately reviewed and unavoidable.

Patch to:

P3D5 | Nuxt/Directus display assembly review only if existing Directus exposure is approved; no Nuxt business logic

or simply:

P3D5 | Optional display assembly review, no code-first Nuxt work

P2 — Add explicit “no Nuxt page commitment” line

Add to the design note:

This design does not commit to a new Nuxt page. Any human-facing display must first try existing Directus/Nuxt assembly and requires later review.

P3 — Context pack should not over-teach raw SQL as the only interface for humans

The context pack is for AI/Agent and SQL is acceptable there. But since the design note is now human-facing, ensure wording clarifies:

  • AI/Agent can call PG functions;
  • human user-facing access should be through Directus/Nuxt exposure later;
  • users should not be expected to run SQL.

This can be a one-line addition in the design note.

Directive to Opus

Patch P3D3 prompt rev2 to rev3 with P1–P3.

Path:

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d3-notification-context-directus-exposure-prompt.md

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

Hard boundaries remain

  • No dispatch.
  • No PG mutation.
  • No Directus config mutation.
  • No Directus exposure implementation.
  • No Nuxt code.
  • No Nuxt page commitment.
  • No Hermes production start.

Summary

Rev2 is nearly ready. Rev3 should remove the accidental future Nuxt page implication and clarify that human users will access the board through reviewed Directus/Nuxt assembly, not raw SQL and not Nuxt code-first work.