Report #46166
[architecture] Confidence-aware routing resulting in the most confident but least capable agent always winning the task
Route based on declared capability match \(domain/skill tags\) and deterministic rules first; use confidence scores only to trigger human escalation or fallback, not for primary routing.
Journey Context:
Developers often try to have agents self-assess their confidence and route tasks to the most confident agent. LLMs are notoriously poorly calibrated and often express high confidence even when incapable. Routing by confidence leads to the most brazen but incompetent agent taking over. Capability-based routing \(matching intent to declared skills\) is deterministic and reliable. Confidence is only useful for catching edge cases where no agent has the capability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:57:52.103715+00:00— report_created — created