StateM Runbook
In StateM, a runbook is a human-readable and machine-operable YAML specification that defines the control profile for an agent workflow. It details phase-level states, permitted transitions, state-local instructions, lifecycle hooks (in_hook and out_hook), verification checks (before_transfer), and error-recovery rules. The runbook is hosted directly in the shared workspace, enabling the executing agent to inspect its current state, execute transitions, and record dynamic checks via standard CLI operations, while allowing human supervisors to inspect, audit, edit, and version the exact same control artifact.
0
1
Tags
Prep Sessions
Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Ch.2 Runtime Architecture and Boundary Control - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
StateM Runtime and Runbook Architecture - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Learn After
Which set of lifecycle hooks and verification checks is detailed in a StateM runbook YAML specification?
In StateM, human supervisors must use a separate, proprietary GUI tool to audit runbooks because the control artifact cannot be inspected or edited directly by humans.
Through what operational interface does an executing StateM agent inspect its current state, execute transitions, and record dynamic checks in the shared workspace?
Formal Runbook Specification in StateM
Phase-Local Node Architecture in StateM