ORK modules
Per-module specs for @mdk/ork: responsibility, interfaces, state machines, recovery, and scaling.
@mdk/ork's coordination splits across single-purpose modules. Each owns its own state machine, persistence boundary,
and scaling characteristics. Six modules ship in v0.0.1; two more (Fault Supervisor, Concurrency Manager) are deferred
to a later release.
For the architectural overview that explains how these modules connect, see Architecture. This page is the per-module spec.
How to read this page
Each accordion below covers one module:
- Responsibility: what the module owns and the example commands or events it handles.
- Interfaces: input and output channels, plus the public function names callers depend on.
- State machine: the canonical diagram for the module's internal lifecycle.
- Crash recovery: behavior on a fresh start, including how state is reconstructed.
- Scalability: where the module can be extracted, sharded, or replicated.