Module tracking 

Experiment tracking types: run manifests, status, event envelopes, and the EventSink/Tracker traits.

A run is the unit of tracking — one training session, study, or fit — materialized as a directory of append-only logs plus small atomic JSON files. This module holds only the schema and trait contracts; the file-writing implementation lives in soma-runtime (LocalTracker), and a future remote backend implements the same Tracker trait.

Structs

EventEnvelope

One line of events.jsonl: a monotonic sequence number and wall timestamp wrapped around the event, with the event’s own event_type tag flattened into the same object.

GitInfo

Best-effort git context captured at run start.

GraphSummaryInfo

Compact description of the graph a run executed, with pointers to the full topology files inside the run directory.

RunManifest

Run manifest — written once, atomically, at run start.

RunStatus

Mutable run status — small, atomically rewritten (status.json).

Enums

RunKind

What kind of work a run tracks.

RunState

Lifecycle state of a run.

Constants

RUN_SCHEMA_VERSION

Version of the on-disk run schema (manifest + logs layout).

Traits

EventSink

A lossless, ordered consumer of events.

Tracker

A tracking backend bound to one run.