Recover Telemetry

Telemetry is not only a live UI feed. Dokime publishes each accepted sample as a tracked Harmos series row and queries the durable series together with the in-memory window.

Publication Path

1. A installed artifact declares a telemetry channel and schema.
2. The runtime validates each payload against that contract.
3. Samples for a closing or non-running execution are dropped.
4. Accepted samples receive a cursor and are published to the telemetry stream.
5. The stream tracks cycle and execution scopes and retains a 16,384-row hot window.

The stored row contains the scope, channel, cursor, timestamp, and payload bytes. Plot and telemetry queries filter the combined historical/hot result by scope and cursor.

What Survives Restart

The Harmos series directory persists rows beneath <storage-root>/harmos/series/. On boot, Dokime queries recovered streams to reconstruct the last cursor per scope. New samples continue after that cursor, so a process restart does not reuse an existing coordinate.

Repository integration tests exercise a hard process stop and reboot, then verify that prior cycle telemetry remains queryable and that newly published rows do not collide.

Durability Boundary

seal is the explicit telemetry durability barrier. A completed execution uses runtime shutdown/finalization paths that seal storage. A client should not infer durable persistence merely from seeing a WatchRuntime invalidation.

Legacy Keel data is left untouched by the Harmos migration. The current runtime does not translate it into the new series layout.