Module stage 

The stage: a persistent workbench holding one rendered candidate.

A stage is evidence an agent reads. It holds every destination the candidate would land, the reference material of the exact installed version, and a receipt describing both. It is written outside the target and never into it, and no production verb reads a byte of it: a landing renders the candidate again from this binary’s own sources.

The directory is renamed into place once it is complete, so a stage a reader can see is a stage that finished. Only sdd stage clean removes one, and only after the receipt inside it says this tool wrote it.

Structs

Artifact

One artifact the stage carries, and what a landing would do with it.

Receipt

The receipt a stage carries, and the report the command prints.

Request

What a stage was asked to render.

Enums

RootSource

Which rule chose the stage root, for the report that names it.

Constants

ARTIFACTS_DIR

Where the candidate’s own destinations are rendered.

RECEIPT_FILE

The receipt every stage carries, and the one file clean trusts.

REFERENCE_DIR

Where the installed version’s reference material is copied.

STAGE_ROOT_VAR

The base directory an automation points every stage at.

STAGE_SCHEMA

The machine schema stage.json declares.

Functions

clean

Remove one stage this tool wrote, and refuse anything else.

create

Render one candidate into a stage, and report what it holds.

resolve_root

Where a stage goes, and which rule decided.