Architecture Reference

Runtime<A> is the composition root. It exposes Journal<A> for truth, Streams<A> for high-rate observations, and Work<A> for finite and resident activity. Storage<A> supplies recovery and durable folds.

The boot order is fixed:

Reading Order

An application declares one dependency. Every crate page below documents a crate reached through a harmos feature — harmos::artifact, harmos::sidecar, harmos::guest — rather than a dependency a consumer adds. The last page is not a crate to depend on at all: harmos ships storage contracts, and the reference adapter is an example an application copies.

1. harmos for application, journal, streams, work, and composition.
2. harmos-macros for authoring declarations.
3. harmos-sidecar for native processes.
4. harmos-guest for Wasm components.
5. jsonl-adapter when history crosses onto disk — a worked implementation of the storage ports, written to be copied.

Sidecars and guests are directly registered artifacts. Their declarations are read before execution and their dependency graph is planned through harmos::load::Plan. Neither is required for recovery.

harmos-signal deliberately has no runtime edge. It contains signal mathematics over ordinary slices.