GPT Review — User Provided Opus Summary + P3D4C Directive

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

Verdict

User-provided Opus summary is directionally correct and suitable as a compact re-entry note, with one clarification:

• Current PG notification runtime creates events for comments, review drafts, and applied official versions.
• Birth/new IU (version_seq=1) was explicitly excluded in P3D2 tests.
• Therefore, if the summary says “miếng mới”, interpret it as “new review draft / newly updated official version”, not every brand-new IU birth event.

This clarification should be carried into P3D4C so the human notification board does not overpromise birth/new-IU notifications unless a later pack explicitly adds them.

Current state confirmed

• Pack 23 IU edit workflow is active.
• P3D notification runtime in PG is active.
• Per-actor read state exists.
• User-facing web board is not implemented yet.
• P3D4B passed and recommended READY_FOR_IMPLEMENTATION_PROMPT.
• Next step is P3D4C prompt drafting, not dispatch.

Role split confirmed

• GPT holds roadmap, architecture direction, critique, final review, and small-detail decisions on behalf of User.
• Opus drafts prompts, executes detailed reviews, and directs Agent.
• Agent executes approved prompts and uploads reports.
• User decides high-level direction, principles, and any major exception such as Nuxt code or Codex dispatch.

Directive to Opus

Create P3D4C prompt, do not dispatch.

Prompt path:

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d4c-pg-view-directus-dot-notification-readonly-implementation-prompt.md

Future report path:

knowledge/dev/laws/dieu44-trien-khai/reports/23-p3d4c-pg-view-directus-dot-notification-readonly-implementation-report.md

P3D4C prompt must implement a reviewed execution plan for:

1. public.v_iu_notification_board PG view.
2. Metadata-only HISTORY scope.
3. No IU body, no unit_version body, no raw payload jsonb.
4. read_count = COUNT(DISTINCT actor_ref) from iu_notification_read.
5. latest_readers top 5 ordered by read_at DESC, actor_ref ASC.
6. DOT pair: DOT-NOTIF-BOARD-EXPOSE ↔ DOT-NOTIF-BOARD-EXPOSE-VERIFY.
7. Directus read-only exposure only.
8. Role strategy: re-check runtime inventory; reuse suitable existing role if found, else use notif_board_reader only if the reviewed prompt approves it.
9. Rollback: revoke permission + drop view.
10. Quiet period: 24–48h before mark-read / actor mapping / display assembly packages.

P3D4C must preserve these hard boundaries

• No dispatch after prompt drafting.
• No PG mutation while drafting the prompt.
• No Directus mutation while drafting the prompt.
• No Nuxt code.
• No Nuxt business logic.
• No direct PG from Nuxt.
• Directus DOT/change package only.
• Directus UI view/inspect only, no manual configuration.
• Metadata/ref-only board.
• Mark-read deferred.
• Directus user → actor_ref mapping deferred.
• Hermes deferred.
• Codex dispatch only with explicit User approval.

P3D4C prompt must include explicit warning

The board will show PG notification events currently generated by P3D2:

• comment_added;
• draft_created;
• version_applied.

It does not yet show birth/new IU creation events unless those become notification events in a future reviewed pack.

Next after P3D4C prompt

After Opus drafts P3D4C prompt:

1. GPT/User review P3D4C prompt.
2. If approved, dispatch Agent execution in a separate step.
3. If execution passes, observe quiet period before considering mark-read or display assembly.