GPT Review — Pack 21 Birth Runtime Truth Doc Fix

Date: 2026-05-05 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed: knowledge/dev/laws/dieu44-trien-khai/design/21-birth-runtime-truth-doc-fix-pack.md

Verdict

Pack 21 direction PASS. Rev2 patch required before execution prompt.

Search after vector cleanup now returns canonical docs and older reports correctly. The selected targets are mostly right, but Pack 21 needs a few adjustments before execution.

Good points

• Correctly focuses on stale documentation before dot-iu-create.
• Correctly records 162 runtime trigger instances and dual trigger patterns.
• Correctly separates runtime-active vs documented/design-only.
• Correctly states QT-002 is not currently a dedicated binary wrapper.
• Correctly records birth_registry.status column drift.
• Correctly avoids runtime mutation.

Required rev2 patches

P1 — Add law-04-birth-process.md as a target doc

Search found knowledge/dev/laws/law-04-birth-process.md discussing birth/description guard and trigger responsibility. Pack 21 should include a quick check/patch note for Đ4 if it contains wording likely to imply incomplete runtime coverage or stale trigger count.

Do not over-patch Đ4. Only add a runtime truth note if needed.

P2 — Clarify S145 report patch as appendix-only

Do not rewrite historical S145 content. Append a dated note:

Historical report. Counts in this report describe the S145 batch scope. Runtime as of 2026-05-05 has 162 birth trigger instances: 31 trg_birth_* and 131 legacy birth_trigger_*.

P3 — CAT-023 patch must be verify-first

Pack says “check + patch CAT-023 if stale,” good. Make explicit:

• read CAT-023 current content first;
• if status already exists, no patch;
• if missing, add status field as runtime note, not schema mutation.

P4 — Do not put TDs into system_issues in Pack 21 unless separately approved

Pack §3 says 21-E5 | Ghi TDs vào system_issues hoặc TD tracker | KB/PG.

For Pack 21, avoid PG mutation. Use KB TD section only, or create a KB review/doc with TD list. system_issues insert/update should be a separate execution pack if needed.

P5 — Add evidence references per patch

For each target doc patch, cite supporting source:

• P2B-INV report for runtime truth;
• S145 report for historical scope;
• 18c report for IU-specific 30→31 truth;
• Pack 21 itself as consolidation.

P6 — Add search regression note

Mention that search vector cleanup has been completed and Pack 21 was prepared using post-cleanup retrieval; this prevents future readers from assuming the earlier search failure still applies.

Directive to Opus

Patch Pack 21 to rev2 with P1–P6. Then create execution prompt for doc patching only:

knowledge/dev/laws/dieu44-trien-khai/prompts/21-birth-runtime-truth-doc-fix-execution-prompt.md

Execution prompt must:

• read Pack 21 rev2;
• patch KB docs only;
• append historical notes rather than rewriting history;
• verify each old string before patch;
• if target doc not found or already current, record SKIPPED;
• no PG/runtime mutation;
• no DOT patch;
• no system_issues mutation;
• upload report after patch.

After Pack 21 execution

Proceed to Pack 22: dot-iu-create wrapper design, under existing pipeline.

Hard boundaries

• no runtime mutation;
• no DOT patch;
• no trigger/function/schema patch;
• no Pack 2C dispatch;
• no new birth process design;
• no cleanup/delete.