Shared Control and Privilege Boundaries in Runbook Modification
StateM balances agent autonomy with governance by exposing runbooks as shared workspace artifacts while maintaining strict privilege boundaries between agent and user modifications:
- Agent-Authored Additions: An executing agent may dynamically register additional stricter checks or runtime notes when encountering unexpected operational risks, provided the runbook permits dynamic check registration. These additions are logged in the per-run history for subsequent human auditing and potential promotion into future runbook versions.
- User-Owned Invariants: Modifying, weakening, or removing existing invariants, permissions, and blocking transition checks requires a privileged policy decision. Agents cannot unilaterally weaken baseline constraints.
This shared control architecture enables runtime adaptation to emergent task conditions while preventing agents from compromising security invariants or bypassing transition contracts.
0
1
Tags
Prep Sessions
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
Learn After
Under StateM's privilege boundaries, which modification is an executing agent authorized to perform dynamically during execution?
In StateM, an executing agent has the authority to unilaterally weaken baseline constraints when encountering unexpected operational conditions.
What specific prerequisite must a runbook satisfy before an executing agent can introduce stricter checks at runtime?
Explain the architectural rationale behind StateM's division between agent-authored additions and user-owned invariants during runbook modification.
Match each runbook governance concept in StateM with its operational definition.
StateM's privilege architecture permits agents to dynamically adapt to emergent risks, but strictly prevents them from compromising security invariants or bypassing transition ___.
Order the lifecycle stages of an agent-authored check addition in StateM, from initial risk encounter to long-term adoption.
Based on StateM's privilege boundaries, evaluate whether each of the agent's two actions will be accepted or rejected, and explain why.