Route work to specialists through explicit task and permission boundaries. A specialist label does not prove expertise, grant access, or establish who may perform the final business action.
Specialist routing is a constrained assignment
Specialist routing selects a worker for a defined subtask based on supported capability, access scope, availability, and expected result. It should not let the receiving agent expand the task independently.
For a proposed registry, record accepted task types, required input contract, result schema, evidence access, permitted tools, deadlines, and fallback owner. The trusted orchestrator validates the assignment and applies the current business policy.
Keep interpretation and execution separate where appropriate. A scheduling specialist may identify options without permission to book. A policy specialist may explain an eligibility rule without authority to override it.
Route a fictional billing dispute
A caller begins with a service appointment question, then disputes an invoice. The coordinator identifies the changed intent and sends a bounded evidence packet to the billing-analysis specialist. It does not pass unrelated customer history or permit an automatic refund.
If the billing specialist requests an action outside its scope, the orchestrator treats it as a proposal requiring the proper owner and checks. A confident recommendation should not silently widen the available tool credentials.
| Routing condition | Boundary assertion |
|---|---|
| Supported billing analysis | Relevant evidence and expected result only |
| Ambiguous task type | Clarification or general triage |
| Specialist lacks resource access | No bypass through another agent |
| Task changes after handoff | Current revision governs returned work |
| Specialist unavailable | Defined fallback, not improvised authority |
Test overlapping capabilities and adversarial requests that try to route around a denied permission. The selected worker must not become a path to data unavailable to the caller or coordinator.
Make specialist value observable
Track correct outcomes, handoff failures, latency, cost, and operational clarity against a simpler baseline. A larger registry can improve modularity, but it can also create confusing routing decisions and repeated evidence retrieval.
Version the capability contracts and review them when tools or policies change. Keep one business-action owner even when several specialists contribute evidence. Staff should understand which component is responsible for the next step, not just which agents participated.
This routing architecture is proposed. The voice integration case study describes related retrieval and tool work. Pair it with structured agent handoffs.
Specialist routing FAQ
Does a specialist name establish authority?
No. Permissions come from trusted application policy and the specific resource relationship.
Should every intent have its own agent?
Only when the separation provides a supported benefit that justifies coordination cost.
What should happen to an out-of-scope result?
Reject or route the proposal through the proper authority boundary without executing it automatically.