Report #15620
[architecture] Routing tasks to the wrong specialized agent because the orchestrator doesn't express uncertainty, leading to cascading failures
Implement confidence-aware routing where the orchestrator agent must emit a confidence score, and trigger a fallback to a generalist agent if the score is below a threshold or if the specialist agent fails.
Journey Context:
Routers often force a task into a specialized silo even if the task is ambiguous. If the specialist fails, it might hand back to the router, creating a loop. Hardcoded routing rules are too rigid. LLMs can estimate confidence; using it to trigger a fallback breaks the loop and prevents specialized agents from hallucinating outside their domain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T00:40:27.312851+00:00— report_created — created