State as a Contract Boundary
In stateful agent harnesses, a state functions as a contract boundary governing phase completion, verification, and transition gating. While the state prompt defines the expected internal work of the phase, the runtime enforces explicit exit conditions before permitting a transition. An exit hook (out_hook) persists progress, updates receipts, or prepares artifacts for the subsequent phase, while a pre-transfer block (before_transfer) evaluates configured exit conditions. If a check fails, the run remains in the source state to enable inspection and repair rather than silently propagating unverified work or incomplete handoffs into later phases.
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
Context Boundaries, Contract Boundaries, and Transition Checks - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Learn After
Which component in a stateful harness evaluates mandatory completion criteria before permitting an exit from a state?
True or False: In a stateful harness, the phase prompt is responsible for actively enforcing transition conditions before permitting an exit.
Identify the three actions handled by an exit hook (
out_hook) when preparing to depart a state.