Principles and concepts
explanation/ answers “what is it, why, and how should I understand it?” It owns concepts and rationale, not independent interfaces, schemas, or acceptance requirements.
Reading order
- How OMK understands knowledge: Concepts of knowledge, entities, context, and carriers.
- Who OMK is for: Users, tasks, and product boundaries.
- The three stages: How doctor, eval, and observe work together.
- Architecture: Domain responsibilities and dependency rationale.
- Statistical rigor: Evidence, differences, and limits of conclusions.
- Related tools and scope: Understand tool boundaries by task.
Document responsibilities
| Question | Entry |
|---|---|
| What is it, and why this design? | This directory; define each concept once |
| What behavior, boundaries, and acceptance must implementation satisfy? | Domain specifications, marked current, partly delivered |
| How does a user complete a task? | Usage guides and guides/ |
| Where can I look up a field, flag, or API? | reference/, such as the sample format |
A document may link to another responsibility's authoritative source without duplicating a contract that can drift independently. See the contributing guide for maintenance rules.