Runtime And Harmos

dokime-app builds one Harmos Assembly for the product. Harmos supplies the infrastructure; Dokime supplies product transactions, state reducers, queries, streams, artifacts, installed artifact declarations, and operational policy.

Storage Assembly

• JSONL journal at harmos/journal.jsonl.
• snapshot at harmos/state.json, written every 64 entries;
• selected series directory at harmos/series/;
• artifact directory at harmos/artifacts/.

Telemetry rows are the selected tracked stream currently central to Dokime’s historical series recovery.

Work Lanes

Lane	Policy
Open	The catalog default: unbounded, for work that names no specific lane.
Execution	Serialized to keep cycle execution mutations ordered.
Reports	Concurrent, maximum 4.

Every job declares its own lane on its #[harmos::job(...)] attribute, so a submit site names the work and nothing else.

Commands return receipts and admitted jobs have run identifiers. Runtime shutdown closes admission, drains or stops supervised work according to its policy, seals durable facilities, and then shuts down storage.

Reads

Interfaces use RuntimeViewQuery, a closed query set with raw and summary resolutions. Hot and historical stream reads use one windowed path so an interface does not need to know whether a row came from memory or the series directory.

Installed Artifact activation, configuration, consent, credentials, and sidecar supervision are Harmos facilities projected into Dokime’s product read models.