GPT Review — P3D Pack 1 Phase 5C2A Probe Prompt Not Approved: Schema Hardcode

Date: 2026-05-11 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed:

• knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5c2a-readonly-publication-authority-ref-probe-prompt.md
• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c2a-publication-authority-probe-prompt-creation-report.md
• knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase5c2a-publication-authority-probe-2026-05-11.md

Verdict

Phase 5C2A probe prompt is NOT approved for Agent dispatch yet.

The probe asks the right questions, but it still assumes schema columns before resolving them. This repeats the exact pattern we just removed in Phase 5C1A/5C1: a prompt cannot probe schema by using unverified schema fields.

What is accepted

1. Probe scope is correct: read-only evidence for publication_authority_ref_value.
2. 5C1 COMMITTED PASS is correctly treated as prerequisite.
3. The probe must not decide the final value.
4. The 11 evidence questions are directionally right.
5. The Agent report target is correct.

Blocking issues

1. Direct doc_code usage in TAC publication queries

Q6 uses:

SELECT * FROM tac_publication
WHERE doc_code = 'DIEU-35';

DIEU-35 as pilot scope is allowed, but doc_code is a schema-sensitive column and must be resolved first.

2. Direct identity_profile usage in IU queries

Q3, Q8, and Q9 use identity_profile directly:

AND column_name = 'identity_profile'
SELECT id, identity_profile FROM information_unit
jsonb_object_keys(identity_profile)

The prompt must resolve iu_identity_profile concept first. If absent/ambiguous, report UNKNOWN and skip dependent queries.

3. dot_config key/value instruction is too loose

Q1 says identify key/value column, but Q4/Q5 should explicitly use a resolved concept map and report FIELD_ABSENT/AMBIGUOUS if key/value cannot be resolved.

4. Authority-like TAC column detection is prose only

Q2 says identify authority/issuer/owner/approved_by/enacted_by-like columns. The prompt should not let Agent choose silently. It should list all candidate columns with match_reason and label all as candidate_not_approved.

5. Function-source queries are acceptable, but analysis must be bounded

Using pg_proc.proname for fn_iu_birth_gate_layer1 and fn_iu_create is acceptable because these are named target functions, not data schema. However, the report must distinguish:

checks_key_presence
checks_value_non_null
validates_against_vocab
sets_authority_ref
requires_prebuilt_identity_profile
UNKNOWN

Agent must not infer beyond the source evidence.

Required patch

Patch prompt to rev2 with explicit semantic field resolution.

Minimum concept map:

dot_config_key
dot_config_value
tac_pub_doc_code
tac_pub_json_profile_candidates
tac_pub_authority_like_candidates
iu_pk
iu_identity_profile

Rules:

0 candidates found → FIELD_ABSENT
1 candidate found → RESOLVED
>1 candidates found → AMBIGUOUS_FIELD

Dependent queries must use only resolved concepts. If unresolved, report UNKNOWN and continue other sections.

Status

phase5c2a_probe_prompt_rev1=NOT_APPROVED_FOR_DISPATCH
reason=schema_columns_assumed_before_resolution
agent_dispatch_allowed=false
migration_allowed=false
seed_allowed=false
backfill_allowed=false
next_action=OPUS_PATCH_PHASE5C2A_PROBE_PROMPT_REV2_INTROSPECTION_FIRST