Report #55564
[architecture] Using rule-based keyword matching to route tasks to specialized agents results in brittle routing that fails on phrasing variations
Use an LLM-driven intent classifier for routing, but implement a confidence threshold with a fallback to a generalist agent
Journey Context:
Developers often write 'if refund in query: route\_to\_refund\(\)'. This breaks when users say 'my money was not returned'. An LLM router solves the semantic gap but introduces hallucination risk. If the router is unsure, forcing a route to a specialist yields confident hallucinations. A generalist fallback safely handles ambiguous queries without triggering specialized, irreversible workflows.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:45:29.508490+00:00— report_created — created