GPT Review — P3D Pack 1 Phase 5C1A 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-phase5c1a-readonly-species-schema-parent-probe-prompt.md
• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c1a-probe-prompt-creation-report.md
• knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase5c1a-species-schema-parent-probe-2026-05-11.md

Verdict

Probe prompt is NOT approved for Agent dispatch yet.

The purpose of this probe is to discover live schema. However, several probe queries assume schema columns before discovery. This is the same hardcode pattern we just removed from Phase 5 prompts.

What is accepted

1. The probe scope is correct: read-only schema + parent evidence.
2. The 12 questions are the right questions.
3. The report target is correct.
4. The probe should be medium effort.
5. The probe must not lock species values or parent decisions.

Blocking issue

The prompt directly uses these columns before resolving them live:

species_code
code
display_name
composition_level
management_mode
status
depth
parent_id
collection_name

Examples:

• Q6 collision check directly selects id, species_code, code, display_name, composition_level, management_mode, status.
• Q9 taxonomy query directly uses depth, parent_id, species_code, display_name.
• Q11 filters species_collection_map WHERE collection_name = 'information_unit'.
• Q12 filters birth_registry WHERE collection_name='information_unit' AND species_code IS NULL.

These fields are likely correct, but the entire point of the probe is to verify that. A probe cannot assume what it is probing.

Required patch

Patch the probe prompt to rev2 using introspection-first / field-resolution behavior:

1. Q1/Q2/Q3/Q4/Q5 run first and dump schemas/constraints.
2. Build a resolved-field map for semantic concepts:

species_identifier
species_entity_code
species_display_label
species_composition
species_management
species_status
species_depth
species_parent_ref
species_pk
mapping_collection_key
mapping_species_identifier
mapping_primary_flag
birth_collection_key
birth_species_identifier
birth_composition
birth_entity_key
birth_pk

3. For Q6/Q9/Q11/Q12, use only resolved fields.
4. If a required field is absent or ambiguous, report FIELD_ABSENT / AMBIGUOUS_FIELD and skip only that dependent query.
5. Do not let one optional missing field abort the whole probe.
6. Keep all candidate parents labelled candidate_not_approved.
7. Replace fuzzy phrase "similar" in Q10. Instead list all root rows and optionally tag deterministic evidence fields; GPT/User interprets.

Status

phase5c1a_probe_prompt_rev1=NOT_APPROVED_FOR_DISPATCH
reason=schema_columns_assumed_before_introspection
agent_dispatch_allowed=false
seed_allowed=false
backfill_allowed=false
migration_allowed=false
next_action=OPUS_PATCH_PHASE5C1A_PROBE_PROMPT_REV2_INTROSPECTION_FIRST