dot-iu-cutter v0.2 — Next-Phase Routing Note (2026-05-16)
dot-iu-cutter v0.2 — Next-Phase Routing Note
Path: knowledge/dev/laws/dieu44-trien-khai/v0.2-planning/dot-iu-cutter-v0.2-next-phase-routing-note-2026-05-16.md
Date: 2026-05-16
Status of this note: ROUTING / PLANNING ONLY — no action started, no design begun.
1. Current Status
| Milestone | State |
|---|---|
v0.1 P0 schema (5 cutter_governance tables) |
LIVE in production (2026-05-15) |
v0.2 Phase α (authority + canonical_address_format_version cols on public/sandbox logical_unit; cutter_governance.canonical_address_alias) |
LIVE in production (2026-05-16), GPT-ratified PASS, backup-verified |
Phase α is closed out. Backup verification = PASS (restore-tested). Production stable.
2. Pending Items (not started)
| Item | Description |
|---|---|
| BR-6 | Split/merge technical-debt (TD) absorption — reconcile split/merge semantics before manifest design depends on them |
| P0-2 | cutter_governance.manifest_envelope + manifest_unit_block (manifest design) |
| P0-6 | cutter_governance.review_decision |
| P0-5 remainder | decision_backlog_history, decision_backlog_dependency, sweep_log |
All four lack design/dry-run evidence and are unauthorized until separately gated.
3. Recommended Next Route
Absorb BR-6 (split/merge TD) BEFORE starting P0-2 manifest design.
Rationale: the manifest model (manifest_envelope / manifest_unit_block) encodes how
units are grouped and addressed. If split/merge TD is unresolved, the manifest schema risks
being designed against semantics that BR-6 will later change, forcing a re-cut of P0-2.
Absorbing BR-6 first de-risks the manifest design and avoids rework.
Suggested ordering:
- BR-6 split/merge TD absorption (design + dry-run, gated)
- P0-2
manifest_envelope/manifest_unit_block(design → dry-run → command-review → ratify → execute) - P0-6
review_decision - P0-5 remainder
4. Optional Alternate Route
If the User prefers to prioritize connector / integration work over schema progression: MCP server Path B — wire the MCP server / connector layer against the now-live Phase α columns. This is an alternative track, not a prerequisite, and would defer BR-6/P0-2.
5. Boundary
- This note starts no work. It records routing options only.
- P0-2 / manifest design / further migration remain unauthorized.
- The next gated step requires its own design → dry-run → command-review → GPT ratify → explicit User execution prompt in a separate session. Operator self-advance PROHIBITED.
Recommended next route: BR-6 split/merge TD absorption first, then P0-2 manifest design.