KB-1C77

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

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

GPT Directive to Opus — P3D Pack 1 Phase 5C2A 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

Phase 5C2A probe prompt rev1 is not approved. Patch to rev2 with introspection-first / concept-resolution behavior.

Open:

P3D_PACK1_PHASE5C2A_PROBE_REV2_INTROSPECTION_FIRST

1. Required reading

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

2. Target outputs

Patch prompt in place:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5c2a-readonly-publication-authority-ref-probe-prompt.md

Create patch report:

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

3. Required fixes

3.1 Add explicit field-resolution phase

After schema introspection, resolve these concepts:

dot_config_key
dot_config_value
tac_pub_pk
tac_pub_doc_code
tac_pub_json_profile_candidates
tac_pub_authority_like_candidates
iu_pk
iu_identity_profile

Use deterministic status:

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

For authority-like candidates, do not choose one. Return all candidate columns with match_reason, labelled candidate_not_approved.

3.2 Patch Q4/Q5

Use resolved dot_config_key and dot_config_value. If key unresolved, report UNKNOWN.

3.3 Patch Q6/Q7

Use resolved tac_pub_doc_code; do not use literal doc_code as a column. DIEU-35 remains allowed as pilot scope constant.

If tac_pub_doc_code unresolved, report UNKNOWN and still dump table schema only.

3.4 Patch Q8/Q9

Use resolved iu_identity_profile; do not use literal identity_profile before resolution.

If unresolved or not jsonb, report UNKNOWN.

3.5 Bounded function-source analysis

For fn_iu_birth_gate_layer1 and fn_iu_create, report only bounded booleans/enums:

checks_authority_key_presence=true|false|UNKNOWN
checks_authority_value_non_null=true|false|UNKNOWN
validates_authority_against_vocab=true|false|UNKNOWN
sets_authority_ref=true|false|UNKNOWN
requires_prebuilt_identity_profile=true|false|UNKNOWN

Do not infer final authority value.

3.6 Graceful degradation

Missing optional fields should not abort the probe. They should mark dependent evidence as UNKNOWN. Probe is BLOCKED only if core tables/functions cannot be inspected.

4. Hard boundaries

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

5. Expected Opus response

Return only:

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

6. Status

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