Report #6048
[architecture] A router agent sending tasks to the wrong specialized agent because it doesn't evaluate its own uncertainty
Require the router to output a confidence score alongside its routing decision. If confidence is below a threshold, route to a generalist agent or prompt the user for clarification instead of guessing.
Journey Context:
Zero-shot routing often forces a choice even when the intent is ambiguous. By forcing a confidence score, the system acknowledges uncertainty. Low confidence means fallback, preventing the downstream specialist from hallucinating capabilities it doesn't have. The tradeoff is that forcing confidence scoring adds a few tokens and latency, and requires tuning the threshold to avoid routing everything to the fallback.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:05:08.909848+00:00— report_created — created