Runtime Authority Envelope
Commit-time three-condition check that decides whether an AI action may execute.
What it is
The Runtime Authority Envelope (paper Section 13.4) checks three conditions at commit time before an AI-authorised action executes: approval validity, scope match, and state stability. Outcome is Permit, Deny, or Escalate.
When to use
- Before an autonomous AI executes a consequential action (transfer, order, patch, deploy).
- During incident response: replay authority checks to see what was permitted when.
- For audit: every check is logged with its three-condition rationale.
Walk-through
- 1Sidebar: Runtime governance > Runtime authority.
- 2Fill: initiative, action summary, declared scope data, action-time scope data.
- 3Submit. Result and the reasoning behind Permit/Deny/Escalate is logged and displayed.
Common pitfalls
- Treating Permit as approval. Permit means the three conditions pass; final accountability still rests with the named human owner.