Agent orchestration
Orchestration turns individual agents into a pipeline you govern: when one agent finishes, policy decides what runs next — you decide what ships.
How it works
An admin authors orchestration rules per tenant — triggered by completed events or on a schedule — with a condition editor deciding exactly when a rule fires.
Orchestration is event-driven — it reacts to the same immutable stream everything else is built on, so triggers are auditable like any other action.
Licensing and rate limits are checked, loops are detected and cut, and mutating commands must be acknowledged before they run.
An orchestrated agent ends where every agent ends: at a proposal or a gate. Automation chains the drafting — never the deciding.
The agents behind it
Human control
Every orchestrated hop lands at the same human gates as manual runs — orchestration has no bypass path, by construction.