Anatomy and Lifecycle of an Understanding-Transfer Unit
SUMMARY
Defines the structure, lifecycle, revision behavior, and validity boundaries of a reusable understanding-transfer unit.
DETAIL
An understanding-transfer unit is a reconstructable reasoning object. It is not merely a note, transcript excerpt, summary, or final claim. Its purpose is to preserve enough semantic structure that another participant or AI can recover how an understanding was formed and use it under appropriate conditions.
A mature UTU contains several distinguishable layers. The intent layer records the purpose, question, or decision the unit addresses. The assertion layer contains the conclusions, distinctions, or operating claims being transferred. The rationale layer contains the causal links, evidence, examples, and why-chain supporting those assertions. The constraint layer records conditions that shaped the reasoning, including resource limits, timing, obligations, dependencies, and domain assumptions. The alternatives layer records options that were rejected, deferred, or left unresolved and explains why. The uncertainty layer identifies weak inferences, missing evidence, active disagreement, and conditions that could overturn the current reconstruction.
Stated material and reconstructed material must remain separable. A participant's words, actions, and explicit judgments form one layer. AI-inferred goals, latent assumptions, and reconstructed causal links form another. An inferred relation may become validated after correction, confirmation through application, or supporting evidence, but it should not silently become equivalent to source testimony.
A UTU normally passes through four states. In capture state, it consists of fragments, examples, questions, and context signals. In reconstructed state, a mediator has proposed a coherent structure but important relations may remain provisional. In validated state, the structure has survived correction or task-relevant tests. In stabilized state, the unit has clear boundaries, known dependencies, and a form suitable for reuse. Stabilized does not mean immutable: later evidence may reopen the unit.
Revision should preserve semantic continuity. A change should identify whether it alters a claim, a constraint, a causal relation, an applicability condition, or an uncertainty. Replacing the prose without preserving these distinctions makes it impossible to tell whether the underlying understanding changed or only its expression changed.
A unit should be split when one representation would combine materially different validity conditions, audiences, time horizons, decisions, or causal structures. It should be merged only when two units express the same underlying reasoning pattern under compatible assumptions. Similar vocabulary is not sufficient for merging. Closely related units may remain separate and be joined by refinement, application, contradiction, or adjacency edges.
The stable filename should name the mechanism or decision context carried by the unit. Internal systems may maintain richer metadata, but public navigation should remain understandable through text paths and explicit semantic relations.
WHY THIS EXISTS
Supports knowledge modeling, expert capture, reasoning preservation, revision systems, context packaging, and any task that needs a concrete unit of transferable understanding.
SOURCE CONTEXT POINTERS
- /concepts/ai-mediated-understanding-transfer-network/PRIMITIVES.txt
- /concepts/ai-mediated-understanding-transfer-network/PATTERNS.txt
- /concepts/ai-mediated-understanding-transfer-network/DEEP.txt
EVIDENCE QUESTIONS
- No evidence query recorded