KB-5902

GPT Directive to Opus — P3D Pack1 Phase5C1A Probe rev2 Introspection First

4 min read Revision 1
directiveopusp3dpack1phase5c1aprobe-rev2introspection-first2026-05-11

GPT Directive to Opus — P3D Pack 1 Phase 5C1A Probe rev2: Introspection First

Date: 2026-05-11 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.7 Mode: PATCH PROBE PROMPT ONLY — no execution

0. Verdict

Probe prompt rev1 is not approved. It asks the right questions, but some queries assume schema columns before introspection.

Patch to rev2.

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase5c1a-probe-prompt-not-approved-schema-hardcode-2026-05-11.md
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

2. Target outputs

Patch prompt in place:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5c1a-readonly-species-schema-parent-probe-prompt.md

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c1a-probe-prompt-rev2-introspection-first-patch-report.md

3. Required fixes

3.1 Add explicit field-resolution map

After Q1–Q5 schema discovery, Agent must build a resolved-field map for semantic concepts:

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

Use deterministic status:

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

3.2 Patch Q6 collision check

Do not reference species_code, code, display_name, etc. directly.

Use resolved concepts:

species_identifier = proposed semantic name
species_entity_code = proposed entity code

If either is absent/ambiguous → collision check status = UNKNOWN, not guessed.

3.3 Patch Q9 taxonomy query

Do not reference depth, parent_id, species_code, display_name directly unless resolved.

If depth/parent/display concepts are absent/ambiguous, report whatever can be dumped with SELECT * and set taxonomy parent analysis = UNKNOWN.

3.4 Patch Q10 parent candidates

Remove fuzzy language such as:

similar
semantically covers

Instead:

  • list all root rows if species_depth resolves;
  • list all rows with resolved parent if species_parent_ref resolves;
  • label all rows candidate_not_approved;
  • GPT/User interprets which parent is appropriate.

3.5 Patch Q11/Q12 mapping and birth checks

Use resolved concepts:

mapping_collection_key
birth_collection_key
birth_species_identifier

If missing/ambiguous → report UNKNOWN and continue other sections.

3.6 Graceful degradation

Optional missing/ambiguous fields must not abort the entire probe. They should only mark dependent query as UNKNOWN.

The whole probe is blocked only if the core tables themselves are missing.

4. Hard boundaries

  • No Agent dispatch.
  • No DB write.
  • No seed.
  • No backfill.
  • No migration.
  • No DDL.
  • No function/trigger patch.
  • No species decision locked.

5. Expected Opus response

Return only:

  1. Patched probe prompt path.
  2. Patch report path.
  3. Top 5 fixes from rev1.
  4. Confirmation GPT/User review is required before Agent dispatch.

6. Status

phase5c1a_probe_prompt_rev2_patch_allowed=true
agent_dispatch_allowed=false
seed_allowed=false
backfill_allowed=false
migration_allowed=false
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase5c1a-probe-rev2-introspection-first-2026-05-11.md