GPT Review — 12a + File 12 rev2 after Điều 20 Context Graph Gate

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

• knowledge/dev/laws/dieu20-thiet-ke-truoc-trien-khai.md rev 12 — v1.2 FINAL with mandatory Context Graph Gate in §0
• knowledge/dev/laws/dieu44-trien-khai/design/12a-iu0-pack2a-description-birth-contract-decision-note.md rev 1
• knowledge/dev/laws/dieu44-trien-khai/design/12-iu0-pack2a-dot-governance-registration-execution-pack.md rev 2

Verdict

PASS ON DESCRIPTION/BIRTH + DOT TOOLING CORRECTIONS. NOT READY FOR DISPATCH UNTIL CONTEXT GRAPH GATE IS APPLIED.

Opus correctly fixed the main technical/legal issues from the previous review:

• source_kind=pg_table removed; native selected within tool whitelist with preflight verification.
• Raw SQL rollback removed; forward-only + --update correction path adopted.
• Description follows Đ3 §A.3 collection format.
• Description provenance clarified as DOT-channel birth/basic description (PROV-DOT), not AI enrichment.
• governance_role=observed justified as pilot/readiness state with upgrade conditions.
• storage_role=primary justified for unit_version as domain version data, not operational log.
• Dry-run/preflight phase added.

However, Điều 20 §0 has now made the Context Graph Gate mandatory before design. File 12 rev2 still does not contain an explicit Context Graph Evidence section proving that the latest Đ43 context pack was loaded and used.

Law / Constitution check

No blocker conflict in the substance of rev2, but there is a process blocker under Điều 20 §0.

• Điều 20 §0: design must pass Context Graph Gate before design; this is not visibly satisfied in file 12 rev2.
• Đ43 §3.1: every new AI/agent session must read PROJECT_MAP before action. File 12 rev2 does not cite PROJECT_MAP/LAWS_INDEX/DOT_REGISTRY/DB_MAP/RED_ZONES evidence.
• Đ3/Đ4: description/birth contract now addressed correctly enough for design.
• Đ35/Đ36: DOT-first and collection tooling now respected.
• Đ14: duplicate check remains required in execution preflight.
• HP NT1/NT9/NT13: evidence-first is improved, but the system graph evidence must be made explicit.

Required next work

Do not dispatch Claude Code yet.

Opus should do one compact package, not multiple microtasks:

1. Create: knowledge/dev/laws/dieu44-trien-khai/design/12b-iu0-pack2a-context-graph-gate-application.md

2. Patch file 12 to rev3 by adding a Context Graph Evidence section and referencing 12b.

12b must include

1. Latest Đ43 context pack/build identified.
2. Evidence from at least:
   • PROJECT_MAP.md
   • LAWS_INDEX.md
   • DOT_REGISTRY.md
   • DB_MAP.md
   • RED_ZONES.md
3. Domain/law resolver:
   • Đ2 Registry
   • Đ3 Metadata/Description
   • Đ4 Birth
   • Đ7 Assembly First
   • Đ14 No Duplicate
   • Đ20 Design Before Execution
   • Đ35 DOT Governance
   • Đ36 Collection Protocol
   • Đ43 System Context
   • Đ44 Information Unit
4. DOT/tool resolver:
   • dot-collection-register
   • dot-collection-health
   • dot-schema-trigger-registry-ensure
   • dot-trigger-guard
   • any relevant birth/description/provenance tooling discovered
5. DB/runtime resolver:
   • information_unit, unit_version
   • collection_registry, birth_registry, meta_catalog, directus_collections
   • dot_config description keys
   • trigger_registry, trigger_guard_*
6. Red zones for Pack 2A:
   • no raw registry SQL
   • no DDL
   • no Directus exposure
   • no Pack 2B/2C
   • no CRUD/IU production rows
   • no vector/outbox
   • no unsupported tool params
7. Unknowns converted to follow-ups or STOP conditions.

File 12 rev3 must add

• A short Context Graph Evidence section near the top.
• A statement that Pack 2A passed Điều 20 §0 CGG with reference to file 12b.
• Any new red-zone/STOP condition discovered from 12b.

Dispatch status

File 12 rev2 is not approved for dispatch only because of the new process gate. Once 12b + file 12 rev3 are uploaded, GPT can review once; if no new blocker appears, the next step can be approval to dispatch Claude Code write via DOT tools.