GPT Final Approval — 23-P3D4C0Y 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-p3d4c0y-universal-phase2-poc-scope-plan-prompt.md rev2

Verdict

APPROVED FOR DISPATCH.

P3D4C0Y rev2 is dispatch-safe for a design/scope review. It correctly turns P3D4C0X into a practical Phase 2 PoC scope plan while preserving all hard boundaries.

This is not an implementation prompt. No runtime changes are allowed.

Accepted rev2 fixes

• PoC domain selection is now based on PG read-only inventory, not intuition.
• dot_config reuse is preferred; no duplicate event_config unless explicitly justified.
• event_type_registry enforcement is technically valid: FK, trigger validation, static generated CHECK, or registry-only deferred PoC. Prompt correctly states that PG CHECK cannot dynamically lookup registry rows.
• Pending strategy must be explicit: universal, per-domain, or hybrid.
• IU compatibility C-i is locked: no dual-write, no migration, no fn_iu_* behavior/signature change.
• Payload safety is schema-level: payload_classification, safe payload, denylist/allowlist, correlation/causation/idempotency policy.
• task vs review must be resolved with a concrete rule.
• Điều 43 alignment has explicit gate: ADDITIVE_ONLY, NEEDS_D43_REVIEW, or BLOCKED.
• Rollback/failure-mode design is required even though this is a scope plan.
• Verification/report fields are sufficiently complete for GPT/User review.

Dispatch instruction to Opus/Agent

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

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3d4c0y-universal-phase2-poc-scope-plan-prompt.md

Mục tiêu:
P3D4C0Y là PoC scope/design review only.

1. Read mandatory upstream documents.
2. Perform PG read-only inventory for candidate PoC domains.
3. Select the safest PoC domain with evidence.
4. Draft non-executable universal core schema sketches.
5. Define event_type_registry and valid enforcement mechanism.
6. Decide pending strategy: UNIVERSAL, PER_DOMAIN, or HYBRID.
7. Reuse dot_config unless proven incompatible.
8. Lock IU compatibility C-i: no dual-write, no migration, no fn_iu_* changes.
9. Absorb P3D4C1 lessons into universal design.
10. Define payload safety and idempotency rules.
11. Resolve task vs review stream boundary.
12. Apply Điều 43 alignment gate.
13. Design rollback/failure-mode plan.
14. Create design note:
    knowledge/dev/laws/dieu44-trien-khai/design/23-p3d4c0y-universal-phase2-poc-scope-plan.md
15. Upload report:
    knowledge/dev/laws/dieu44-trien-khai/reports/23-p3d4c0y-universal-phase2-poc-scope-plan-report.md

Upload report kể cả FAIL/NEEDS_MORE_INVENTORY/BLOCKED.

Hard boundaries for Agent

• No implementation.
• No PG mutation.
• No Directus mutation.
• No Nuxt code.
• No Hermes.
• No Codex dispatch.
• No external scheduler/tool/service.
• No runtime tables/functions/triggers.
• No iu_notification_* runtime changes.
• No old IU-specific P3D4C1 resume.
• No body/raw payload/vector/secret/personal data exposure.
• No activity-log creep.

Expected report fields

At minimum:

phase_status=PASS|FAIL|NEEDS_MORE_INVENTORY|BLOCKED
poc_domain_selected=<domain>
poc_domain_pg_inventory=PASS|FAIL|LIMITED
core_schema_designed=PASS|FAIL
event_type_registry_included=PASS|FAIL
registry_enforcement_mechanism=A|B|C|D
pending_strategy=UNIVERSAL|PER_DOMAIN|HYBRID
config_strategy=REUSE_DOT_CONFIG|NEW_TABLE_JUSTIFIED
iu_compat_ci_locked=PASS|FAIL
iu_no_dual_write=true
iu_no_row_migration=true
iu_fn_api_unchanged=true
p3d4c1_lessons_absorbed=PASS|FAIL
payload_safety_schema=PASS|FAIL
payload_denylist_enforced=PASS|FAIL
task_review_resolved=MERGED|SEPARATED|DEFERRED
dieu43_gate=ADDITIVE_ONLY|NEEDS_D43_REVIEW|BLOCKED
rollback_design=PASS|FAIL
not_activity_log=PASS|FAIL
no_pg_mutation=true
no_directus_mutation=true
no_nuxt_code=true
no_iu_runtime_change=true
no_p3d4c1_resume=true
next_required_pack=P3D4C1U_UNIVERSAL_CORE_IMPLEMENTATION_PROMPT_REVIEW|REVISION_REQUIRED|NEEDS_D43_REVIEW|BLOCKED

Review emphasis for execution

The most important evidence is not the candidate DDL itself. It is whether the selected PoC domain is live, low-risk, and suitable for proving the universal PG-to-outside signal substrate without disturbing the active IU notification runtime.

The implementation roadmap must preserve:

PG hot path = O(1) append only.
Derived work = worker/deferred.
Durable events/read state/routing = PG source of truth.
Directus = read projection only.
Nuxt = display assembly only.
IU runtime = untouched during C-i.

Next after Agent report

GPT/User review the P3D4C0Y design/report. If PASS, the next likely pack is:

P3D4C1U_UNIVERSAL_CORE_IMPLEMENTATION_PROMPT_REVIEW

No implementation is approved until that future prompt is separately reviewed and approved.