GPT Review — 24-P3B-FU Execution Result and P3C2 Re-run Directive

Date: 2026-05-07
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Context: Opus reviewed Agent P3B-FU execution report. User asks for next directive.

Verdict

P3B-FU PASS. Agent and Opus handled the issue correctly.

No supplemental P3B-FU Agent action is needed.

Accepted execution evidence

• fn_iu_verify_invariants(text) has been generalized.
• i3_anchors_exact now checks the current anchored UV via version_anchor_ref.
• Birth checks still use version_seq=1.
• A1–A4 pre-COMMIT assertions passed.
• T1–T10 passed.
• IU/UV counts unchanged: 6 → 6 / 6 → 6.
• P3C1 hashes unchanged.
• Function hash changed as expected: body replaced.
• Owner remained directus.
• Function remained STABLE / invoker, matching original runtime state.
• search_path/config preserved.

Important correction

The P3B-FU prompt rev3 contained an incorrect body declaration copied from a write function style:

VOLATILE SECURITY DEFINER

But the original fn_iu_verify_invariants(text) was read-only style:

STABLE
SECURITY INVOKER / prosecdef=false

Agent correctly detected this via T6 exact metadata check, corrected the replacement to preserve the original metadata, and then passed all tests.

This confirms GPT’s prior requirement for exact owner/security/config comparison was necessary.

Opus has patched the archival prompt to rev4 for record accuracy. Since runtime execution already PASSed with the corrected function, no additional execution is required for P3B-FU.

Decision

Proceed to re-dispatch P3C2 rev7.

The original P3C2 failure was caused by the old birth-only invariant. That blocker is now removed.

Directive to Opus / Agent

Re-run the approved P3C2 prompt:

knowledge/dev/laws/dieu44-trien-khai/prompts/23-p3c2-iu-apply-edit-functions-prompt.md

Report path:

knowledge/dev/laws/dieu44-trien-khai/reports/23-p3c2-iu-apply-edit-functions-report.md

Important:

• This is a re-run after invariant generalization.
• Do not change P3C2 function bodies unless the prompt itself instructs it.
• Do not patch P3C2 before re-run unless new runtime evidence appears.
• Upload report even on FAIL/CRITICAL.

Hard boundaries for P3C2 re-run

• No table DDL.
• No schema changes.
• No trigger changes.
• No gateway changes.
• No notification log implementation.
• No vector mutation.
• No cleanup / no pilot deletion.
• No direct IU/UV writes outside fn_iu_apply_edit_draft.
• Do not alter P3C1 functions.

Expected P3C2 PASS evidence

• phase_status=PASS.
• T1–T19 all PASS.
• fn_iu_apply_edit_draft(uuid,text,text) created.
• fn_iu_edit(text,text,text,text,text,text) created.
• T1 apply creates exactly one new unit_version.
• T11 wrapper creates/applies exactly one new unit_version.
• No new information_unit row.
• IU anchors move correctly.
• content_anchor_ref = new_uv_id::text verified.
• DRAFT_A becomes applied.
• DRAFT_B becomes stale_base.
• Apply/system comment inserted.
• Invariant JSON from successful apply has all_pass=true.
• Direct wrong-door IU write remains gateway-blocked.
• P3C1 function hashes unchanged.
• Source checks pass.
• Official test rows retained.
• next_required_pack=P3C3_NATURAL_SAVE_ROUTER_BEFORE_BROAD_AGENT_USE.
• 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.

Next after P3C2 report

If P3C2 PASS:

1. Implement P3C3 fn_iu_save natural router.
2. Switch broad-use policy toward require_review after P3C3 validation.
3. Then design P3D notification outbox before Hermes production.

If P3C2 FAIL again:

• Do not improvise.
• Preserve state/report.
• Review exact failing tests and root cause before any patch.