GPT Reorientation — After Pack 22 Return to IU Schema / Miếng Thông Tin

Date: 2026-05-06
Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI
Context: User asks to re-locate the project after Pack 22 completion and return to Information Unit schema / miếng thông tin.

Current understanding

The user’s chronology is correct:

1. We were working on “miếng thông tin” / Information Unit.
2. Schema was not settled enough, so we moved to design law/schema work.
3. While implementing schema, birth/creation path was incomplete and unsafe.
4. We paused schema work and completed Pack 22: IU native creation + gateway enforcement.
5. Now we should return to the schema work needed to make miếng thông tin usable.

Pack 22 state

Pack 22 is COMPLETE and can be treated as closed for now:

• fn_iu_create canonical writer exists.
• fn_iu_create_plan dry-run exists.
• Birth is handled automatically by PG triggers.
• canonical_writer marker exists.
• Trigger guards enforce wrong-door blocking on IU/UV INSERT/UPDATE.
• README guidance exists.
• Closure note exists.

Therefore Pack 22 is no longer blocking schema work.

Historical anchors found in KB

Relevant historical documents:

1. knowledge/dev/laws/dieu44-trien-khai/design/07-iu0-information-unit-minimum-standard-outline.md
   IU-0 outline E.1; baseline for Information Unit minimum standard and packaging.

2. knowledge/dev/laws/dieu44-trien-khai/design/07-iu0-index-and-core.md
   IU-0 full draft modular v2; core schema, UMC/profile/capability framing.

3. knowledge/dev/laws/dieu44-trien-khai/design/08-iu0-pilot-planning-pack.md
   Pilot planning pack; G-Pilot decision gates; concerns around MUP strictness, unit_kind, cross-ref drift.

4. knowledge/dev/laws/dieu44-trien-khai/design/08d-iu0-pilot-round1-readonly-execution-prompt.md
   READ-ONLY simulation prompt for Pilot Round 1.

5. knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pilot-round1-g-pilot-2-tracking-report.md
   Pilot metadata / tracking; 9 slices, 3 proposed vocab values.

6. knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pilot-round1-closure-decision-pack.md
   Round 1 closure; 2/2 writable slices PASS at planning/simulation level.

7. knowledge/dev/laws/dieu44-trien-khai/design/09-iu0-minimal-implementation-planning-pack.md
   Minimal implementation planning pack for schema, CRUD, versioning, outbox.

8. knowledge/dev/laws/dieu44-trien-khai/design/04-information-unit-profile-schema.md
   P38-X / Information Unit profile/schema design; controlled draft, not implementation.

9. knowledge/dev/laws/dieu44-universal-object-schema-law.md
   Điều 44 UOSL controlled draft v0.1.2; umbrella law, not enacted/final.

10. knowledge/dev/laws/dieu44-trien-khai/reports/22-pack-closure-iu-native-create-and-gateway.md
    Pack 22 closure; gateway enforced.

Key correction to older roadmaps

Older roadmap items about DOT-119 / trg_birth_information_unit are now superseded by Pack 22.

We should not return to “install IU birth trigger via DOT-119” as the main path. Runtime evidence now says:

• IU creation works through fn_iu_create.
• Birth trigger/gates are active and verified.
• Gateway enforces canonical path.

DOT-119 metadata-driven redesign may remain a deferred governance/tooling item, but it is not the immediate blocker for miếng thông tin schema.

Where we are now

We are at the point of returning to:

IU schema / miếng thông tin minimum production shape

Specifically:

• finalize what fields/JSON profile are required for a usable IU slice;
• settle vocab values needed now (unit_kind, section_type, possibly publication_type);
• settle minimal CRUD/versioning behavior;
• decide what prior pilot assumptions remain valid now that fn_iu_create exists;
• prepare a small schema/pilot continuation plan using the canonical gateway.

Recommended immediate next action

Do not jump straight to execution.

First ask Opus to run a focused history reconciliation:

22+IU0-SCHEMA-RETURN-P0 — read-only KB/history review.

Goal: produce a “where exactly do we resume?” memo.

Directive to Opus

Create/read and report; no runtime mutation.

Suggested prompt to Opus:

Opus, Pack 22 is COMPLETE: fn_iu_create + gateway enforced. We are returning to the interrupted Information Unit / miếng thông tin schema work.

Task: run a READ-ONLY historical reconciliation and recommend the exact resume point.

Search/read at minimum:
- knowledge/dev/laws/dieu44-trien-khai/design/07-iu0-information-unit-minimum-standard-outline.md
- knowledge/dev/laws/dieu44-trien-khai/design/07-iu0-index-and-core.md
- knowledge/dev/laws/dieu44-trien-khai/design/08-iu0-pilot-planning-pack.md
- knowledge/dev/laws/dieu44-trien-khai/design/08d-iu0-pilot-round1-readonly-execution-prompt.md
- knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pilot-round1-g-pilot-2-tracking-report.md
- knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pilot-round1-closure-decision-pack.md
- knowledge/dev/laws/dieu44-trien-khai/design/09-iu0-minimal-implementation-planning-pack.md
- knowledge/dev/laws/dieu44-trien-khai/design/04-information-unit-profile-schema.md
- knowledge/dev/laws/dieu44-universal-object-schema-law.md
- knowledge/dev/laws/dieu44-trien-khai/reports/22-pack-closure-iu-native-create-and-gateway.md

Also search KB for:
- "G-Pilot-1", "G-Pilot-2", "G-Pilot-5"
- "MUP"
- "design_doc_section"
- "unit_kind"
- "section_type"
- "canonical address"
- "P10D"
- "schema sketch"
- "minimum production use"

Questions to answer:
1. Which older roadmap items are now superseded by Pack 22?
2. Which IU-0 schema/design questions are still open?
3. Which pilot results remain valid after Pack 22?
4. What is the minimum schema needed for miếng thông tin to be usable now?
5. Which doc should be the next patch target: 07, 07-index/core, 09, or a new 23-pack?
6. Should we resume at P10D render layer, IU schema law patch, or minimal CRUD pilot?
7. What exact next prompt should Agent execute after this review?

Hard boundaries:
- READ-ONLY only.
- No DDL/DML.
- No runtime changes.
- No vector mutation.
- No Pack 2C.
- No cleanup.

Report path:
knowledge/dev/laws/dieu44-trien-khai/reports/23-p0-iu-schema-return-history-reconciliation-report.md

GPT preliminary recommendation before Opus report

Likely resume point:

1. Close/supersede old DOT-119/IU birth blocker because Pack 22 solved canonical creation.
2. Use 09-iu0-minimal-implementation-planning-pack.md as the immediate planning base.
3. Patch it with Pack 22 reality: creation path is fn_iu_create; direct IU/UV writes forbidden; gateway enforced.
4. Then create a compact 23-iu-schema-minimum-production-pack to settle the minimum schema for usable miếng thông tin.
5. After schema minimum is settled, proceed to small CRUD/render pilot via canonical function.

Stop condition

Do not dispatch implementation until Opus returns the reconciliation report and GPT/User chooses the resume branch.