Section 4
Dependency Graph
The graph below shows the strict assembly order. An arrow from A to B means B cannot start until A is complete. Layers 3a and 3b (State and OTel) are parallel — neither depends on the other.
Single highest-risk transition: Layer 2 → Layer 3. If OTel instrumentation is added after the runtime is written, interface refactoring is almost certain. Instrumentation hooks must be present from the first iteration of the runtime, even if they emit nothing initially.
Critical path (linear)
artifact model → runtime → state + OTel # parallel → API v0 # freeze point → CLI → workloads → benchmark → whitepaper v0.1