GPT Review — File 15 rev2 Option 1 Execution Pack

Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed: knowledge/dev/laws/dieu44-trien-khai/design/15-description-policy-option1-execution-pack.md rev 2

Verdict

PASS AS EXECUTION DESIGN. Do not execute yet. Next step: prepare exact execution prompt with channel separation.

File 15 rev2 resolved the major rev1 blockers:

• Legal/tooling gate added.
• DDL/Directus phase tightened.
• Function amendment made more execution-safe.
• H11 amendment made more exact.
• unclassified behavior clarified.
• Seed preflight/counting tightened.
• Insert smoke tests deferred.
• Law/docs patches separated as draft only.

Remaining caution before dispatch

Rev2 is acceptable as a design, but the execution prompt must split work by channel/tool authority:

Runtime / Claude Code channel

Claude Code may run read-only preflight and runtime DB changes if approved:

• inspect schema/tools;
• DDL on collection_registry if legal path remains clear;
• seed description_policy values;
• capture and replace fn_description_birth_guard;
• runtime verification queries;
• upload runtime report.

KB / Opus-GPT channel

H11 query document patch is a KB/document change, not necessarily a VPS DB action. It should either:

• be done by Opus/GPT via Agent Data after runtime column exists; or
• be explicitly included only if the agent has the correct KB tool authority.

Do not let Claude Code invent a KB update path.

Law / Constitution check

No blocker conflict in rev2 design.

• Đ20 / NT15: design-before-execution respected.
• Đ33/Đ36: DDL must use migration/approved runtime path and STOP if a schema DOT is found/required.
• Đ3: policy aligns with Description Governance and does not replace source descriptions.
• Đ4: birth guard change is designed with capture/restore.
• Đ43: H11 patch is specified but must be done through KB/document channel.
• Đ44: Pack 2B remains closed.

Required adjustments in the execution prompt, not necessarily file 15

1. Exact phase split

   • Phase R0–R5: runtime DB work by Claude Code.
   • Phase K1: H11a KB query patch by Opus/GPT/authorized KB tool after runtime success.
   • No law/guide patch in this execution.

2. Schema tooling preflight before DDL

   • Agent must inspect whether a schema migration/DOT tool exists.
   • If tool exists and is required, use it or STOP.
   • If no tool exists and migration psql is current legal path, print exact DDL and proceed only under approval.

3. Function replacement safety

   • Agent must print full new CREATE OR REPLACE FUNCTION before running it.
   • If source differs materially, STOP.

4. H11a patch not run by Claude Code unless KB authority is explicit

   • Runtime report should include before/after SQL counts using ad hoc query with policy filter.
   • H11a canonical KB file patch can be a follow-up handled by Opus/GPT.

5. Rollback clarity

   • If failure after DDL but before function: drop column or leave column with report depending failure point.
   • If function replacement fails: restore captured source immediately.
   • If Directus field absent: STOP before function/H11; do not manual insert directus_fields.

Directive to Opus/Ocus

Do not patch file 15 unless Opus believes channel separation must be added into the doc. Rev2 is acceptable as execution design.

Prepare a draft Claude Code runtime execution prompt based on file 15 rev2, but with these boundaries:

• Runtime DB only: DDL, seed, fn amend, runtime verification.
• H11a KB query patch: defer to separate Opus/GPT KB patch after runtime PASS, unless the prompt explicitly has KB authority.
• No law/guide patches.
• No Pack 2B, no IU rows, no entity_enrichment.
• Print exact DDL and exact full function replacement before executing.
• Upload report to: knowledge/dev/laws/dieu44-trien-khai/reports/description-policy-option1-runtime-execution-report.md
• HARD STOP after report.

After Opus drafts the execution prompt, GPT/User must review it before dispatch.

Current state

• File 15 rev2: PASS as design.
• Execution: not yet approved.
• Next: Opus drafts exact runtime execution prompt, not dispatch.