Open table of contents
Conclusion
Manage user intent separately from the authority available to tools.
Context
An agent operating with more authority than its requester blurs delegation boundaries. Distinguish requester, executor and approver.
Design and verification scope
Assess the following responsibilities and boundaries when designing and verifying a configuration.
- Delegation
- OAuth scopes
- Tenants
- Approval
- Idempotency
- Audit
Decision rationale
Use the relationship between Delegation and Audit to compare the responsibilities of the selected approach and alternatives. Separate retained constraints from what the new boundary can change.
Trade-offs
Compare the implementation, maintenance and review work introduced by OAuth scopes with the control it provides. Include failure paths, operator effort and conditions in which the approach should not be adopted.
Limitations
Review permission matrices, approvals and delegated-action audit records. The SaaS case is not a production agent deployment claim.
Related case context
These cases provide attributed design context. They do not establish that the proposed experiments or configurations were delivered in those engagements.