Report #5065
[architecture] Orchestrator agents blindly routing tasks to sub-agents based on keyword matching, leading to cascading failures when the sub-agent lacks capability
Implement confidence-aware routing where the orchestrator evaluates the sub-agent's predicted probability of success or requires the sub-agent to explicitly reject tasks outside its scope.
Journey Context:
Static routing assumes the orchestrator perfectly understands the sub-agent's capabilities, which degrades as tools are added. If an agent attempts a task it isn't trained for, it hallucinates. By requiring a confidence check or an explicit reject capability, the orchestrator can fallback or re-plan. The tradeoff is an extra LLM call for validation, but it saves expensive execution rollbacks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T20:36:35.814519+00:00— report_created — created