Storage, Completion, And Manifest

The output runtime has no database locally. A simulation’s state is split between three small pieces: completion is computed by key from the store, the manifest is a parquet registry of what was registered, and storage helpers locate project inputs, outputs, and backing stores.

Completion

A simulation is complete iff every artifact it is configured to produce exists in the store (see stilt.completion).

stilt.completion.StatusCounts	Aggregate completion counts for one project or scene.
stilt.completion.expected_artifacts	Return the artifacts a complete simulation must produce.
stilt.completion.is_complete	Return whether one simulation has produced all of its expected outputs.

Manifest

The registry of registered simulations, persisted as .stilt/manifest.parquet through a Store. Registration metadata only; completion is never stored here.

stilt.manifest.Manifest

Registry of registered simulations, persisted as .stilt/manifest.parquet.

Storage helpers

stilt.storage.ProjectLayout	Resolved local directories and output refs for one model instance.
stilt.storage.ProjectFiles	Local paths plus output key conventions for one project root.
stilt.storage.SimulationFiles	Local paths and output keys for one simulation's standard outputs.
stilt.storage.Storage	STILT-aware output storage facade over a lower-level store backend.
stilt.storage.FsspecStore	Output store backed by an fsspec remote filesystem.