Expand description
Workload checkpointing — see SRD-44.
Submodules:
identity—PathSegment,PhaseIdentity, and the per-phase canonical-program hash. Identity is per-phase (no workload-level identity tuple) and(yaml_path, coords)is necessary; the program hash is sufficiency.storage— JSON file format + atomic-rename writer.writer—CheckpointWriteractor: subscribes to phase-lifecycle events, flushes on the metrics-tick cadence with sqlite-fsync-then-checkpoint-fsync ordering.resume— resume planner: loads checkpoint, classifies each freshly-pre-mapped phase per the resume protocol, produces aResumePlanthe executor consults before dispatch.
Re-exports§
pub use events::CheckpointData;pub use identity::PathSegment;pub use identity::PhaseIdentity;pub use resume::ResumeAction;pub use resume::ResumePlan;pub use storage::Checkpoint;pub use storage::OpCounts;pub use storage::PhaseEntry;pub use storage::PhaseStatus;pub use writer::CheckpointWriter;
Modules§
- events
- SRD-44a — Checkpoint event taxonomy.
- identity
- Per-phase identity for checkpoint match / mismatch decisions.
- params_
scope - SRD-107 — the consumed-params derivation.
- resume
- Resume planner — classify each freshly-pre-mapped phase
against the saved checkpoint document and emit a
ResumePlanthe executor consults before dispatch. - storage
- Checkpoint storage — fold-state types + JSONL event-log reader.
- writer
CheckpointWriter— append-only event-log owner for the per-session checkpoint document. SRD-44a §“Writer behaviour”.
Functions§
- declare_
scene_ tree_ phases - Declare every phase node in a freshly-pre-mapped scene tree
to the writer. Called once at session bootstrap, immediately
after [
crate::executor::pre_map_tree] returns. Each phase gets aPendingentry with no hash; the runtime updates the hash viaCheckpointWriter::update_phase_hashwhen the phase compiles. - scene_
tree_ resume_ candidates - Build a list of
(identity, declared_idempotent)pairs for every phase the scene tree will execute. The runner feeds this toResumePlan::from_checkpointwhen resuming, so the planner can classify each freshly-pre-mapped phase against the saved document.