University of Michigan - Ann Arbor

In a StateM runbook, each phase-level state node is organized into four distinct structural components:

1. `in_hook`: Executes setup operations upon entering the state, initializing state files and loading durable context or progress records.
2. `State body`: The primary open-ended execution space in which the agent retains discretion to reason, invoke tools, and edit files to solve phase-local tasks.
3. `out_hook`: Persists durable task progress, updates status receipts, and prepares workspace artifacts before state departure.
4. `before_transfer`: Evaluates blocking pre-commit checks; failing any check prevents transition commit and keeps the agent within the node for error repair.

Phase-Local Node Architecture in StateM

In StateM's phase-local node architecture, what occurs when an evaluation fails during the `before_transfer` component?

Which structural component of a StateM phase-level node serves as the primary open-ended execution space where the agent reasons, invokes tools, and edits files?

Learn Before

Related