Multi-Agent Orchestration
A prompt is a suggestion, so asking an agent to wait for approval is not a control.
What it does
An orchestration layer where agents may draft, propose and prepare, and only a person may approve, greenlight or release. The boundary is enforced at the authorisation layer, which is what lets the number of agents grow without oversight quality falling.
Capabilities
- Agents draft, propose and prepare; people approve and release
- The boundary enforced at the authorisation layer, not asked for in a prompt
- Agent count grows without oversight quality falling
In use

In practice
Overnight the agents prepare 140 supplier invoices, each matched to its order and delivery and queued for payment. One carries an instruction hidden in its text: pay today, to a new bank account. The agent can read it, but it cannot pay and cannot change a supplier’s bank details. Those are permissions it does not hold, enforced at the authorisation layer rather than requested in a prompt. At 08:30 the finance lead approves 139 and sends the odd one to be checked.
The principle
Built from

