GPT Review — 23-P3C3 Natural Save Router Design Note

Date: 2026-05-07
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Reviewed: knowledge/dev/laws/dieu44-trien-khai/design/23-p3c3-iu-natural-save-router-design-note.md

Verdict

P3C3 direction accepted. Small clarification required before P3C2 dispatch.

Opus correctly captured the operational problem: AI/Agents cannot be expected to remember create-vs-edit-vs-apply rules. A natural router is needed.

Accepted points

1. fn_iu_save as the future/default content-saving front door is accepted.
2. First creation may be official immediately.
3. Existing IU edit should go through draft/apply policy.
4. Broad-use default should lean toward require_review; auto_apply is for pilot/low-risk or explicitly trusted flows.
5. fn_iu_edit should become an internal convenience wrapper, not the final AI-facing front door.
6. Comment should remain free-flow and should not require approval.

Comment clarification

User clarified that comments do not need approval. This is accepted.

Comment is not content mutation. Comment is feedback/audit/discussion. AI/Agent should be able to comment naturally and repeatedly. Timestamp + actor stamp handle traceability.

Do not add comment approval workflow.

Caution on mode='comment' inside fn_iu_save

Opus’s idea to include mode='comment' in fn_iu_save is creative, but GPT recommends treating it as an optional alias, not the primary interface.

Reason: save and comment are different intents. Overloading body to mean either official content or comment text can create confusion.

Preferred AI-facing interface:

SELECT fn_iu_save(address, body, actor, title, reason, mode); -- content save/create/edit
SELECT fn_iu_comment(address, actor, comment);                -- free-flow comment

This is still simple: two obvious buttons, not many rules.

If P3C3 later includes mode='comment', it should simply delegate to fn_iu_comment and must not require approval.

P3C2 dispatch decision

P3C2 should not be rewritten to implement fn_iu_save. That belongs to P3C3.

However, before dispatching P3C2, patch P3C2 prompt/report fields so the next pack is P3C3, not P3D.

Required P3C2 rev7 small patch:

1. Change final report/readiness next pack from:

   • next_required_pack=P3D_NOTIFICATION_OUTBOX_BEFORE_HERMES_PRODUCTION

   to:

   • next_required_pack=P3C3_NATURAL_SAVE_ROUTER_BEFORE_BROAD_AGENT_USE

2. Add:

   • deferred_after_p3c3=P3D_NOTIFICATION_OUTBOX_BEFORE_HERMES_PRODUCTION
   • comment_policy=FREE_FLOW_NO_APPROVAL
   • fn_iu_edit_interface=INTERNAL_CONVENIENCE_NOT_FINAL_AI_FRONT_DOOR

3. Preserve notification roadmap reference:

   • notification_roadmap=knowledge/dev/laws/dieu44-trien-khai/design/23-p3d-notification-outbox-roadmap-note.md

4. No function body changes unless required by this reporting update.

Recommended order now

1. Patch P3C2 rev7 with roadmap/report wording only.
2. Dispatch P3C2 Agent.
3. Review P3C2 report.
4. Implement P3C3 natural save router.
5. Then implement P3D notification outbox before Hermes production.

Summary

P3C3 is needed, but it should not block creation of the apply machinery. P3C2 remains necessary as the engine. P3C3 becomes the user/agent-facing steering wheel. Comments remain free-flow, timestamped, actor-stamped, and not approval-gated.