GPT Final Approval — 23-P3C4 Policy + Agent Context Prompt rev5

Date: 2026-05-07
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Reviewed: knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3c4-iu-policy-and-agent-context-prompt.md rev5

Verdict

APPROVED FOR DISPATCH.

P3C4 rev5 resolves the rollback ordering and upload verification issues. It may now be executed.

Accepted rev5 fixes

• Rollback decision now occurs after DB tests and context/anchor upload gate.
• Two-part execution is explicit:
  • Part A: DB shell — switch + tests + temp content generation;
  • Part B: Agent Data upload/readback for context pack and P3D anchor;
  • Part C: rollback decision + final report.
• Upload statuses are separated:
  • context_pack_upload;
  • p3d_anchor_upload;
  • combined context_upload.
• Final report includes policy_before, policy_after_switch, and policy_final after any rollback.
• Already-switched failure path does not rollback to auto_apply and reports NOT_RUN_ALREADY_SWITCHED.
• P3D notification/read-state requirement is recorded as a design anchor, not implemented in P3C4.

Dispatch instruction

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

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3c4-iu-policy-and-agent-context-prompt.md

Mục tiêu:
1. Chuyển default IU edit policy từ auto_apply sang require_review.
2. Verify require_review behavior trên dedicated pilot IU.
3. Upload + verify Agent context pack.
4. Upload + verify P3D notification/read-state design anchor.

Report tại:
knowledge/dev/laws/dieu44-trien-khai/reports/23-p3c4-iu-policy-and-agent-context-report.md

Context pack path:
knowledge/dev/laws/dieu44-trien-khai/context-packs/iu-agent-front-door-context.md

P3D anchor path:
knowledge/dev/laws/dieu44-trien-khai/design/23-p3d-notification-outbox-read-state-design-anchor.md

Upload report kể cả FAIL/CRITICAL.

Hard boundaries for Agent

• No function changes.
• No table DDL.
• No trigger/gateway changes.
• No vector mutation.
• No notification implementation in P3C4.
• No cleanup/pilot deletion.
• Only one dot_config key may change:
  • iu_edit.policy.default_mode.
• Rollback may only restore that same key if this pack changed it and tests/upload fail.
• No raw rollback instructions in context pack.

Expected PASS evidence

Report should include:

• phase_status=PASS;
• policy_action=UPDATED_AUTO_APPLY_TO_REQUIRE_REVIEW or SKIPPED_ALREADY_REQUIRE_REVIEW;
• policy_before=<...>;
• policy_after_switch=require_review;
• policy_final=require_review;
• rollback_status=NOT_RUN unless idempotent/failure path applies;
• T1–T8 PASS;
• dedicated pilot IU created;
• existing save under fn_iu_save(..., mode='auto') returns draft_created_review_required after switch;
• draft created under require_review does not create UV until reviewer apply;
• reviewer apply creates official version;
• mode=draft creates draft only;
• comment free-flow returns comment_added;
• wrong-door direct write remains gateway-blocked;
• protected function hashes unchanged;
• protected function count remains 10;
• context_pack_upload=PASS;
• p3d_anchor_upload=PASS;
• context_upload=PASS;
• context pack readback verified;
• P3D anchor readback verified;
• notification_design=PG_NATIVE_EVENT_OUTBOX_WITH_PER_ACTOR_READ_STATE;
• notification_implementation=DEFERRED_P3D;
• hard boundaries honored.

Next after Agent report

If P3C4 PASS:

1. Review execution report.
2. Declare Pack 23 minimum edit workflow complete for limited use.
3. Do not start Hermes production yet.
4. Proceed to P3D design/execution for PG-native notification outbox + per-actor read state.

Note on notification design

The User’s requested notification model is accepted:

• dedicated lightweight event lists;
• separate comment/draft/update-apply event types;
• per-actor read state, not global read flag;
• GPT read state does not overwrite Opus read state;
• PG triggers/functions should create events;
• external automation such as Hermes consumes PG queues later.

P3C4 only records the design anchor. Implementation is deferred to P3D.