Skip to content

Latest commit

 

History

History
53 lines (46 loc) · 2.97 KB

correspondence.md

File metadata and controls

53 lines (46 loc) · 2.97 KB

State correspondence

Candidate ecosystem correspondence

At this revision, OpenMontage persists schema-validated stage checkpoints with completed, failed, awaiting_human, and in_progress status. Its helper derives the next pipeline stage from completed checkpoints, while the checkpoint protocol tells execution to resume partial work, wait for approval, or advance depending on persisted status. This is source evidence for persisted and resumed task-state-controlled behavior.

The correspondence remains candidate. The reviewed files centralize checkpoint logic and status branches; they do not materialize separate GoF State and ConcreteState participants or show a Context delegating the same operation to those objects. Static source inspection also does not prove end-to-end Agent Runtime behavior. Checkpoint vocabulary alone is not sufficient to confirm State.

Constructive sample

The Context reloads one versioned record, delegates to a distinct ConcreteState, and atomically persists the successor only after legal handling. Tests prove restart recovery, deterministic rejection before write, deletion and corruption rejection, and stable fixture output. This local construction is independent of the OpenMontage case and does not establish Agent Runtime interpretation.