Incomex AI Portal
KB-6FA0

dot-iu-cutter v0.1 Design Review Control

7 min read Revision 1
dot-iu-cutterreview-controldesign-reviewgates

dot-iu-cutter v0.1 — Design Review Control

Date: 2026-05-15 Purpose: Review index for GPT/User to navigate 12 design files efficiently. Status: Active review phase. No implementation allowed.

1. File Index (12 files)

# Slug Rev
0 checkpoint-0-design-plan 1
1 operational-design (D1) 1
2 manifest-and-operator-contract (D2) 1
3 segmentation-health-design (D3) 1
4 capability-intake-design (D4) 1
5 decision-backlog-registry-design (D5) 1
6 assembly-axes-metadata-contract (D6) 1
7 uosl-compatibility-note (D7) 1
8 design-report (D8) 1
9 cross-temporal-semantic-threading (D9) 1
10 legal-alignment-governance-report (D10) 1
11 thread-retrieval-user-interaction (D11) 1

All at: knowledge/dev/laws/dieu44-trien-khai/design/

2. Review Gates

Gate 1 — Safety / Scope / Law

Files: D8, D10, D5, D7 Reviewer: GPT primary, User final Check:

  • Law conflicts blocked or deferred properly?
  • 5 governance gaps routed to Decision Backlog?
  • Đ44 treated as controlled draft, not enacted?
  • No parallel graph (Đ39) or taxonomy (Đ24)?
  • No DDL/implementation leaked? PASS condition: 0 unresolved law conflicts, all gaps tracked, no scope breach.

Gate 2 — Core Cutter Correctness

Files: D1, D2, D6 Reviewer: GPT primary, User for key decisions Check:

  • Decision truly separate from execution? (Mark → Review → Cut)
  • Round-trip verify sufficient?
  • Rollback clear and PG-backed?
  • Manifest has enough fields for both assembly axes?
  • DOT-pair / dual review defined or justified? PASS condition: Cut flow is deterministic from manifest, rollback works, both axes supported.

Gate 3 — Semantic Thread + Retrieval

Files: D9, D11, D3 Reviewer: GPT + User Check:

  • Thread ≠ Edge maintained?
  • universal_edges first respected?
  • User-directed thread not auto-truth?
  • Auto-accept risk-gated (5 conditions)?
  • Retrieval has access-control (security, not filter)?
  • Search gap feeds back into health/enrichment? PASS condition: Threading is compliant, retrieval is access-controlled, feedback loop closed.

Gate 4 — Implementation Readiness Boundary

Files: D8 §6, §8, §9 Reviewer: GPT categorize, User decide Check: Classify each item as:

  • Blocker before implementation planning
  • Governance closure required
  • Schema migration candidate
  • Instrumentation backlog
  • User/Council decision needed PASS condition: All blockers identified, no hidden implementation dependency.

3. Open Questions (26) by Owner

User Decision (8)

  • Auto-accept thresholds for semantic threading (D9)
  • Retrieval target values: thread_hit_rate, fallback_rate (D11)
  • Audience formal definitions: employee/partner/customer (D11)
  • Per-unit blocks: child rows vs JSONB (D2)
  • Backlog scope: cutter-only vs federated (D5)
  • Wrong_audience_result rollback policy (D11)
  • Context Pack caching policy (D11)
  • Self-Review cadence defaults (D4)

Đ37 Governance (5)

  • Threading roles assignment
  • Backlog custodian designation
  • Capability-intake reviewer assignment
  • DOT-pair signing authority
  • Audience-scope access-control authority

Đ44/UOSL (5)

  • semantic_thread family placement
  • Manifest/Review/Cut/Report families: separate or unified
  • Maturity ladder ↔ tool revision interaction
  • Multi-valued labels: first-class vs profile JSON
  • Family Registry closure for 6 new families

Đ32 Approval/Risk (2)

  • Fixed vs learned weights for coupling_score (D3)
  • Impact diff auto-generation vs hand-authored (D4)

Đ33/Đ43 PG Placement (2)

  • semantic_thread final placement if universal_edges insufficient
  • Default next_review_date per risk/kind (D5)

Technical Instrumentation (4)

  • Co-edit instrumentation reliance on current CDC
  • Exact threshold values for D3 signal scoring
  • Negative knowledge decay policy
  • Embedding scheme for thread centroids

4. Schema Gaps (56) by Priority

P0 — Required before any implementation planning (6)

  • canonical_address on tac_logical_unit
  • manifest_envelope + manifest_unit_block tables
  • cut_change_set with rollback_key
  • verify_result table
  • decision_backlog_entry table
  • review_decision table

P1 — Needed for MVP cutter (15)

  • Fields: semantic_role, risk_class, authority, birth_gate_class, reviewer_identity
  • Tables: report_envelope, cut_history_index, vocabulary_gap_register, manifest_diff view
  • Tables: health_signal_event, segmentation_health_report, f2_action_decision
  • Family Registry: manifest, review_decision, cut_change_set families

P2 — Needed for semantic threading (14)

  • Tables: semantic_thread, membership, candidate, evidence, health_signal, negative_knowledge, expected_chain
  • Fields: thread_hint, lifecycle_stage_hint, edge_readiness_notes, candidate_edges
  • Family Registry: semantic_thread family
  • Trigger: CDC + NOTIFY/LISTEN for birth events
  • Edge reassignment audit trail

P3 — Needed for retrieval/instrumentation (21)

  • Fields: visibility, readiness, publication_state, vector_projection_readiness, uosl_compat_version/status
  • Tables: retrieval_metric_event/aggregate, search_gap_signal, audience_filter_policy, thread_context_pack_cache, consumer_contract_log
  • Tables: capability_intake_record, impact_diff, no_impact_record, cutter_self_review_report, tool_revision
  • Tables: unit_health_score, thread_health_score, coupling_score
  • Alias/redirect table for superseded units
  • Family Registry: retrieval_metric, audience_filter_policy families

5. Governance Gaps (5)

  1. Threading roles — no Đ37 mapping yet
  2. Backlog custodian — no owner assigned
  3. Capability-intake reviewer — no role defined
  4. DOT-pair signing authority — no authority designated
  5. Audience-scope access-control authority — no policy owner

All route to Decision Backlog → Đ37 governance resolution.

6. Missing Instrumentation (9)

  1. Retrieval log events (D11)
  2. Co-edit detection (D3, D9)
  3. Co-citation capture (D3, D9)
  4. Co-retrieval capture (D3, D9)
  5. CDC plumbing — PG trigger + NOTIFY/LISTEN (D9)
  6. Thread centroid embedding (D11)
  7. Health-score aggregator (D3)
  8. DOT-pair signature recording (D1)
  9. Auth-context propagation (D11)

7. Explicit Blockers Before Implementation

  1. User must PASS design phase (all 4 gates)
  2. 5 governance gaps must have Đ37 owner assignment
  3. P0 schema gaps must have migration design (separate phase)
  4. Auto-accept thresholds must be decided by User
  5. Threading PG placement must be decided (Đ33/Đ43)
  6. Family Registry entries must be submitted to Đ44

8. Status

review_phase_status: ACTIVE
gate_1_safety: pending
gate_2_cutter: pending
gate_3_threading: pending
gate_4_readiness: pending
implementation_allowed: false
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/reviews/dot-iu-cutter-v0.1-design-review-control-2026-05-15.md