GPT Review — P3D Pack 1 Phase 5C1A Probe PASS; Species Identity Locked for 5C1 rev1

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

• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c1a-species-schema-parent-probe-report.md
• knowledge/dev/laws/dieu44-trien-khai/reviews/opus-review-p3d-pack1-phase5c1a-probe-pass-species-identity-ready-2026-05-11.md

Verdict

Phase 5C1A probe PASS is accepted.

The probe executed correctly: introspection → concept resolution → evidence query. It produced the live schema and taxonomy evidence required to lock the 5C1 species identity.

Accepted evidence

• phase5c1a_probe_status=PASS
• no_mutation_performed=true
• phase2_resolution_complete=true
• phase2_field_absent_count=0
• phase2_ambiguous_count=0
• proposed_species_collision=false
• info_unit_mapping_exists=false
• info_unit_null_species_count=12
• fill_policy_matrix_complete=true
• entity_species: 18 columns discovered.
• species_collection_map: 13 columns discovered.
• birth_registry: 19 columns discovered.

Important live findings

1. Taxonomy is flat

All live species rows are:

depth = 1
parent_id = NULL

There is no depth=0 root row. Therefore, GPT locks the new species as a root-tier peer of existing species:

parent_id = NULL
depth = DB default 1

Do not create a new depth=0 root. Do not attach to an arbitrary parent.

2. entity_species required values are simple

Only these entity_species fields require explicit values:

code
species_code
display_name
composition_level

In addition, management_mode must be explicitly overridden because its DB default is governed, while Phase 5C1 needs observed.

3. species_collection_map has no UNIQUE constraint

Duplicate mappings are physically possible. Therefore, 5C1 rev1 must perform pre-insert dedupe checks and exact inserted-key capture. Do not add DDL in this pack.

4. composition_level and management_mode are free-text

No DB CHECK/enum protects the values. 5C1 rev1 must verify post-insert exact values.

GPT locked species identity for 5C1 rev1

Use these values in 5C1 rev1:

entity_species.code = SPE-IUA
entity_species.species_code = information_unit_atom
entity_species.display_name = Đơn vị Thông tin
entity_species.composition_level = atom
entity_species.management_mode = observed
entity_species.status = DB default active
entity_species._dot_origin = DOT:QT-005-P3D-PACK1-5C1
entity_species.parent_id = NULL
entity_species.depth = DB default 1
entity_species.prefix = IUA
entity_species.kg_metadata = DB default {}
entity_species.description = Loài cho collection information_unit dưới chiến lược D3 hybrid; IU là atomic text unit, hierarchy lưu metadata/edges hậu pilot.

For species_collection_map:

species_collection_map.species_code = information_unit_atom
species_collection_map.collection_name = information_unit
species_collection_map.is_primary = DB default true
species_collection_map.discriminator_* = NULL

Required 5C1 rev1 safety gates

5C1 rev1 must include:

1. Schema introspection and concept resolution before writes.
2. Collision check for both code=SPE-IUA and species_code=information_unit_atom.
3. Dedupe check: no existing mapping for collection_name=information_unit.
4. Exact-key capture for inserted species row and inserted mapping row.
5. SELECT target birth rows before UPDATE.
6. Backfill only captured target birth rows.
7. Post-insert verification for exact values, especially management_mode=observed and composition_level=atom.
8. Post-backfill verification: captured rows now have species_code=information_unit_atom and composition_level=atom.
9. Rollback by captured keys only.
10. No TAC migration in 5C1.

Status

phase5c1a_probe=PASS_ACCEPTED
species_identity=LOCKED_FOR_5C1_REV1
parent_strategy=NULL_DEPTH_DEFAULT_1
phase5c1_rev1_allowed=true
agent_dispatch_allowed=false_until_GPT_FINAL_REVIEW_AND_USER_GO
seed_allowed=false_until_5C1_REV1_APPROVED
backfill_allowed=false_until_5C1_REV1_APPROVED
migration_allowed=false
next_action=OPUS_PATCH_5C1_PROMPT_TO_REV1_DISPATCH_CANDIDATE