Learn Before
Context Boundaries, Contract Boundaries, and Transition Checks - Long-Horizon Agent Reliability: Stateful Scaffolding and Runtime Verification @ University of Michigan - Ann Arbor
Verification Typologies and Transition Protocols - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Check Typology and Transition Verification Protocols - Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Taxonomy of State Transition Checks by Evidentiary Strength
StateM distinguishes transition checks across four distinct tiers of evidentiary strength to prevent structured declarations from being mistaken for verified proof:
- Command and Predicate Checks: Evaluated directly by the host runtime, providing independently reproducible evidence (subject to the correctness of the command or predicate).
- Manual Checks: Require an explicit operational decision or approval from a user or human operator.
- Checklist and Message Checks: Require the agent to acknowledge specified obligations; these serve as structured self-attestations rather than independent verification.
- LLM Review Checks: Provide a separate qualitative semantic judgment without deterministic verification guarantees.
This evidentiary hierarchy ensures that self-attestations remain auditable and visible while reserving objective verification for deterministic or host-evaluated gates.
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
Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Ch.1 Operational Reliability and Verification - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Verification Typologies and Transition Protocols - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Ch.1 Execution Lifecycle and Fault Management - Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Check Typology and Transition Verification Protocols - Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Related
State as a Context Boundary
State as a Contract Boundary
Taxonomy of State Transition Checks by Evidentiary Strength
StateM Ordered Transition Protocol
Taxonomy of State Transition Checks by Evidentiary Strength
StateM Ordered Transition Protocol
Checked and Recoverable Transition Semantics
State as a Contract Boundary
Transition Guards and Repair Routing
StateM Ordered Transition Protocol
Formal StateM Runbook Specification
Taxonomy of State Transition Checks by Evidentiary Strength
Checked and Recoverable Transition Semantics
Learn After
Which category of state transition check provides independently reproducible verification evaluated directly by the host runtime?
Checklist and message checks provide independently reproducible verification because the agent must confirm procedural criteria before state transitions can occur.
Explain the architectural purpose of organizing transition checks into an evidentiary hierarchy in StateM, specifically contrasting how the system handles self-attestations versus objective verification gates.
Match each tier of state transition check in StateM to its operational implementation scenario.
StateM distinguishes transition checks across four distinct tiers of evidentiary strength to prevent structured declarations from being mistaken for verified ___.
Order the state transition check tiers as cataloged in StateM's hierarchy of evidentiary strength, from Tier 1 to Tier 4.
Which tier of state transition check should the team configure to satisfy this sign-off policy, and what specific action does this check type require?
What form of evaluation do LLM review checks provide during a state transition, and what specific guarantee do they lack?