dot-iu-cutter v0.1 — Agent Design Handoff Notes

Date: 2026-05-15 Purpose: Companion notes for Agent design phase. Read alongside rev5d. Status: Active — controls Agent design scope.

1. Controlling Document

knowledge/dev/laws/dieu44-trien-khai/requirements/dot-iu-cutter-v0.1-operational-problem-statement-rev5-assembly-axis-uosl-integrated-2026-05-15.md

Version: rev5d | Status: Ready for User approval. Agent design may start only after explicit User approval. Agent MUST read fully. All 56 questions, 50 criteria, 15 principles are binding.

2. Design Priority Order

1. Cut Flow (Resolve → Mark → Review → Cut → Verify → Report)
2. Manifest and Operator Contract (fields, review checklist, PG persistence)
3. Semantic Threading (objects, intake, enrichment, lifecycle)
4. Thread-first Retrieval (context pack, resolution, fallback, metrics)
5. Health / Correction (signals, health report, split/merge/edge)
6. Capability Intake (TAC/KG upgrade loop, impact diff)
7. Decision Backlog Registry (PG table, sweep, governance routing)
8. Assembly Axes Metadata Contract (reconstruction + semantic fields)
9. UOSL / Đ44 Compatibility (profile mapping, schema gaps)
10. Legal Alignment Report (Đ24/Đ32/Đ33/Đ37/Đ38/Đ39/Đ43/Đ44/Đ0-G)
11. Design Report (summary, open decisions, risk, next steps)

3. Hard Boundaries

DESIGN ONLY. No code, no PG mutation, no migration, no DDL, no vector/Qdrant, no nginx, no UI build, no self-dispatch for implementation.

4. Gap Handling

• Schema gap → record, recommend, do NOT invent schema
• Law conflict → STOP, report. Do NOT override law
• Missing instrumentation → classify requires_instrumentation, design hook, note gap
• Unclear authority → flag for User/Council. Do NOT assume

5. PG-First

Every data structure must specify: target DB, target layer (Não/Kho/Cổng), why PG not text. If text: justify.

6. Key Guardrails

Thread ≠ Edge. SKOS conceptual only. W3C PROV for evidence. User-directed = intent not auto-truth. Auto-accept risk-gated. universal_edges first. Đ24 no parallel taxonomy. Đ37 governance map. Đ32 high-risk approval. Đ33/Đ43 explicit target DB. Đ44 controlled draft. Đ0-G distinguish base/draft/runtime. Access control = security requirement.

7. Output Format

Each deliverable: standalone KB markdown. Must contain: purpose, scope, dependencies, key decisions with rationale, schema gaps, law references, open questions, PG storage per object.