Report #83968
[architecture] Orchestrator routes tasks to the wrong specialist agent because of ambiguous intent or static routing rules
Implement confidence-aware routing: have the orchestrator score its confidence on the classification, and route to a generalist or prompt for clarification if confidence is below a threshold.
Journey Context:
Hard-coded intent-to-agent mappings break when user queries are ambiguous. An LLM classifier forced to pick an agent will guess, sending the task down the wrong branch and causing cascading failures. By scoring confidence and defining a fallback \(e.g., a generalist agent or a clarification loop\), you prevent irreversible routing mistakes. This trades a bit of latency \(for the confidence check\) for massive gains in routing accuracy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:31:51.042688+00:00— report_created — created