GPT Review — P10A-1 Read-only Dispatch Prompt

Date: 2026-04-29

Verdict

APPROVE WITH MICRO-PATCH — not ready to dispatch as-is.

The prompt is directionally correct and aligned with P10A-1: read-only schema/source discovery and segmentation candidate generation for Điều 35. However, a few lines can cause scope drift or execution errors.

Law / constitutional check

No conceptual conflict after micro-patch.

• Hiến pháp / Zero Trust: aligned if all schema/vocab/source facts are verified, not assumed.
• Điều 38 / LSL-01: aligned; this is segmentation candidate work only.
• Điều 33 / PostgreSQL SSOT: aligned; no production write in P10A-1.
• Gate separation: aligned only if no insert/render execution and no P10A-2 actions occur.

Accepted points

• Objective is correct: schema discovery + source snapshot + segmentation candidate + render plan.
• PASS/FAIL table is useful.
• Hard exclusions are mostly correct.
• Trigger firing is correctly excluded.
• Report path is specified.

Required micro-patches before dispatch

Patch 1 — Remove Authorized: Execute immediately

The artifact is still under GPT review. Change header to:

Status: DRAFT — GPT review; execute only after GPT PASS + User GO

or, if User later authorizes:

AUTHORIZED — User GO <date/time>

Do not pre-authorize inside a draft.

Patch 2 — Fix vocab table names

The prompt says query tac_section_type, tac_publication_type, tac_lu_lifecycle, etc. Actual Gate C seed tables use _vocab names, including:

• tac_section_type_vocab
• tac_publication_type_vocab
• tac_lu_lifecycle_vocab
• tac_uv_lifecycle_vocab
• tac_pub_lifecycle_vocab
• tac_review_state_vocab
• tac_cs_lifecycle_vocab

Use exact names from schema discovery; do not hardcode shortened names.

Patch 3 — Replace GIT COMMIT requirement

GIT COMMIT kết quả cuối is not appropriate for P10A-1 unless a tracked repository file is intentionally modified. The required source of truth for this step is Agent Data KB report upload.

Replace with:

• upload report to KB;
• if any local files are created on VPS, include path/SHA in report;
• no git commit unless explicitly required by an existing repo workflow and GPT/User authorizes it.

Patch 4 — Clarify role/database verification without assuming role is final

The prompt says DB=directus, role=directus. For P10A-1 read-only this may be acceptable, but it should still be verified, not assumed.

Use:

• connect to database directus;
• run SELECT current_database(), current_user;;
• if using role directus, record it as read-only discovery role;
• do not infer this role is valid for P10A-2 insert.

Patch 5 — Do not require “all 14 tables” constraints if only core pilot tables need detail

It is fine to snapshot all 14, but PASS should not fail merely because an irrelevant vocab table has no FK/CHECK. Better wording:

• full column snapshot for all 14 tac_* tables;
• detailed NOT NULL/FK/CHECK/trigger/privilege discovery for 6 core/member tables and relevant vocab/config tables;
• missing expected target table/constraint = FAIL.

Directive to Opus 4.6

Patch the P10A-1 dispatch prompt with the five micro-patches above.

Do not expand scope.

Return the patched P10A-1 prompt for GPT final review. After GPT PASS, User can authorize dispatch.

Current state

• P9 foundation: complete.
• P10A v0.4: conceptually ready after micro-patch.
• P10A-1 dispatch prompt: needs micro-patch.
• No production core/member insert authorized.