Skip to content

Build / Publish / Activate

V9 separates three lifecycle operations:

BUILD != PUBLISH != ACTIVATE

BUILD

Produces candidate Logical Artifacts and materializations from declared Derivations.

BUILD does not change the active state.

PUBLISH

Validates candidates and creates an immutable State Snapshot.

Recommended order:

1. write physical blobs
2. verify blob digests
3. write materialization manifests
4. reconstruct/verify logical commitments
5. construct immutable State Snapshot
6. validate snapshot
7. publish snapshot

ACTIVATE

Moves a mutable channel pointer such as production or HEAD to a published immutable snapshot.

production → S42

may atomically become:

production → S43

S42 remains unchanged.

Crash consistency

A failure before activation must leave the previous active state usable. Unreferenced candidate blobs may later be garbage-collected.

Concurrent publication

A publisher may use compare-and-swap semantics against the expected previous commitment. A pointer conflict is not automatically a semantic conflict.

STORAGE CONFLICT != SEMANTIC CONFLICT

Rollback

Rollback selects a retained prior immutable snapshot. It does not rewrite history to pretend the newer snapshot never existed.