KB-52A4

GPT Review — P3D Pack1 Phase5C1 rev4 Not Approved Missing Species Concepts

3 min read Revision 1
gpt-reviewp3dpack1phase5c1rev4not-approvedmissing-concepts2026-05-11

GPT Review — P3D Pack 1 Phase 5C1 rev4 Candidate Not Approved: Missing Species Concepts

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

  • knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5c1-species-mapping-qt001-backfill-prompt-DRAFT.md revision 12
  • knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c1-rev4-final-hardening-patch-report.md

Verdict

5C1 rev4 is not approved for Agent dispatch yet.

Rev4 correctly applied the requested final hardening: traceability, non-blocking advisory lock, collection_registry introspection, and rollback-reference typo fix.

However, the clean rewrite introduced a dispatch blocker: some columns used in verification are not resolved in the concept map.

What is accepted

  1. Traceability is clean rev4.
  2. Non-blocking advisory lock via pg_try_advisory_xact_lock is accepted.
  3. collection_registry introspection is accepted.
  4. G0-4/G0-5 use resolved collection_registry concepts.
  5. Rollback reference typo is fixed.
  6. Species identity remains correct.
  7. Transaction model remains correct.

Blocking issue

§4.3 uses unresolved species concepts

In §4.3, the prompt verifies:

<status col>
<depth col>
<parent_ref col>

But §2.2 concept resolution does not define these entity_species concepts.

Current §2.2 defines:

PK
identifier
entity_code
display
composition
management
dot_origin
prefix
description

Missing required concepts:

entity_species | status     | status
entity_species | depth      | depth
entity_species | parent_ref | parent_id

Because the prompt later uses <status col>, <depth col>, and <parent_ref col>, those concepts must be resolved before use. Otherwise Agent must either guess or fail late.

§2.4 also references status/depth by literal names

§2.4 says:

status_default = column_default for 'status'
depth_default  = column_default for 'depth'

This should reference the resolved concepts after §2.2, not literal names, e.g.:

status_default = column_default for resolved <status col>
depth_default  = column_default for resolved <depth col>

Required patch

Patch prompt to rev5.

Scope must be minimal:

  1. Add to §2.2 concept resolution:
entity_species | status     | status
entity_species | depth      | depth
entity_species | parent_ref | parent_id
  1. Change §2.4 default resolution to use resolved concepts instead of literal status / depth.

  2. Keep all rev4 fixes unchanged.

  3. Update visible status/title/footer to rev5 and metadata if possible.

Status

phase5c1_rev4_candidate=NOT_APPROVED_FOR_DISPATCH
reason=unresolved_status_depth_parent_ref_concepts
species_identity_locked=true
agent_dispatch_allowed=false
seed_allowed=false
backfill_allowed=false
migration_allowed=false
next_action=OPUS_PATCH_5C1_PROMPT_TO_REV5_ADD_MISSING_SPECIES_CONCEPTS
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase5c1-rev4-candidate-not-approved-missing-species-concepts-2026-05-11.md