Learn Before
Persistent Run State and Recoverable Execution Protocols - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Per-Run State Persistence, Recovery, and Stop Hooks - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Runtime Persistence, Recovery, and Stop Hooks - Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Recovery Anchor and Recovery Scope in StateM
The persistent per-run record in StateM functions as an external recovery anchor during process restarts, context refreshes, or model-side compactions. Rather than forcing the agent to infer its current position from a noisy terminal transcript, the agent queries StateM to retrieve the authoritative phase, past transitions, unresolved checks, and evidence files.
The scope of this recovery is specifically procedural rather than transactional:
- Recoverable scope: StateM restores its recorded control state, active obligations, and configured repair routines.
- Non-recoverable scope: StateM cannot reconstruct unpersisted working memory, retrieve hidden model activations, or execute ACID-style rollbacks of arbitrary external environment side effects.
Reliability therefore depends on positioning persistence hooks at phase boundaries and ensuring hooks are idempotent to tolerate re-execution.
0
1
Tags
Prep Sessions
Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Ch.3 State Persistence and Continuous Optimization - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Persistent Run State and Recoverable Execution Protocols - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Ch.2 Runtime Lifecycle and State Management - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Per-Run State Persistence, Recovery, and Stop Hooks - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Ch.1 Execution Lifecycle and State Boundaries - Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Runtime Persistence, Recovery, and Stop Hooks - Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Related
StateM Per-Run Execution Record
Recovery Anchor and Recovery Scope in StateM
Operational Run Situations in StateM
StateM Stop Hook Integration and Execution Continuation
Shared Control and Privilege Boundaries in Runbook Modification
Checked and Recoverable Transition Semantics
StateM Per-Run Execution Record
Recovery Anchor and Recovery Scope in StateM
Operational Run Situations in StateM
StateM Per-Run Execution Record
StateM Stop Hook Integration and Execution Continuation
Recovery Anchor and Recovery Scope in StateM
Operational Run Situations in StateM
Checked and Recoverable Transition Semantics
Learn After
Which component falls within the recoverable scope of StateM during a recovery event?
The recovery scope provided by StateM is transactional rather than procedural.
What two implementation requirements for persistence hooks are necessary to maintain execution reliability in StateM?
Classify StateM's recovery scope as procedural or transactional, and explain the architectural boundaries that define what it can and cannot restore.
Match each recovery and persistence concept in StateM to its correct description.
Order the sequence of actions that occur when an agent relies on StateM to resume execution after an interruption.
Analyze why StateM did not revert the cloud firewall configuration or restore the agent's scratchpad variables following the crash.
During process restarts, context refreshes, or model-side compactions, the persistent per-run record in StateM functions as an external ___ anchor.