GPT Review — P3D Pack 1 Phase 4B Opus Design Not Approved; Legal Alignment Required

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

• knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4b-species-composition-registry-alignment-design.md
• knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4b-readonly-species-composition-registry-discovery-prompt.md
• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4b-species-composition-design-and-discovery-prompt-report.md
• knowledge/dev/architecture/species-taxonomy-complete.md
• knowledge/dev/architecture/composition-level-law.md
• knowledge/dev/architecture/birth-registry-law.md
• knowledge/dev/laws/dieu29-classification-law.md
• knowledge/dev/architecture/birth-procedures.md
• knowledge/ops/processes/birth-process-v1.md

Verdict

NOT APPROVED FOR AGENT DISPATCH.

Opus is directionally correct that IU must align with species/composition/birth-registry infrastructure before TAC→IU migration. However, the current Phase 4B design is not yet sufficiently anchored to the old laws and risks making new decisions before proving how the old system requires the decision to be made.

The User's concern is accepted: Phase 4B must not create a new birth/classification universe. It must reconcile IU/TAC with existing laws first.

What Opus did well

1. Correctly identified IU/TAC are not fully wired into species/composition registry.
2. Correctly separated birth core, registry alignment, and DOT enrichment.
3. Correctly kept the prompt read-only.
4. Correctly used introspect-first posture after the entity_species.species_name error.
5. Correctly noted current IU birth rows with NULL species/composition require a backfill decision.

Blocking issues

1. Legal alignment is incomplete

Opus read Species Taxonomy and Composition Level Law, but the design needs an explicit compliance matrix against at least:

• Điều 0-B — Composition Level Law;
• Điều 0-G — Birth Registry Law;
• Điều 29 v2.0 — one classification system, no parallel admin systems;
• Birth Procedures v3.1 / QT-001/QT-003R;
• Species Taxonomy v1.2;
• current live Phase 3/4 reports.

Without this matrix, Phase 4B may still optimize locally and violate old architecture.

2. New species recommendation is premature

Design recommends creating a new species (e.g. SPE-IUL) before discovery proves:

• whether existing live species already fits;
• whether IU should be one species or multiple species by unit_kind;
• how Điều 29's one-system principle expects collection classification;
• whether species is collection-level, unit-kind-level, or entity-level for IU.

Recommendation must be downgraded to option analysis pending discovery and legal matrix.

3. Composition recommendation atom is plausible but not proven

The claim that law_unit is atom may be right, but it must be derived from Điều 0-B criteria and tested against actual TAC/IU containment semantics:

• Does a migrated IU law_unit contain child IU units through parent_or_container_ref?
• Is parent/child hierarchy structural containment or document tree ordering?
• Does tac_publication_member/render_order represent building/molecule context outside the unit?

Do not lock atom before this analysis is explicit.

4. Birth backfill policy bypasses formal birth procedures

Design recommends updating 12 existing birth_registry rows. That may be correct, but it must be framed under QT-001/QT-003R/backfill procedures, not as a simple ad-hoc update.

Backfill must follow the existing birth law/process if later implemented.

5. Discovery prompt still assumes some column names and table names after claiming introspect-first

The prompt introspects columns, but later queries use fixed columns such as collection_name, governance_role, species_code, migration_state, source_collection, target_collection, etc. This may be acceptable if gated by D0, but currently it is not executable-adaptive. Since the prompt is read-only, this is not a mutation risk, but it can still fail and give incomplete evidence.

6. Old law says metadata changes should avoid code changes

Điều 0-G emphasizes: when system runs, do not change code; change metadata. Phase 4B must encode this as a core decision rule before considering birth-gate patching.

Decision

Do not dispatch current Phase 4B discovery prompt.

Opus must produce a legal-alignment addendum and patch the discovery prompt to focus first on law/runtime reconciliation, not candidate implementation.

Required next work

Open:

P3D_PACK1_PHASE4B_LEGAL_ALIGNMENT_PATCH

Mode:

LEGAL_ALIGNMENT_ADDENDUM + PATCHED_READONLY_PROMPT_ONLY

No agent dispatch yet.

Status

phase4b_design=NOT_APPROVED_YET
phase4b_discovery_prompt=NOT_APPROVED_FOR_DISPATCH
migration_allowed=false
species_seed_allowed=false
composition_seed_allowed=false
next_action=OPUS_PATCH_PHASE4B_WITH_OLD_LAW_COMPLIANCE_MATRIX