“Autonomous” is not a useful production permission. Authority must be specific enough to enforce, observe, and revoke.
A practical model has five levels:
| Level | Agent capability | Typical control |
|---|---|---|
| Read | Retrieve approved information | Data scope and audit log |
| Recommend | Propose an action | No system change |
| Prepare | Create a draft transaction | Human review before submission |
| Execute | Perform an approved action | Policy, amount, and time limits |
| Reverse | Correct or roll back an action | Separate permission and evidence |
An agent can operate at different levels inside the same workflow. A hospitality agent might send check-in instructions, prepare a reservation change, and require approval before issuing a refund. A banking agent might gather KYC evidence but remain unable to approve a customer or restrict an account.
Start with the lowest level that creates measurable value. Expand authority only after production evidence shows that the agent completes the workflow correctly, stays within policy, and escalates exceptions as designed.
Before granting write access, define:
Track successful workflow rate, policy denials, false denials, escalation rate, unauthorized-action attempts, rollback frequency, and unresolved exceptions. These measures show whether authority can expand safely.
Progressive authority gives security, compliance, operations, and engineering teams evidence instead of an abstract promise. It also prevents a successful prototype from receiving broad production access simply because that access was convenient during development.
Cayru helps companies define authority levels, approval limits, and the evidence required to move an agent from recommendation to controlled execution.
Review an agent’s authority model before granting write access.