Delegation
Delegation is one party handing a task, and part of its authority, to another. In a chain of AI agents it decides what the next agent may do when the work is passed on.
In a run
When one agent hands work to another, Ares gives the next agent the overlap of the caller’s permission and what the next agent needs. The handoff, the narrowed permission and the agent that received it go on the record.
Our word for it
The permission narrows at each handoff.
Narrower or the same, never wider
A permission can get smaller or stay the same at each handoff. It never grows. A downstream agent never holds more than the agent that called it.
This matters most in long chains. An agent three handoffs down still holds no more than the person who started the job could give. The record shows each handoff, so you can follow the permission from the first agent to the last.
Delegation to another company
The same rule holds when the work crosses to a supplier. In the two-company sandbox run, a buyer’s agents ask a supplier’s agents for a quote on one order line, and the supplier’s agent reaches for the buyer’s full bill of materials. The permission narrows at the company boundary, and both records agree on what crossed it. More on working across organisations.
Where it stops
- Delegation limits what the next agent may do. It does not check whether the task was the right one to hand on.
- Widening a permission is never part of a handoff. It waits for a person.
- It covers handoffs between agents enrolled in Ares.
Related terms
- Least privilegeLeast privilege means an account holds only the access it needs for its task, and nothing more.
- Agent-to-agent (A2A)Agent-to-agent (A2A) is an open protocol that lets AI agents built by different teams find each other and pass work between them.
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.