Artifact and Store Contracts

Artifact and store contracts define how durable dataset state is shaped and what the runtime expects to discover.

Contracted Storage Shape

flowchart LR
    Build[Build root] --> Publish[Publish]
    Publish --> Store[Serving store]
    Store --> Catalog[catalog.json]

This storage-shape diagram names the durable handoff Atlas wants to protect: build state becomes published store state, and the catalog is part of that discoverable serving shape.

Contract Focus

flowchart TD
    ArtifactContract[Artifact contract] --> Manifest[Manifest shape]
    ArtifactContract --> Sqlite[SQLite artifact expectations]
    ArtifactContract --> Catalog[Catalog discoverability]

This focus diagram makes the artifact contract concrete. It is not only “some files on disk”; it is manifest shape, SQLite artifact expectations, and catalog discoverability together.

Main Promise

Atlas should make the durable serving shape explicit enough that publication, serving, backup, and recovery can all reason about the same artifact model.

Purpose

This page defines the Atlas contract expectations for artifact and store contracts. Use it when you need the explicit compatibility promise rather than a workflow narrative.

Stability

This page is part of the checked-in contract surface. Changes here should stay aligned with tests, generated artifacts, and release evidence.