GPT Final Approval — 23-P3D4C2U Table Module Read-Only Exposure Prompt

Date: 2026-05-08
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Reviewed: knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d4c2u-table-module-readonly-exposure-prompt.md

Verdict

APPROVED FOR DISPATCH.

The prompt correctly follows the User's governance principle: when work touches another law/domain/function, reuse and obey the specialized law/module. If the existing module is insufficient, stop and repair/extend the shared module, not build a parallel solution.

P3D4C2U is therefore not a notification UI task. It is a Table Module / Assembly Module reuse and inventory task.

Accepted approach

Use the existing path:

PG projection/schema
→ Directus collection/permission/metadata
→ table_registry configuration
→ DirectusTable / existing Nuxt UI render

Do not invent:

• bespoke notification UI;
• notification-specific Nuxt page/component;
• custom Directus screen;
• parallel context/relationship graph outside Điều 43;
• alternate table rendering system outside Table Module.

Specialized-law principle to carry into execution

The execution agent must apply this rule:

1. If Table Module already covers the need, use it.
2. If Table Module is incomplete, stop and recommend Table Module generic extension/repair.
3. If Điều 43 already provides relationship/context/graphic information, use/align with it.
4. If Điều 43 is insufficient, stop and request Điều 43 review/amendment.
5. If Directus/DOT conventions already exist, reuse them.
6. If a required capability would duplicate another law's jurisdiction, stop and escalate.
7. No workaround, no double system, no local special-case solution for notification.

Dispatch instruction to Opus/Agent

Đọc prompt từ KB rồi thực hiện:

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d4c2u-table-module-readonly-exposure-prompt.md

Mục tiêu:
P3D4C2U là read-only inventory/design review for exposing the universal event core through the existing Table Module / DirectusTable path.

1. Read mandatory documents.
2. Inventory Table Module / Assembly Module path.
3. Confirm system_issues registry precedent.
4. Inventory DirectusTable, table_registry, generic table route/page.
5. Inventory Directus/DOT read-only exposure path.
6. Inventory live universal event schema.
7. Review Điều 43 graphic/context-pack relevance.
8. Decide display source: raw event_outbox vs PG view projection vs blocked.
9. Draft table_registry declaration if viable.
10. Draft minimal DOT read-only exposure plan if viable.
11. Determine whether Nuxt requires no code, registry declaration only, generic extension, or blocked.
12. Create design note:
    knowledge/dev/laws/dieu44-trien-khai/design/23-p3d4c2u-table-module-readonly-exposure-design.md
13. Upload report:
    knowledge/dev/laws/dieu44-trien-khai/reports/23-p3d4c2u-table-module-readonly-exposure-report.md

Upload report even on FAIL/BLOCKED/NEEDS_MORE_INVENTORY.

Hard boundaries for Agent

• No implementation.
• No PG mutation.
• No Directus mutation.
• No Directus click-config.
• No Nuxt code.
• No bespoke notification UI.
• No notification-specific Nuxt page/component.
• No Nuxt business logic.
• No Nuxt direct PG.
• No Directus write/mark-read in this pack.
• No UI outside Table Module / Assembly Module path.
• No body/raw payload/vector/secret exposure.
• No IU runtime change.
• No worker/cron.
• No Điều 43 machinery duplication.
• No modification to Điều 43 context-pack builder/verify.

Required decision gates

If DirectusTable / table_registry / generic route is ready:

recommendation=PROCEED_TO_DOT_TABLE_REGISTRATION_PROMPT

If the shared Table Module is incomplete:

recommendation=NEEDS_GENERIC_TEMPLATE_EXTENSION

If Điều 43 relationship/graphic support is needed but not available:

recommendation=NEEDS_D43_REVIEW

If the only way forward is bespoke notification UI:

recommendation=BLOCKED

Expected outcome

The best outcome is proof that universal event visibility is just another registered table, like system_issues, using the existing shared Table Module path.

If this proof fails, the next work must repair/extend the shared module, not create a one-off notification interface.