GPT Review — Pack 2A Description/Birth Contract Discovery Prompt

Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Scope: Review Opus proposed read-only Agent prompt for Description/Birth Contract discovery.

Verdict

APPROVE READ-ONLY DISCOVERY — WITH ADDENDUM.

The prompt is directionally correct and matches the lesson: if not certain, do runtime/legal discovery first. It asks the right core questions about dot-collection-register, description enforcement, collection description conventions, trigger chain, rollback tooling, species, and storage_role.

Legal check

No blocker conflict if kept read-only.

• Đ3: prompt investigates Description contract, templates, examples, and enforcement.
• Đ4: prompt investigates birth chain and description guard instead of assuming.
• Đ35/Đ36: prompt checks DOT tools and collection registration gateway before write.
• Đ20 v1.2 / NT15: this is a read-only spike/discovery before execution.
• Hiến pháp NT9: unknowns are converted to evidence requests.
• Đ44: keeps Pack 2A within governance registration, no CRUD/vector/outbox.

Required addendum before dispatch

Add these guards to Opus prompt:

1. Read mandatory docs first

   • knowledge/dev/laws/law-03-metadata.md
   • knowledge/dev/laws/dieu3-phu-luc-description-templates.md
   • knowledge/dev/laws/law-04-birth-process.md
   • knowledge/dev/laws/dieu35-dot-governance-law.md
   • knowledge/dev/laws/dieu36-collection-protocol-law.md
   • knowledge/dev/laws/dieu20-thiet-ke-truoc-trien-khai.md
   • knowledge/dev/laws/dieu44-trien-khai/design/12-iu0-pack2a-dot-governance-registration-execution-pack.md
   • knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-file12-description-birth-governance-2026-05-04.md

2. No executing DOT tools at all. --help is allowed only if source/header proves it is non-mutating. If uncertain, use head, sed, grep, cat only.

3. Distinguish evidence vs inference. Report must separate:

   • raw output/evidence;
   • agent interpretation;
   • unknowns needing law/design decision.

4. Description quality check. For proposed descriptions, agent must explicitly check against:

   • Đ3 C1–C4;
   • Phụ lục Đ3 §A.3 Collection format;
   • runtime description_min_length / table-specific min length if present.

5. Do not propose final values as decision unless supported. For governance_role, storage_role, species_code, agent may recommend only if supported by runtime convention + law. Otherwise mark UNKNOWN — needs design decision.

6. Add Q8 — Directus/API path. Since dot-collection-register may write via Directus API or SQL, inspect source to identify exact write path and audit trail. It must report whether the path is legal per Đ33/Đ35/Đ36 or uncertain.

7. Add Q9 — provenance for description. Check whether fn_auto_label_provenance or related label rows mark PROV-DOT / PROV-AI for collection_registry rows. This matters because Description Law distinguishes basic vs detailed description.

Directive

Send the prompt with the addendum. Do not run any write-capable command. Target report remains:

knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pack2a-description-birth-contract-discovery.md

After report upload, GPT reviews report before file 12 rev2 or execution approval.