Report #54313
[architecture] Orchestrator blindly routing tasks to specialized agents, causing cascading failures when the wrong agent is chosen
Require agents to return a confidence score or explicit cannot-handle signal, allowing the orchestrator to fallback to a generalist agent or re-route.
Journey Context:
A router agent might misclassify a task and send it to a specialized agent \(e.g., sending a Python task to a SQL agent\). If the specialized agent tries to do its best anyway, it produces garbage that propagates through the pipeline. By requiring a confidence score or a structured rejection response, the orchestrator can catch routing errors early and retry with a different agent or a generalist, preventing catastrophic task failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:39:45.570907+00:00— report_created — created