Platform / Orchestration
Coordinating the steps, not just answering the prompt.
Orchestration is the layer that turns a goal into a sequence of tool calls, memory updates, and decisions — and knows when a step needs to loop back or hand off.
How a task moves
Plan, act, update memory, repeat until done.
Scroll to see the full diagram →
Task
The orchestrator receives a goal and the context needed to work on it.
Key concepts
What orchestration is responsible for.
Multi-step planning
The orchestrator breaks a goal into steps and re-plans as new information comes back.
Tool calling
Actions happen through defined tool interfaces, not free-form access to systems.
Memory
State from earlier steps — and earlier runs, where relevant — informs what happens next.
Hand-offs
A workflow can pass a sub-task to another agent with its own defined scope.
Guardrails
What orchestration does not decide.
Orchestration decides how to sequence steps toward a goal — it does not decide whether a step is permitted. That check happens at the policy gate, independent of the orchestrator's plan.
A planning loop has a bounded number of steps and a timeout, so a workflow that isn't converging surfaces for review instead of running indefinitely.
Map orchestration to a real workflow.
Bring a multi-step process and we'll walk through how it breaks into planned steps, tool calls, and checkpoints.