GPT Review — B3-A Readiness Rerun after B3-A1b — PARTIAL Accepted — 2026-05-12

Scope reviewed

Reviewed Agent report:

• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-system-b3a-readiness-rerun-after-b3a1b-report.md

Related SSOT / design references checked:

• knowledge/dev/architecture/species-taxonomy-complete.md
• knowledge/dev/architecture/birth-procedures.md
• knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4b-species-composition-registry-alignment-design.md
• knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-completion-architecture-design.md
• knowledge/dev/laws/dieu44-trien-khai/design/p3d-multidimensional-entity-db-architecture-design.md
• knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-standard-relationship-rules-8-confirmed-2026-05-12.md

Verdict

Status: PARTIAL_ACCEPTED

The readiness rerun is accepted as a read-only recomputation. It confirms that B3-A1a + B3-A1b closed the known species mapping gaps: missing_species_mapping_count=0 and missing_physical_table_count=0 for 73 BIRTH_REQUIRED + IN_SCOPE collections.

Important terminology / governance confirmations

• Species / loài is a meta-classification layer standing outside the 6 composition classes.
• The 6 composition classes remain the composition model; species is the 7th registry dimension / meta-layer.
• If a needed species is new, the correct sequence is: create/birth the species first in entity_species, then add species_collection_map. A mapping must not reference a non-existent species.
• dot_domain_rules → governance_infra did not need new-species birth because governance_infra already existed.
• Counts are evidence snapshots only and must not become gates.

Accepted findings from readiness rerun

• birth_required_total=73
• birth_required_in_scope=73
• already_wired_count=60 using contract function OID 39232.
• missing_species_mapping_count=0
• missing_physical_table_count=0
• variant_function_bindings_count=3
• birth_registry_recursive_risk=true
• no_mutation_performed=true

Interpretation of policy_unknown_count=57

The rerun report defines policy_unknown_count=57 as rows where description_policy='unclassified', not as missing B3-P coverage policy. B3-P coverage storage remains populated. This is a semantic/description-policy workstream and should not be conflated with coverage_status / coverage_scope_status readiness gates.

Remaining B3-A blockers

1) birth_registry self-birth recursion risk

birth_registry must not be wired naively to fn_birth_registry_auto; doing so can recursively insert into itself. It requires an explicit exemption or a designed self-birth guard.

2) Variant function bindings

The following use fn_birth_registry_auto_id rather than the contract function fn_birth_registry_auto:

• governance_relations
• law_dot_enforcement
• law_jurisdiction

A formal design decision is required: migrate to contract function or recognize/whitelist the variant as a contract sibling.

3) Trigger candidates now include newly mapped tables

The readiness rerun lists 10 missing-trigger collections, of which birth_registry is blocked by recursion. The remaining 9 may be clean candidates subject to design review:

• apr_action_types
• apr_approvals
• apr_request_types
• binding_registry
• dot_domain_rules
• field_type_equivalences
• normative_relations
• nrm_approval_rules
• nrm_doc_type_config

4) Duplicate trigger tech debt

18 collections have duplicate enabled triggers bound to the same contract function. This is out of scope for B3-A install but must be handled in a cleanup design, because it can double-emit birth rows.

5) Description policy classification

57 rows have description_policy='unclassified'. This is not the immediate B3-A blocker but should be classified in a separate PG-native policy/description workstream.

Process decision

Do not run trigger install yet.

The next designs must be assigned to Opus for proper drafting, then GPT review:

1. B3-A2 blocker-resolution design: birth_registry exemption/self-birth guard + variant function unification policy.
2. B3-A3 trigger install design for clean candidates after blockers are resolved.
3. B3-A-DUP duplicate trigger de-duplication design.
4. B3-DESC description_policy classification design for the 57 unclassified rows.

Immediate next action

Dispatch Opus to draft B3-A2 blocker-resolution design. GPT may continue to operate small read-only checks directly, but persistent design artifacts and architecture decisions must be authored by Opus and reviewed by GPT before execution.