State and Persistence

State is the reason this crate exists.

Main Persisted Families

• dataset registry entries and sidecar-derived metadata
• run identity, directory layout, and front-end provenance
• manifests, reports, history entries, and artifact headers
• provenance hashes and environment evidence

Persistence Boundary

Infra owns how repository state is laid out and interpreted. It does not own the semantic meaning of core artifact payloads or the runtime-side production of those payloads.

Durability Rule

Run footprints should remain understandable after the command and process that created them are gone. That is the architectural standard here, not a nice-to- have.

First Proof Check

• the run-layout guide
• the dataset registry source
• the run-layout facade
• the run-record source
• the persistence source
• the front-end provenance source
• the provenance hash source