Incomex AI Portal
KB-4FE0

GPT Checkpoint Report — Pack 23/P3D Notification + Directus Exposure

5 min read Revision 1
gpt-onlycheckpointpack-23p3dnotificationdirectushandoff

GPT Checkpoint Report — Pack 23/P3D Notification + Directus Exposure

Date: 2026-05-08
Audience: GPT only.
Instruction: This report is for GPT checkpoint continuity only. Opus/Claude does not need to read this file to save time/tokens. Use the handoff document instead for Opus.

1. What is complete

PG/IU edit workflow

  • New IU content can be created through the front door.
  • Existing IU content edits create drafts under require_review policy.
  • Drafts can be applied into official versions through reviewed approval.
  • Comments remain free-flow and do not require approval.
  • fn_iu_save, fn_iu_comment, and fn_iu_apply_edit_draft are the operational front-door functions.

PG-native notification runtime

  • P3D1 created notification tables and read/unread functions.
  • P3D2 activated triggers and board function.
  • PG now creates notification events for:
    • non-system comments;
    • new review drafts;
    • official version-applied events.
  • PG tracks per-actor read state.
  • Creator implicit self-read is implemented.
  • fn_iu_unread, fn_iu_mark_read, and fn_iu_notification_board exist.

Documentation/context

  • P3D3 updated the AI/Agent context pack.
  • P3D3 created user-facing Directus exposure design notes.
  • Directus/Nuxt boundary is documented:
    • PG = source of truth;
    • Directus = exposure layer;
    • Nuxt = display assembly only;
    • no Nuxt business logic;
    • no direct PG from Nuxt.

Directus exposure design and inventory

  • P3D4 completed read-only Directus/PG inventory.
  • Directus already auto-registers iu_notification_event and iu_notification_read but item access is 403 pre-DOT.
  • PG currently has no notification view.
  • P3D4 recommended staged Option C: read-only metadata board first; mark-read later.

DOT package review

  • P3D4B completed a non-executable DOT package review.
  • Recommendation: READY_FOR_IMPLEMENTATION_PROMPT.
  • View scope: HISTORY.
  • Payload strategy: OMIT_RAW_PAYLOAD.
  • Role strategy: NEW_ROLE_RECOMMENDED (notif_board_reader), with re-check at implementation time.
  • Overlap risk with Điều 43/DOT/counting: LOW.
  • Reused conventions: 3-part DOT description contract + NT12 paired DOT + PG-native COUNT(DISTINCT actor_ref).

2. Where we are now

The system has:

PG notification runtime: ACTIVE
AI/Agent context: UPDATED
Directus exposure design: DONE
P3D4B candidate package review: DONE / GO
Human-visible Directus/Nuxt board: NOT IMPLEMENTED YET

The next required pack is:

P3D4C_PG_VIEW_AND_DIRECTUS_DOT_IMPLEMENTATION_PROMPT_REVIEW

Important: P3D4C is still a prompt review first. Do not dispatch execution until the P3D4C prompt is reviewed and approved.

3. Next thing to do

Opus should create a P3D4C prompt:

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 should cover, but not execute:

  1. Creating public.v_iu_notification_board.
  2. Metadata-only view columns.
  3. No raw payload, no IU body.
  4. Deterministic read_count and latest_readers.
  5. Directus DOT/read-only exposure plan.
  6. Role strategy: reuse existing if suitable, else notif_board_reader if approved.
  7. Tests, rollback, and 24–48h quiet period.

4. Critical constraints to preserve

  • No Nuxt code.
  • No Nuxt business logic.
  • No direct PG from Nuxt.
  • Directus must be DOT-driven.
  • Directus UI is view/inspection only, not content operation/config mutation.
  • User does not edit IU content in Directus.
  • Metadata/ref-only board first.
  • Mark-read for humans is deferred.
  • Directus user → actor_ref mapping is deferred.
  • Hermes production remains blocked.
  • Codex dispatch requires explicit user approval.
  • Do not duplicate Điều 43 DOT/counting conventions.

5. Most recent GPT directive

Latest GPT review/directive saved at:

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-23-p3d4b-execution-pass-and-p3d4c-directive-2026-05-08.md

Use that directive to instruct Opus.

This is a good checkpoint to change session after giving Opus the P3D4C directive or after Opus drafts P3D4C prompt. The next phase will involve executable SQL/DOT prompt review, so preserving clean context is important.

7. One-line summary

Pack 23/P3D has completed the PG edit + notification infrastructure and DOT exposure design. The next step is P3D4C: draft, review, and later execute a safe read-only PG view + Directus DOT exposure package for a human-visible notification board.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/reports/gpt-checkpoint-report-2026-05-08-pack23-p3d-notification-directus.md