Orchestration Layer · Event bus
In developmentEvents, handoffs, webhooks and shared memory on one bus, with every run traced end to end. Agents that cooperate, fail loudly and never act on high-risk tools alone.
Trace · 8 spans
2,480 ms end to end
email.received
40 msintake.parse
180 msmemory.lookup_customer
50 mstriage.classify
370 mshandoff → quote_agent
28 msquote.draft
1242 msrisk.check send_quote
36 msapproval.request
534 ms
What it handles
Everything between one agent finishing and the next one starting.
Most agent projects fail in the gaps: a handoff nobody logged, a webhook that silently stopped, context that never arrived. The Orchestration Layer owns those gaps.
Events
Agents publish what happened. Others subscribe to what they need. No brittle point-to-point wiring.
quote.requested → triage_agent
Agent handoffs
One agent finishes its job and passes the work, with context, to the next. Every handoff is an event you can see.
triage_agent ⇢ quote_agent · ctx 3
Webhooks
Your CRM, ERP and inbox trigger agents, and agents call back out, through one governed entry point.
POST /hooks/crm · 200 · 84 ms
Shared memory
Customer context, prior decisions and state live in one place, so agents stop asking each other the same question.
customer:4471 → sla_tier, last_quote
End-to-end traces
Every run is traced from trigger to outcome, with each span timed. Know exactly where the seconds went.
run 7f3a · 8 spans · 2,480 ms
Error history
Every failure is logged with what happened next: retried, escalated or stopped. Nothing fails quietly.
quote.draft timeout → retry 1/3 ✓
End-to-end traces
One handoff, traced from trigger to human.
A quote request arrives by email. Three agents and a human touch it. The trace shows every event, every handoff and every millisecond, so when something is slow or wrong you know exactly where.
- Agent spans
- Tool and memory calls
- Handoff on the bus
- Waiting on a human
run 7f3a · quote request
8 spans · 2,480 ms · 1 handoff
email.received
webhook
40 msintake.parse
intake_agent
180 msmemory.lookup_customer
shared memory
50 mstriage.classify
triage_agent
370 mshandoff → quote_agent
bus
28 ms · context: 3 itemsquote.draft
quote_agent
1242 msrisk.check send_quote
policy
36 ms · mediumapproval.request
Rendly
534 ms · waiting on a human
quote.draftrun 7f3a08:41:07
Model timeout after 30 s
→ Retry 1/3 succeeded
crm.updaterun 81c009:12:55
Webhook returned 401
→ Owner alerted in Rendly
intake.parserun 8a2210:03:19
Attachment unreadable
→ Routed to a human
triage.classifyrun 9d0411:47:02
Confidence 0.41 below 0.70 threshold
→ Held for human review
dispatch.planrun a1f913:30:44
Auth token expired
→ Run stopped · logged
Logging and error history
Agents fail. Ours fail out loud.
The most expensive agent failure is the one nobody notices: a routine that stopped three weeks ago, a token that expired overnight. Every error is logged with what happened next, and the owner hears about it.
Retried
Transient errors retry with limits.
Escalated
Owners alerted in Rendly.
Stopped
Unsafe runs halt and are logged.
Principles
Built so agents can be trusted, a little at a time.
One agent, one job.
Small agents with one clear responsibility are easier to test, trust and replace. The bus lets them work as a team without becoming one tangled agent.
Staged autonomy.
Agents earn rights the way people learn to ride a bike: drafts first, one action next, full rights only after weeks of clean runs.
Humans on high-risk actions.
No agent moves money or signs a commitment without a named person approving it. That is enforced by the tool's risk rating, not by a prompt.
Tool risk table
Every tool an agent can call is risk-rated before it ships. Example below.
Staged autonomy · the bike method
Nobody learns to ride without stabilisers.
Agents earn autonomy in five stages. Each one has a clear gate, and autonomy can be dialled back at any time. Step through it, or let it play.
Stabilisers on: the agent drafts, a human sends.
- The agent
- Drafts replies, quotes and updates. Sends nothing.
- The human
- Reads every draft, edits, and sends it themselves.
- Move on when
- Drafts need few edits on real work.
The Anoryx EcoSystem
One EcoSystem. Four parts. All inside your walls.
Every Anoryx product is self-hosted and built to work alongside the others. Start with the one that hurts most.
Agents that work as a team.
And answer to yours.
The Orchestration Layer is in development. If you are running more than one agent, or planning to, tell us where the handoffs hurt.