GPT Decision — Pause P3C2 for Natural Router Policy

Date: 2026-05-07
Decision-maker: GPT-5.5 Thinking / Incomex Hội đồng AI
Context: User has not dispatched Agent for P3C2 yet and asks whether to run P3C2 as approved or pause to add natural router design first.

Decision

Pause P3C2 dispatch. Do not run Agent yet.

P3C2 rev6 is technically approved, but the User identified a deeper operational problem: stateless AI/Agents cannot be expected to remember create-vs-edit-vs-apply rules.

Since P3C2 has not been executed yet, it is safer to add a small design/UX correction now rather than after creating official write functions with a potentially confusing default interface.

Reason

Current lower-level function set is correct as building blocks:

• fn_iu_create — create new IU official version 1;
• fn_iu_create_edit_draft — create edit draft;
• fn_iu_comment — comment naturally;
• fn_iu_apply_edit_draft — apply draft to official version;
• fn_iu_edit — wrapper create+apply depending on policy.

But the agent-facing surface is still rule-dependent.

The AI/Agent should not need to remember:

• whether the address exists;
• whether to call create or edit;
• whether the edit becomes draft or official;
• when apply is needed;
• which function is safe for general use.

Required design correction

Introduce a natural front-door concept before P3C2 execution is finally dispatched:

P3C3 — IU Natural Save Router

Proposed AI-facing function:

fn_iu_save(
  p_address text,
  p_body text,
  p_actor text,
  p_title text DEFAULT NULL,
  p_reason text DEFAULT NULL,
  p_mode text DEFAULT 'auto'
) RETURNS jsonb

Agent-facing rule:

To save content for an information unit address, call fn_iu_save(...).

System behavior:

1. If the address does not exist:

   • call/use fn_iu_create path;
   • create official version 1;
   • return created_official.

2. If the address exists:

   • do not direct-write official content;
   • create edit draft;
   • if policy/mode allows auto-apply, call apply;
   • otherwise return draft_created_review_required.

3. If the body is unchanged:

   • return no_change.

4. If unsafe/ambiguous:

   • return status + guidance + next_action.

Immediate instruction to Opus

Before P3C2 dispatch, Opus should review and patch the design minimally:

1. Do not run P3C2 yet.
2. Create a short design note or patch section that defines the natural router policy:
   • fn_iu_save as future/default AI front-door;
   • first creation is official;
   • edits to existing official content go through draft/apply policy;
   • fn_iu_edit should be treated as internal convenience / wrapper, not the final general AI front-door.
3. Evaluate whether iu_edit.policy.default_mode should stay auto_apply or be changed to require_review before broad use.
4. Decide whether P3C2 rev6 itself needs a small prompt patch to add this note/report field, or whether P3C3 should be the immediate next pack after P3C2 PASS.
5. Return recommendation for GPT/User review. Do not dispatch.

GPT recommendation

• Keep P3C2 function bodies mostly as-is, because fn_iu_apply_edit_draft is still required.
• Do not treat fn_iu_edit as the final AI-facing interface.
• Add a report/roadmap field:
  • next_required_pack=P3C3_NATURAL_SAVE_ROUTER_BEFORE_BROAD_AGENT_USE
• Consider changing default policy to require_review before real operations, while allowing auto_apply only for pilots or low-risk IUs.

Summary

Technically, P3C2 rev6 is ready. Operationally, it should pause because the system still requires too much memory from stateless AI agents. Add the natural router layer/policy now, while no runtime function has been created yet.