pub struct Checkpoint {
pub idempotent: bool,
pub hashed: bool,
pub verify: Option<Value>,
}Expand description
Per-phase checkpoint declaration. Three legal forms in YAML:
checkpoint: idempotent— short form, equivalent toCheckpoint { idempotent: true, hashed: true, verify: None }.checkpoint: none(orfalse, orno) — explicitly not skip-eligible. Equivalent to no declaration; the phase always re-runs on resume.checkpoint: { idempotent: true, hashed: true, verify: ... }— full mapping form with sub-properties.
See SRD-44 §“Forms” and §“Sub-properties” for the full
contract. The Default is “skip-eligible with hashing on,
no verify” — what the short form idempotent produces.
Fields§
§idempotent: boolMarks this phase as skip-eligible on resume. false
here is equivalent to checkpoint: none and means the
phase always re-runs.
hashed: boolWhen true (the default for any set checkpoint
declaration), the resume planner additionally verifies
that the freshly-pre-mapped phase’s compiled program
hash matches the saved one before honouring the saved
status. false is the operator opt-out — “trust
structural identity (yaml_path + coords) alone”.
verify: Option<Value>Optional verify op-template body. When present, the resume planner runs this op against the live system before classifying the phase as Skip; verify failure reclassifies to re-run with wholesale purge. Currently typed as a generic YAML value — the runtime re-parses it through the op-template grammar so the existing pipeline (SRD-32 wrappers, SRD-03 status- determination invariants) governs the verify execution.