GPT Directive — Track B Execution Roadmap after IU-0 Modular Baseline

Date: 2026-05-04 Context: User asked GPT to reduce overly granular Opus handoffs and steer Track B toward actual usage of information units.

Current status

Track 0 Orphan/Ghost and Track A Legacy Vector Stabilization are DONE. IU-0 Modular v2 baseline is active in KB and reviewed 3/3 PASS. Pilot planning pack 08/08a/08b/08c/08d is prepared. 08d rev 3 is approved as a READ-ONLY simulation prompt template.

Operating principle from now

Stop micro-handoffs. Use larger work packages with clear gates. Opus should not ask GPT/User after every small patch unless a gate decision or safety issue appears.

Near objective

Move from design to practical use: validate candidate information-unit slicing and MUP feasibility, then prepare a minimal read-only-to-write pilot plan that can create actual information units safely later.

Roadmap

Work Package 1 — Run READ-ONLY simulation

Dispatch 08d rev 3 to Agent/Codex. Output: one report at knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pilot-round1-readonly-simulation-report.md.

Opus action after report:

• Read actual report file.
• Summarize boundary verification, Scenario A/B token savings, MUP feasibility, IU-0 §3 vs P38-XC §5 consistency, and recommendation.
• Do not patch 07/07b/07c unless report shows a real defect.

Work Package 2 — G-Pilot-2 decision pack

If simulation PASS, Opus prepares one compact decision pack (5-8K chars max): 08e-iu0-pilot-round1-g-pilot-2-decision-pack.md.

It should decide only:

• Which 1-2 docs enter first writable pilot.
• Which slices are in scope.
• Which fields from 15-element MUP are fillable immediately vs placeholder.
• Which writes are allowed and which are still forbidden.
• Exact rollback/stop criteria.

Work Package 3 — Implementation preflight, not implementation

If User/GPT approves G-Pilot-2, Opus prepares one Agent prompt for implementation preflight. It must investigate actual storage options and produce an implementation plan, not create tables yet.

Work Package 4 — Minimal writable pilot

Only after explicit User approval. Target: create a tiny number of actual IU records/slices for IU-0/P38-XC, with rollback and audit. No vector IU collection until storage and outbox are approved.

Constraints

• Do not reopen Track A unless legacy vector regresses.
• Do not rewrite big documents. Patch only concrete defects.
• Keep new docs small: 5-8K chars preferred.
• One work package = one Opus prompt/report, not many small handoffs.
• User decision required only for: dispatching Agent, opening writable pilot, or schema/DDL/code changes.