KB-24B1
dot-iu-cutter v0.1 — Checkpoint 0 Design Plan
13 min read Revision 1
dot-iu-cutterdesign-plancheckpoint-0rev5ddesign-phase
dot-iu-cutter v0.1 — Checkpoint 0: DESIGN PLAN
Date: 2026-05-15 Status: ACTIVE — controls 11-deliverable design phase Baseline: rev5d Operational Problem Statement (User PASS) Companion: Agent Design Handoff Notes (2026-05-15) Scope: DESIGN ONLY. No code, no DDL, no migration, no PG mutation, no Qdrant/vector work, no UI build, no implementation dispatch.
1. Mandate Acknowledgement
Agent has fully read:
knowledge/dev/laws/dieu44-trien-khai/requirements/dot-iu-cutter-v0.1-operational-problem-statement-rev5-assembly-axis-uosl-integrated-2026-05-15.md(rev5d, 32923 bytes)knowledge/dev/laws/dieu44-trien-khai/requirements/dot-iu-cutter-v0.1-agent-design-handoff-notes-2026-05-15.md(2458 bytes)
Binding contracts confirmed:
- 56 questions (Q1–Q56) — all must be addressed across deliverables
- 50 acceptance criteria — all must be satisfied
- 15 principles (P1–P15) — design must comply
- Hard boundaries (Section 11 + Handoff §3): no implementation actions
- Gap handling rules (Handoff §4): record gaps, do not invent
- PG-First rule (Handoff §5): every data structure specifies target DB + layer
2. Design Strategy
2.1 Operating Principles for the Design Phase
- Inherit, do not rewrite. C1A is law. Đ24, Đ32, Đ33, Đ37, Đ38, Đ39, Đ43, Đ44/UOSL, Đ0-G are foundations.
- Manifest as code. All design decisions traceable, diffable, reviewable.
- PG-first, text-mirror. SSOT = PG; KB markdown = documentation only.
- Two assembly axes are first-class. Reconstruction + semantic domain assembly always co-design.
- Three flows only. Cut, Health/Correction, Upgrade. No fourth flow.
- Positive recursion baked in. Every loop must close: usage → signal → review → upgrade.
- Schema gap ≠ implementation task. Record gaps; do not propose DDL.
- Law conflict → STOP. If any deliverable surfaces a law conflict, halt and report; do not override.
2.2 Cross-Cutting Concerns (apply to all 11 deliverables)
Every deliverable must include the standard section block:
- Purpose
- Scope
- Dependencies (law refs, sibling deliverables)
- Key Decisions (with rationale)
- PG Storage per Object (DB, layer Não/Kho/Cổng, justification)
- Schema Gaps (no DDL; named gap + recommendation)
- Law References (which Đ controls this design surface)
- Open Questions
- Coverage:
- Questions covered (Q-IDs)
- Acceptance criteria covered (criterion numbers)
- Schema gaps
- Law dependencies
- Open questions
2.3 Authoring Order (matches Handoff §2 priority)
- D1 Operational Design (sets the three-flow backbone)
- D2 Manifest & Operator Contract (formalizes what flows operate on)
- D9 Cross-Temporal Semantic Threading (semantic backbone)
- D11 Thread Retrieval & User Interaction (consumer of D9)
- D3 Segmentation Health / Usage Feedback (closes Flow 2)
- D4 Capability Intake & Upgrade Loop (closes Flow 3)
- D5 Decision Backlog Registry (anti-forgetting infra)
- D6 Assembly Axes & Metadata Contract (axis-1 + axis-2 contract)
- D7 UOSL / Đ44 Compatibility Note (profile mapping)
- D10 Legal Alignment / Governance Compatibility Report (audit)
- D8 Design Report (synthesis, last)
3. Deliverable ↔ Question Coverage Map
| # | Deliverable | Primary Questions | Secondary |
|---|---|---|---|
| D1 | Operational Design | Q1, Q2, Q3, Q11, Q12, Q13, Q14, Q18, Q19, Q20, Q34, Q35 | Q5, Q8, Q21 |
| D2 | Manifest & Operator Contract | Q4, Q5, Q6, Q7, Q8, Q9, Q10, Q21 | Q11, Q31, Q32 |
| D3 | Segmentation Health & Usage Feedback | Q15, Q16, Q17, Q22, Q23, Q24, Q25 | Q41, Q42, Q43, Q44 |
| D4 | Capability Intake & Upgrade Loop | Q26, Q27, Q28 | Q23, Q41 |
| D5 | Decision Backlog Registry | Q29, Q30 | Q43 |
| D6 | Assembly Axes & Metadata Contract | Q31, Q32, Q33 | Q4, Q34 |
| D7 | UOSL / Đ44 Compatibility Note | — (cross-cuts) | Q4, Q31, Q32, Q39 |
| D8 | Design Report | (synthesis) | all |
| D9 | Cross-Temporal Semantic Threading | Q37, Q38, Q39, Q40, Q41, Q42, Q43, Q44, Q45, Q46 | Q22, Q32 |
| D10 | Legal Alignment Report | Q35, Q36, Q45 | Q21, Q39 |
| D11 | Thread Retrieval & User Interaction | Q47, Q48, Q49, Q50, Q51, Q52, Q53, Q54, Q55, Q56 | Q42 |
Total questions referenced: Q1–Q56 (full coverage planned).
4. Deliverable ↔ Acceptance Criteria Coverage Map
| Criterion | Primary Deliverable | Supporting |
|---|---|---|
| 1 (C1A inherit) | D1 | D2, D10 |
| 2 (3 flows) | D1 | D8 |
| 3 (manifest as code) | D2 | D1 |
| 4 (independent review pre-cut) | D2 | D1 |
| 5 (round-trip verify) | D1 | D2, D6 |
| 6 (rollback) | D1 | D2 |
| 7 (split/merge lifecycle) | D3 | D9 |
| 8 (edge/context/no-action, not auto-merge) | D3 | D9 |
| 9 (post-cut usage review) | D3 | D9 |
| 10 (Segmentation Health Report) | D3 | — |
| 11 (signal classification) | D3 | D9 |
| 12 (TAC capability intake) | D4 | — |
| 13 (KG capability intake) | D4 | — |
| 14 (Cutter Self-Review) | D4 | D8 |
| 15 (Decision Backlog Registry) | D5 | — |
| 16 (impact diff / no-impact record) | D4 | D5 |
| 17 (no hardcoding to infra state) | D1 | D7, D8 |
| 18 (dogfood TAC) | D1 | D2 |
| 19 (KG feedback hooks) | D6 | D9 |
| 20 (state what infra missing) | D8 | all |
| 21 (human escalation for authority) | D10 | D2, D3 |
| 22 (no decision lost) | D5 | — |
| 23 (axis-1 reconstruction) | D6 | — |
| 24 (axis-2 semantic assembly) | D6 | D9 |
| 25 (UOSL/Đ44 mapped) | D7 | D10 |
| 26 (acknowledge current TAC) | D1 | D8 |
| 27 (PG-driven assembly/manifest/registry) | D5 | D1, D2, D9 |
| 28 (DOT-pair / dual-engine) | D1 | D10 |
| 29 (schema gaps separated from impl tasks) | D8 | all |
| 30 (metadata for cross-doc assembly) | D6 | D9 |
| 31 (cross-temporal semantic threading) | D9 | — |
| 32 (semantic intake flow) | D9 | — |
| 33 (candidate edge/thread lifecycle) | D9 | — |
| 34 (negative knowledge persistence) | D9 | — |
| 35 (missing/wrong link detection) | D9 | D3 |
| 36 (thread split/merge lifecycle) | D9 | D3 |
| 37 (Đ37 governance map) | D10 | D9, D5 |
| 38 (existing governance channels, no parallel notif) | D10 | D5 |
| 39 (industry standards leverage) | D9 | D11 |
| 40 (system-discovered + user-directed first-class) | D9 | D11 |
| 41 (TAC/KG progress feeds intake) | D4 | D9 |
| 42 (thread-first retrieval) | D11 | — |
| 43 (thread resolution from query) | D11 | — |
| 44 (Thread Context Pack) | D11 | — |
| 45 (fallback to vector search) | D11 | — |
| 46 (retrieval quality metrics) | D11 | — |
| 47 (search-gap feedback signals) | D11 | D3 |
| 48 (audience-scoped search) | D11 | D10 |
| 49 (visibility/readiness/publication filters) | D11 | D10 |
| 50 (search usage → health → positive recursion) | D11 | D3 |
Total criteria planned: 50/50.
5. Law Dependency Map
| Law | Role | Used in |
|---|---|---|
| C1A (Đ38-trien-khai) | Segmentation law (binding) | D1, D2, D6, D10 |
| Đ24 Label Law | No parallel taxonomy | D2, D9, D10 |
| Đ32 Risk/Approval | Approval guard for risk-bearing actions | D1, D2, D9, D10 |
| Đ33 / Đ43 | Target DB + layer rules | D5, D9, D7, D10 |
| Đ37 Governance Org | Owner/reviewer/escalation mapping | D2, D5, D9, D10 |
| Đ38 Text-as-Code | Manifest-as-code, versioned, diffable | D2, D4, D6 |
| Đ39 Universal Edges | universal_edges first; thread compat | D6, D9, D10 |
| Đ44 UOSL (DRAFT) | OQC, G1–G12, profile, edge layer | D6, D7 |
| Đ0-G Birth Gate | Distinguish base/draft/runtime | D2, D7 |
6. PG-First Object Allocation (planned, design-level)
This is design intent; no DDL is produced here.
| Object | Target DB | Target Layer | Notes |
|---|---|---|---|
| cut_manifest | directus (TAC schema) | Kho | Versioned rows + JSONB envelope |
| review_decision | directus (TAC schema) | Não | reviewer, status, evidence |
| cut_result + rollback_key | directus (TAC schema) | Kho | exact-key rollback |
| segmentation_health_signal | directus | Não | views/queries; signal table |
| capability_intake_record | directus | Não | TAC/KG intake |
| decision_backlog_registry | directus (Lớp KHO) | Kho | SSOT; KB mirror only |
| semantic_thread | directus | Kho | First evaluate universal_edges |
| semantic_thread_membership | directus | Kho | Prefer reuse of universal_edges |
| semantic_thread_candidate | directus | Não | Status lifecycle |
| semantic_thread_evidence | directus | Não | JSONB PROV envelope |
| semantic_thread_health_signal | directus | Não | Route to Decision Backlog |
| retrieval_metric (counter/event) | directus | Não | Instrumentation hook |
| search_gap_signal | directus | Não | Feedback loop |
| audience_filter_policy | directus | Cổng | Access-control surface |
Final placement is to be confirmed in D7 (UOSL Compatibility) and D10 (Legal Alignment) per Đ33/Đ43.
7. Anticipated Schema Gaps (named only; no DDL)
Recorded as design-phase observations:
semantic_thread*family — may map touniversal_edges; evaluate per Đ39 before separate tables.- Thread-first retrieval instrumentation —
retrieval_metric,search_gap_signallikely require new PG tables. - UOSL G1–G12 field group mapping — may collide with current
tac_logical_unitJSON profile. - Audience scope policy — relationship to existing access-control surface unclear.
- Negative knowledge persistence — no current table for rejected thread proposals.
- Capability intake record — may collide with existing
decision_logif any. - Expected lifecycle chain JSONB on thread — new field requirement.
- Birth-gate distinction (base/draft/runtime) — visibility flag in
tac_logical_unitunclear.
Each gap is recorded, not solved, in the relevant deliverable.
8. Anticipated Law Conflict Surfaces (watch list — stop if encountered)
- Đ24 vs SKOS-style thread taxonomy — must use Đ24 vocabulary or flag.
- Đ32 risk approval vs auto-accept memberships — must be risk-gated, not bypassed.
- Đ33/Đ43 PG location vs cross-DB temptation — must commit to a target DB explicitly.
- Đ37 governance vs new notification systems — must reuse existing channels.
- Đ44 (DRAFT) vs treating fields as enacted — must flag as draft, not assume.
- Đ39 universal_edges authority vs parallel thread graph — universal_edges first.
- Birth Gate (Đ0-G) vs IU L4 extension — distinguish base/draft/runtime.
Stop rule: if a deliverable surfaces a conflict that cannot be resolved by deferring/flagging, halt and report.
9. Forbidden Actions (Hard Boundaries Reminder)
The following are not allowed during this design phase:
- Writing or proposing concrete DDL
- Migration scripts of any kind
- PG mutations (INSERT/UPDATE/DELETE/ALTER)
- Qdrant collection/vector mutations
- UI build / frontend code / nginx config
- Self-dispatching to implementation agents
- Inventing new vocabulary outside Đ24
- Creating new governance/notification systems outside Đ37
If any of the above appear necessary, the deliverable must record the requirement as a gap and stop — not act.
10. Definition of Done for Design Phase
The design phase is complete when:
- 11 deliverables exist at
knowledge/dev/laws/dieu44-trien-khai/design/with consistent dating (2026-05-15). - Q1–Q56 coverage is 100% (verified by D8 Design Report).
- Acceptance criteria 1–50 coverage is 100% (verified by D8).
- Every schema gap is recorded (named, located in deliverable, not solved).
- Every law dependency is named with the controlling Đ.
- D10 (Legal Alignment) confirms no unresolved conflicts; if any, document and stop.
- D8 (Design Report) emits: paths + revisions, coverage tables, schema-gap list, law-conflict status, missing instrumentation list, open questions, recommended next step.
11. Authoring Notes
- All 11 deliverables use the same path pattern:
knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-<slug>-2026-05-15.md. - Markdown is the documentation mirror; the SSOT for design decisions remains this Checkpoint 0 + the 11 deliverables until promoted into PG governance.
- No deliverable will alter the rev5d controlling file.
12. Ready Statement
Checkpoint 0 confirms scope, boundaries, and coverage plan. Agent proceeds to write the 11 deliverables in priority order under DESIGN ONLY scope. Any law conflict halts the phase; any schema gap is recorded, not solved.