dot-iu-cutter v0.1 — Design Report (synthesis)
dot-iu-cutter v0.1 — Design Report (D8)
Date: 2026-05-15 Status: DESIGN PHASE COMPLETE — pending User review Baseline: rev5d (User PASS) + Agent Design Handoff Notes Scope: DESIGN ONLY. Synthesis of all 11 deliverables.
1. Purpose
Synthesize the design phase: list deliverables and revisions, confirm full coverage of Q1–Q56 and acceptance criteria 1–50, consolidate schema gaps, declare law-conflict status, surface missing instrumentation, list open questions, and recommend the next step.
2. Deliverables (paths and revisions)
| # | Slug | Path | Revision |
|---|---|---|---|
| 0 | checkpoint-0-design-plan | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-checkpoint-0-design-plan-2026-05-15.md |
1 |
| 1 | operational-design | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-operational-design-2026-05-15.md |
1 |
| 2 | manifest-and-operator-contract | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-manifest-and-operator-contract-2026-05-15.md |
1 |
| 9 | cross-temporal-semantic-threading-design | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-cross-temporal-semantic-threading-design-2026-05-15.md |
1 |
| 11 | thread-retrieval-user-interaction-design | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-thread-retrieval-user-interaction-design-2026-05-15.md |
1 |
| 3 | segmentation-health-design | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-segmentation-health-design-2026-05-15.md |
1 |
| 4 | capability-intake-design | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-capability-intake-design-2026-05-15.md |
1 |
| 5 | decision-backlog-registry-design | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-decision-backlog-registry-design-2026-05-15.md |
1 |
| 6 | assembly-axes-metadata-contract | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-assembly-axes-metadata-contract-2026-05-15.md |
1 |
| 7 | uosl-compatibility-note | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-uosl-compatibility-note-2026-05-15.md |
1 |
| 10 | legal-alignment-governance-compatibility-report | knowledge/dev/laws/dieu44-trien-khai/design/dot-iu-cutter-v0.1-legal-alignment-governance-compatibility-report-2026-05-15.md |
1 |
| 8 | design-report | (this document) | 1 |
Total: 11 design deliverables + Checkpoint 0.
3. Coverage of Questions Q1–Q56
| Q | Primary deliverable | Secondary |
|---|---|---|
| Q1 | D1 | — |
| Q2 | D1 | — |
| Q3 | D1 | — |
| Q4 | D2 | D7 |
| Q5 | D2 | D1 |
| Q6 | D2 | — |
| Q7 | D2 | — |
| Q8 | D2 | D1 |
| Q9 | D2 | — |
| Q10 | D2 | — |
| Q11 | D1 | D2 |
| Q12 | D1 | D6 |
| Q13 | D1 | — |
| Q14 | D1 | — |
| Q15 | D3 | — |
| Q16 | D3 | — |
| Q17 | D3 | — |
| Q18 | D1 | — |
| Q19 | D1 | D3, D4 |
| Q20 | D1 | — |
| Q21 | D1, D2 | D5 |
| Q22 | D3 | D9 |
| Q23 | D3 | — |
| Q24 | D3 | — |
| Q25 | D3 | — |
| Q26 | D4 | — |
| Q27 | D4 | — |
| Q28 | D4 | — |
| Q29 | D5 | — |
| Q30 | D5 | — |
| Q31 | D6 | D7 |
| Q32 | D6 | D9 |
| Q33 | D6 | D1 |
| Q34 | D1 | D6 |
| Q35 | D1 | D10 |
| Q36 | D1 | D10 |
| Q37 | D9 | — |
| Q38 | D9 | — |
| Q39 | D9 | D7 |
| Q40 | D9 | D11 |
| Q41 | D9 | D3 |
| Q42 | D9 | D3, D11 |
| Q43 | D5 | D3, D9 |
| Q44 | D9 | D3 |
| Q45 | D9, D10 | — |
| Q46 | D9 | — |
| Q47 | D11 | — |
| Q48 | D11 | — |
| Q49 | D11 | — |
| Q50 | D11 | — |
| Q51 | D11 | — |
| Q52 | D11 | D3 |
| Q53 | D11 | — |
| Q54 | D11 | — |
| Q55 | D11 | — |
| Q56 | D11 | — |
Coverage: 56 / 56 (100%).
4. Coverage of Acceptance Criteria 1–50
| Criterion | Primary | Status |
|---|---|---|
| 1 (C1A inherit) | D1 | covered |
| 2 (3 flows) | D1 | covered |
| 3 (manifest as code) | D2 | covered |
| 4 (independent review pre-cut) | D2 | covered |
| 5 (round-trip verify) | D1 | covered |
| 6 (rollback) | D1 | covered |
| 7 (split/merge lifecycle) | D3 | covered |
| 8 (edge/context-pack/no-action) | D3 | covered |
| 9 (post-cut usage review) | D3 | covered |
| 10 (Segmentation Health Report) | D3 | covered |
| 11 (signal classification) | D3 | covered |
| 12 (TAC capability intake) | D4 | covered |
| 13 (KG capability intake) | D4 | covered |
| 14 (Cutter Self-Review) | D4 | covered |
| 15 (Decision Backlog Registry) | D5 | covered |
| 16 (impact diff / no-impact) | D4 | covered |
| 17 (no hardcoding to infra state) | D1 | covered |
| 18 (dogfood TAC) | D1, D2 | covered |
| 19 (KG feedback hooks) | D6 | covered |
| 20 (state what infra missing) | D8 (this report §6) | covered |
| 21 (human escalation) | D10 | covered |
| 22 (no decision lost) | D5 | covered |
| 23 (axis-1 reconstruction) | D6 | covered |
| 24 (axis-2 semantic assembly) | D6 | covered |
| 25 (UOSL/Đ44 mapped) | D7 | covered |
| 26 (acknowledge current TAC) | D1 | covered |
| 27 (PG-driven assembly/registry) | D1, D2, D5, D9 | covered |
| 28 (DOT-pair / dual-engine) | D1 | covered |
| 29 (separates schema gaps from impl) | D8 §6 | covered |
| 30 (cross-doc assembly metadata) | D6 | covered |
| 31 (cross-temporal threading) | D9 | covered |
| 32 (semantic intake flow) | D9 | covered |
| 33 (candidate/membership lifecycle) | D9 | covered |
| 34 (negative knowledge) | D9 | covered |
| 35 (missing/wrong link detection) | D9 | covered |
| 36 (thread split/merge lifecycle) | D9 | covered |
| 37 (Đ37 governance map) | D10 | covered |
| 38 (no parallel notification) | D5, D10 | covered |
| 39 (industry standards leverage) | D9 | covered |
| 40 (user-directed + system-discovered) | D9 | covered |
| 41 (TAC/KG progress feeds intake) | D4 | covered |
| 42 (thread-first retrieval) | D11 | covered |
| 43 (thread resolution) | D11 | covered |
| 44 (Thread Context Pack) | D11 | covered |
| 45 (fallback to vector) | D11 | covered |
| 46 (retrieval quality metrics) | D11 | covered |
| 47 (search-gap feedback) | D11 | covered |
| 48 (audience-scoped search) | D11 | covered |
| 49 (visibility/readiness/publication) | D11 | covered |
| 50 (search usage → health → recursion) | D11 | covered |
Coverage: 50 / 50 (100%).
5. Principles P1–P15 Spot Check
All 15 mandatory principles (rev5d §8) are honored across deliverables. Key examples:
- P1 (C1A is law) — D1 §4.6, D2 §4.3, D6 §4.7.
- P2 (decision separate from execution) — D1 §4.2.
- P3 (manifest as code) — D2 §4.1.
- P4 (round-trip verification) — D1 §4.7.
- P5 (split/merge lifecycle) — D3 §4.7, §4.8.
- P6 (usage evidence is governance) — D3 §4.5.
- P7 (graph enrichment before structural change) — D3 §4.6, §4.8 guardrail.
- P8 (dogfood Text-as-Code) — D2 §4.1.
- P9 (cutter feeds from KG) — D6 §4.5.
- P10 (positive recursion) — D4 §4.7, D11 §4.14.
- P11 (anti-forgetting registry) — D5 §4.11.
- P12 (simple at operation layer; 3 flows) — D1 §4.1.
- P13 (two assembly axes) — D6 §4.1.
- P14 (PG-driven assembly) — D1 §4.13, D2 §4.9, D5 §4.1.
- P15 (UOSL compat) — D7.
6. Schema Gaps Consolidated
Schema gaps are recorded; no DDL is produced. Categorized:
6.1 New first-class fields on tac_logical_unit
canonical_address(D6, D7)semantic_role(D6, D7)classification_labelscardinality / placement (D6)candidate_edges(preferuniversal_edges) (D6, D9)edge_readiness_notes(D6)universal_edges_compat_flag(D6)vector_projection_readiness(D6)thread_hint(D6)lifecycle_stage_hint(D6)risk_class(D2, D7)authority(enacted/draft/runtime) (D7)visibility,readiness,publication_state(D11, D7)reviewer_identity(D1, D2, D7)birth_gate_class(D1)uosl_compat_version,uosl_compat_status(D7)
6.2 New tables / views (logical; no DDL)
manifest_envelope(D2)manifest_unit_block(D2)review_decision(D2)cut_change_setwithrollback_key(D1)verify_result(D1)report_envelope(D1)cut_history_index(D1)vocabulary_gap_register(D2)manifest_diffview (D2)health_signal_event(D3)unit_health_score,thread_health_score,coupling_score(D3)segmentation_health_report(D3)f2_action_decision(D3)capability_intake_record(D4)impact_diff(D4)no_impact_record(D4)cutter_self_review_report(D4)tool_revision(D4)decision_backlog_entry,_history,_dependency,_sweep_log(D5)semantic_thread(D9)semantic_thread_membership(preferuniversal_edges) (D9)semantic_thread_candidate(D9)semantic_thread_evidence(D9)semantic_thread_health_signal(D9)semantic_thread_negative_knowledge(D9)semantic_thread_expected_chain(D9)retrieval_metric_event,_aggregate(D11)search_gap_signal(D11)audience_filter_policy(D11)thread_context_pack_cache(D11, optional)consumer_contract_log(D11)
6.3 Family Registry entries (D7)
- Manifest envelope family
- Review decision family
- Cut change-set family
- semantic_thread family
- retrieval_metric family
- audience_filter_policy family
6.4 Trigger / event plumbing
- CDC trigger for birth event (D9)
- NOTIFY/LISTEN plumbing for intake (D9)
- Edge reassignment audit trail (D3)
- Alias / redirect table for superseded units (D3)
7. Law Conflict Status
No unresolved law conflict at design phase completion.
Conflict watchlist (Checkpoint 0 §8) reviewed in D10 §8. All items either resolved or deferred to governance via D5 backlog. Design phase MAY proceed to user review and (after approval) implementation planning.
8. Missing Instrumentation (criterion 11, 20)
Items classified requires_instrumentation and still missing:
- Retrieval logs / event capture (D11) —
thread_hit_rate,fallback_vector_rate,context_sufficiency_rate, etc. - Co-edit detection (D3, D9) — change-set proximity capture.
- Co-citation capture (D3, D9) — citation graph extraction.
- Co-retrieval capture (D3, D9) — depends on (1).
- CDC plumbing (D9) — PG trigger + NOTIFY/LISTEN for birth events.
- Thread centroid embedding (D11) — per-thread aggregate embedding for ranking.
- Health-score aggregator (D3) — view/materialized-view refresh policy.
- DOT-pair signature recording (D1) — dual signature envelope on REPORT.
- Auth-context propagation (D11) — role/scope to retrieval layer.
These are named, not built, in v0.1 design.
9. Open Questions (consolidated)
From each deliverable (selected; full list per deliverable):
- Should
dot-iu-cutter-verifybe separate code path or--verifymode? (D1) - Where does the independent-AI reviewer run? (D1)
- Per-unit blocks: child rows vs JSONB? (D2)
- How does Đ24 self-extend (vocabulary-of-vocabulary)? (D2)
- Exact threshold values for D3 signal scoring. (D3)
- Co-edit instrumentation reliance on current CDC. (D3, D9)
- Fixed vs learned weights for
coupling_score. (D3) - Auto-accept thresholds + material-difference thresholds (D9).
semantic_threadfinal placement ifuniversal_edgesinsufficient (D9, D10).- Heterogeneity measure for
overbroaddetection (D9). - Negative knowledge decay policy (D9).
thread_hit_rateinitial target value (D11).- Embedding scheme for thread centroids (D11).
- Audience formal definitions (employee/partner/customer) (D11).
wrong_audience_resultrollback policy (D11).- Context Pack caching policy (D11).
- Self-Review cadence defaults (D4).
- Impact diff auto-generation vs hand-authored (D4).
- Tool revision propagation to verifier (D4).
- Default
next_review_dateper risk/kind (D5). - Auto-resolve on signal silence: yes/no (D5).
- Backlog scope: cutter-only vs federated (D5).
- Manifest/Review/Cut/Report families: separate or unified (D7).
- semantic_thread family placement in UOSL (D7).
- Maturity ladder ↔ tool revision interaction (D7).
- Multi-valued labels first-class vs profile JSON (D7).
Governance closure recommendations (D10 §9) feed these questions to Đ37 / Đ44 / Đ32 owners.
10. Recommended Next Step
The design phase is complete and self-consistent. No code, no DDL, no migration, no PG mutation, no vector work, no UI build was performed. All 11 deliverables exist at knowledge/dev/laws/dieu44-trien-khai/design/. All 56 questions and 50 acceptance criteria are covered.
Recommended next step:
- User review of the 11 deliverables + Checkpoint 0. Focus on:
- D7 / D10 governance closures (UOSL family decisions, Đ37 role closures).
- Auto-accept thresholds (D9) and retrieval metric targets (D11).
- Threading PG placement decision (D9 / Đ33 / Đ39).
- Governance routing of the open questions in §9 to Đ37, Đ44, Đ32 owners via Decision Backlog Registry (D5).
- Closure of Family Registry entries for new object families (D7 §6 items 47–52) at Đ44 governance.
- Schema gap prioritization for migration planning (a separate phase, not this design phase). Suggested priority: critical-path fields for axis-1/axis-2 first (D6 §6), then manifest envelope (D2 §6), then threading (D9 §6), then retrieval instrumentation (D11 §6).
- Only after governance closure and User PASS on this design phase, implementation planning may begin under standard Đ32/Đ37 controls. Implementation is not authorized by this design phase.
11. Phase Status
design_phase_status: COMPLETE_PENDING_USER_REVIEW
deliverables_count: 11
checkpoint_0_present: true
questions_covered: 56/56
acceptance_criteria_covered: 50/50
principles_honored: 15/15
schema_gaps_recorded: 56
law_conflicts_unresolved: 0
governance_gaps_recorded: 5
missing_instrumentation_recorded: 9
implementation_actions_taken: none
forbidden_scope_respected: true
ready_for_user_review: true
ready_for_implementation: false_until_user_approval_and_governance_closure