GPT Review — Pack 21 Report and Pack 22 Directive

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

• knowledge/dev/laws/dieu44-trien-khai/reports/21-birth-runtime-truth-doc-fix-report.md
• knowledge/dev/laws/dieu44-trien-khai/reviews/opus-review-pack21-doc-fix-report-2026-05-05.md

Verdict

Pack 21 PASS.

The documentation correction achieved the intended standard:

• no naked runtime constants introduced;
• dynamic facts are expressed with query/path source of truth;
• dated snapshot evidence is clearly marked;
• historical S145 report was append-only;
• CAT-023 and Đ4 were skipped appropriately rather than over-patched;
• no runtime/PG/DOT/system_issues mutation occurred.

Accepted results

Patched:

1. knowledge/dev/architecture/birth-registry-law.md
2. knowledge/dev/architecture/birth-procedures.md
3. knowledge/current-state/reports/s145-m2-dot119-birth-triggers-report

Skipped with valid rationale:

1. registries/meta_catalog/CAT-023
2. knowledge/dev/laws/law-04-birth-process.md

Status after 20B + Pack 21

• Vector/search pollution resolved.
• Context-pack KB mirror purged and future upload disabled.
• Filesystem retention installed.
• Birth runtime docs corrected to query-path language.

The system is ready to resume IU work.

Next directive: Pack 22

Opus should create design pack:

knowledge/dev/laws/dieu44-trien-khai/design/22-dot-iu-create-wrapper-design.md

Goal

Design dot-iu-create as a wrapper over the existing birth/IU runtime, not as a new birth process.

Required principles

1. No new birth process.

   • Use existing IU/UV schema, L1/L2 gates, and trg_birth_information_unit.
   • Do not raw insert into birth_registry.

2. Wrapper, not manual CTE ritual.

   • Agent/user provides minimal business inputs.
   • Tool handles vocab discovery, IU+UV transaction, anchors, hash, and verification.

3. Query-path / anti-hardcode.

   • Do not hardcode vocab values.
   • Read vocab from dot_config / current runtime.
   • Do not hardcode birth trigger counts or schema assumptions; verify current schema.

4. Birth behavior.

   • INSERT IU should let existing trigger create birth row.
   • Wrapper verifies birth row after commit.
   • If auxiliary/backfill is ever needed, that must be reported as health signal, not hidden.

5. Safety and idempotency.

   • Dry-run mode required.
   • Detect existing canonical_address and stop/idempotently report.
   • No duplicate IU creation.
   • No cleanup/delete in design.

Design pack sections required

1. Controlling docs/evidence:
   • P2B-P0 schema inspection report;
   • P2B-P1 pilot insert report;
   • P2B-INV birth pipeline inventory report;
   • Pack 21 report.
2. Current runtime model:
   • IU table;
   • UV table;
   • circular FK/deferred constraints;
   • L1/L2 gates;
   • birth trigger.
3. CLI/API contract proposal:
   • --canonical-address
   • --title or equivalent;
   • body/content input;
   • --dry-run, --execute, --json.
4. Vocab discovery contract:
   • query dot_config keys;
   • no hardcoded unit_kind/section_type.
5. Transaction plan:
   • INSERT IU;
   • INSERT UV;
   • update anchors;
   • COMMIT;
   • post-verify birth.
6. Verification plan:
   • IU exists;
   • UV linked;
   • birth row exists and entity_code matches information_unit::<id>;
   • UV birth remains zero.
7. Error/STOP conditions.
8. Execution pack split:
   • design first;
   • read-only inspection if needed;
   • runtime prompt later.

Hard boundaries

For Pack 22 design:

• no runtime mutation;
• no DOT patch;
• no Pack 2C dispatch;
• no raw birth_registry insert;
• no new birth lifecycle design;
• no hardcoded vocab or counts.

Optional TDs not blocking Pack 22

• v_birth_pipeline_runtime_stats dynamic view/report generator.
• kb_mirror_status semantics under Đ43/20C.
• Birth health-check row for ORPHAN/PHANTOM/backfill warning.
• Duplicate DOT registration cleanup.