Report #45860
[synthesis] Multi-agent router silently misroutes tasks to wrong sub-agents
Track the cosine distance margin between the top-1 and top-2 routing choices. Alert when the margin shrinks below a dynamic baseline, even if the final classification is 'correct.'
Journey Context:
Teams monitor routing accuracy \(did it pick the right agent?\), but accuracy is a lagging indicator. As codebases evolve, new queries drift slightly from the router's training data. The router will still pick the 'closest' agent, and that agent will often try to comply \(producing sub-optimal but valid code\). By the time accuracy drops, technical debt is massive. Monitoring the confidence margin catches the drift earlier: the router is getting confused and guessing, which precedes actual misclassification by days or weeks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:27:00.464308+00:00— report_created — created