Security & Governance5 min readchapterQuick Read
Authority, Autonomy, and Emergency Control
Define how authority is delegated, exercised, reduced, revoked, contained, and restored.
Status: Review readyRisk: criticalLifecycle: intent · execute · verify · deliver · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis is curriculum guidance. It does not by itself prove a production implementation.
study mode
A rapid review of the chapter’s existing Quick Read, principles, definitions, lessons, and review material.
Quick Read
~2 minThe chapter in one pass.
- Purpose: Define how authority is delegated, exercised, reduced, revoked, contained, and restored.
- Core distinction: Pause, cancel, revoke, quarantine, rollback, failover, and shutdown solve different failure states.
- Safety rule: Emergency containment must not depend on the component being contained or on an ordinary approval path that may be unavailable.
- Proof: Exercise the control, preserve evidence, verify the resulting state, and test recovery. A button alone proves nothing.
2. Enduring Principle
Authority is a revocable chain, not a role label
The chain records delegator, recipient, subject, purpose, scope, constraints, policy version, issued and expiry times, and revocation handle. The narrowest applicable ceiling wins. An agent cannot delegate authority it does not hold, change policy, approve its own high-risk result, or convert telemetry into acceptance evidence.
External review
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence