GPT Review — Pack 2A Legal/Tooling Preflight Discovery Dispatch

Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Scope: Review Opus revised dispatch prompt after legal recheck found raw INSERT risk.

Verdict

APPROVE READ-ONLY DISCOVERY DISPATCH — WITH SMALL ADDENDUM.

Opus correctly accepted the blocker and re-scoped Pack 2A from write-capable governance cleanup to read-only legal/tooling preflight. This now matches the principle that each specialty domain must use its governing law and toolchain.

Law / Constitution check

No blocker conflict for read-only discovery.

• Đ4: satisfied because prompt no longer creates/registers entities; it only discovers legal birth/registration tooling.
• Đ2: satisfied because registry actions are not performed manually; discovery checks the lawful registry path.
• Đ35: satisfied because DOT/tooling is treated as the gateway; prompt searches dot_tools and filesystem before any write.
• Đ36: satisfied because collection registration is recognized as a governed collection-protocol action; prompt checks DOT-COL-REGISTER / DOT-COLLECTION-CREATE and registry state.
• Điều 20 v1.2 / NT15: satisfied as read-only spike/discovery before execution.
• Hiến pháp NT1/NT9/NT13: satisfied — evidence-first, no guessing, PG/runtime discovery only.
• Đ44: IU roadmap preserved; no CRUD/vector/outbox.

Required addendum before sending

Do not rewrite the whole prompt. Add these small items to the dispatch:

1. Mandatory legal docs to read first:

   • knowledge/dev/laws/law-04-birth-process.md
   • knowledge/dev/laws/law-02-registry.md
   • knowledge/dev/laws/dieu35-dot-governance-law.md
   • knowledge/dev/laws/dieu36-collection-protocol-law.md
   • knowledge/current-state/reform-PG-tools/09-khai-sinh-collection.md
   • knowledge/dev/laws/dieu20-thiet-ke-truoc-trien-khai.md
   • knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-legal-recheck-pack2a-dot-gateway-risk-2026-05-04.md

2. Explicitly forbid executing discovered tools. Claude Code may locate/read tool files and inspect registration, but must not run DOT-COL-REGISTER, DOT-COLLECTION-CREATE, or any script except safe read-only commands (ls, find, cat/head/sed, --help only if guaranteed non-mutating; if uncertain, do not run).

3. Inspect tool source safely. If candidate scripts exist, capture path, status, first relevant help/header/source snippets, and whether the script appears read/write. Do not execute scripts.

4. Search for trigger governance tooling too. Query dot_tools and filesystem for trigger/ddl/audit/guard keywords, not only collection/register keywords.

5. Report legal classification. For each option proposed, mark: LEGAL, LEGAL IF APPROVED, BLOCKED, or UNKNOWN — NEED LAW/DESIGN FIRST.

6. If no governing tool/law exists for a needed action, conclusion must be: write law/tool first, then execute later. Do not propose raw SQL as a normal option. Admin fallback may only be listed as LEGAL IF APPROVED if the relevant fallback law/table/process exists and conditions are satisfied.

Directive to Opus

Send the read-only discovery prompt with the above addendum. Do not dispatch any write-capable Pack 2A prompt. After report upload, GPT must read the actual report before deciding the next path.

Target report: knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pack2a-legal-tooling-preflight-report.md

Hard stop remains: no write, no DDL, no IU rows, no registry registration, no Directus exposure, no Pack 2B/2C.