Anatomy of an orchestration run
- Tools and channels01TriggerAn event or request starts the run
- Agentic Hub02PlanTasks, owners, and risks
- People03Review planPeople adjust and approve
- Agentic Hub04DelegateRoute each task with full context
- Specialist agents05ExecuteParallel where possibleEscalates to people when unsure
- Agentic Hub06CheckGuardrails and consistency
- People07ApproveConsequential work
- Tools and channels08ActPublish, send, or update
- Agentic Hub09LearnMeasure and log results
- Results inform the next plan, back at step 02.
How a single piece of work moves through the Agentic Hub, from the event that starts it to the results that shape the next plan. Four lanes show who acts at each step.
What each part does
Trigger
An event or request starts the run: a form fill, a usage milestone, a performance change, or a person's brief.
Plan
The hub's planner turns the goal into tasks with owners, inputs, outputs, and risks.
Review plan
For consequential work, a person reviews and adjusts the plan before anything happens. Plans are cheap to change.
Delegate
The router sends each task to a specialist with a handoff contract: payload, context, assumptions, and acceptance criteria.
Execute
Specialist agents do the work, in parallel where tasks are independent. When unsure, they escalate instead of guessing.
Check
The hub runs hard guardrails and a consistency review across all outputs before anything moves forward.
Approve
People approve consequential work. The state model makes this step impossible to skip.
Act
Approved actions run through governed connectors: publish, send, schedule, or update.
Learn
Results are measured and logged against the run, and they inform the next plan.
See the architecture in the product
Marketix is built on these diagrams: specialist agents, governed connectors, and a hub that plans, routes, and records every run. Sign up for early access.
