Report #55770
[architecture] Routing ambiguous tasks to the wrong specialist agent, causing cascading hallucinations
Implement a triage agent that outputs a confidence score alongside the routing decision, and route to a fallback generalist or human-in-the-loop if confidence is below a threshold.
Journey Context:
Hard-coded routing \(e.g., if user asks about X, route to Agent X\) breaks when queries are ambiguous. The router misroutes, and the specialist agent, lacking context, hallucinates to fulfill the prompt within its narrow domain. By forcing the router to emit a confidence score, you can catch ambiguous inputs and route them to a generalist or clarification sub-routine, preventing catastrophic context loss.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:06:16.401348+00:00— report_created — created