GPT Clarification — Notification Display vs AI-Readable Notification

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

User concern

User correctly noted that passing the notification display checkpoint should not only mean a backend/table route exists. For practical supervision, users and AIs need a readable place to inspect notifications.

Current confirmed state

The P3D4C2U report confirms:

tbl_event_outbox.status=published
/knowledge/registries/event_outbox HTTP 200
notification_display_checkpoint=unblocked
permission #1483 safe
unsafe fields denied
runtime field deny smoke PASS

Therefore, there is already a concrete web path to inspect notifications:

/knowledge/registries/event_outbox

This is the minimal read-only table view, not yet a dedicated AI-readable notification board.

Important distinction

There are two levels:

Level 1 — Display checkpoint (DONE)

A generic DirectusTable-backed registry view exists and is safe:

/knowledge/registries/event_outbox

This lets User inspect notification events through the standard registry/table UI.

Level 2 — Operational notification reader / AI board (NOT DONE)

The design history references per-actor read state and board functions such as:

fn_event_unread
fn_event_mark_read
fn_iu_notification_board(actor)

But the current completed P3D4C2U checkpoint did not implement a dedicated AI-readable notification inbox, unread board, mark-read workflow, or role-specific dashboard. Those are still separate work.

Next recommendation

Before returning to the main Information Unit text-as-code stream, run a small validation / bridge pack:

P3D4C2V_NOTIFICATION_READER_TEST_AND_AI_BOARD_REQUIREMENT

Scope:

1. User manually opens /knowledge/registries/event_outbox and verifies readability.
2. Agent verifies route from user-facing public/Nuxt side.
3. Agent checks whether existing functions such as fn_event_unread / fn_event_mark_read / board-like functions exist for universal event core.
4. Agent determines whether current table view is enough for Phase 1 supervision or whether a minimal AI-readable board/API is required before resuming text-as-code.
5. No new UI, no deploy, no schema mutation unless explicitly approved later.

Provisional conclusion

Do not claim the AI notification reader is complete. Claim only:

notification display checkpoint = PASS
minimal table route = available
AI-readable operational inbox/board = needs validation/design before or alongside text-as-code resume

Current status

minimal_notification_path=/knowledge/registries/event_outbox
notification_display_checkpoint=unblocked
ai_readable_notification_board_status=not_yet_confirmed
recommended_next=P3D4C2V_NOTIFICATION_READER_TEST_AND_AI_BOARD_REQUIREMENT