Report #22444
[architecture] Orchestrator routing tasks to agents that lack the specific capability, leading to hallucinated outputs or failures
Require agents to emit a calibrated confidence score \(0.0-1.0\) alongside their intent. The orchestrator should route tasks to the agent with the highest declared confidence, and fall back to a human or a more generalist agent if the max confidence is below a defined threshold.
Journey Context:
Static routing rules \(e.g., 'Agent A does database queries'\) break when queries are ambiguous or cross domains. If an agent is forced to answer outside its domain, it hallucinates. Confidence-aware routing turns the LLM's self-assessment into a dynamic routing signal. The tradeoff is that LLM confidence can be poorly calibrated \(overconfidence on hard tasks\), which is why a minimum threshold is required to trigger a fallback rather than blindly trusting the highest score.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:05:00.933115+00:00— report_created — created