GPT Review — P3D Pack 1 Phase 2 DDL PASS + Phase 3 Directive

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

• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase2-ddl-extend-implementation-report.md
• Opus verification note for Phase 2

Verdict

PASS ACCEPTED.

Phase 2 DDL is complete and accepted.

Accepted evidence

• phase_status=PASS
• 10 approved columns added only:
  • information_unit.doc_code
  • information_unit.section_type
  • information_unit.section_code
  • unit_version.title
  • unit_version.description
  • unit_version.review_state
  • unit_version.provenance
  • unit_version.editor
  • unit_version.enacted_at
  • unit_version.updated_at
• information_unit: 16 → 19 columns.
• unit_version: 9 → 16 columns.
• Row counts unchanged: IU 12, UV 19.
• All new columns NULL on existing rows.
• No defaults.
• No FK/index/trigger added.
• No vector columns added.
• No data migration.
• No TAC modification.
• No Directus mutation.
• Gateway remains enforced.
• Gateway guard triggers remain enabled.
• fn_iu_create_plan reachable in dry-run mode.
• Rollback not needed.

Important findings from Phase 2

These are not Phase 2 failures, but they are blockers for any future TAC→IU backfill/migration.

1. Hash divergence

• Native IU unit_version.content_hash matches sha256(body::bytea).
• TAC tac_unit_version.content_hash matches neither md5(body) nor sha256(body::bytea) on samples.

Implication:

• Do not compare TAC and IU versions using naive hash equality.
• Do not recompute TAC hash during migration until the TAC hash rule is identified.
• Phase 3 must investigate hash rules before any backfill or drift verification.

2. law_unit planner resolution quirk

fn_iu_create_plan('...', 'law_unit', ...) returned:

resolved_unit_kind=design_doc_section
resolved_section_type=section

Implication:

• This may be policy aliasing or a bug.
• It is not a DDL issue.
• It is a blocker for using fn_iu_create as the canonical creator for 86 TAC law units until the behavior is explained or corrected.

Decision

Do not proceed directly to TAC→IU data migration.

Next phase must be:

P3D_PACK1_PHASE3_HASH_PLANNER_AND_COMPATIBILITY_DESIGN

Mode: design + read-only investigation prompt first. No migration.

Phase 3 purpose

Phase 3 must resolve or design around:

1. TAC hash algorithm / canonical hash policy.
2. IU planner unit_kind policy for law_unit.
3. Read-side compatibility/introspection layer design after Phase 2 schema extension.
4. Migration acceptance criteria for 86 TAC units, but no migration yet.

Status

pack1_phase2_ddl=PASS_ACCEPTED
pack1_phase3_required=true
implementation_allowed=false
next_action=OPUS_CREATE_PHASE3_DESIGN_AND_READONLY_INVESTIGATION_PROMPT