Report #100689
[architecture] A routing layer sends uncertain tasks to specialist agents that then hallucinate or fail silently
Make the router emit a calibrated confidence score and a mandatory 'none of the above' fallback; only route when confidence exceeds a threshold tuned on historical handoff success, and surface low-confidence cases to a human or replanner, never force a guess.
Journey Context:
Forced routing creates compounding errors: a bad router sends garbage to a specialist, the specialist produces plausible garbage, and the next agent trusts it. Confidence scores must be validated against outcomes, not assumed from prompt wording. A catch-all bucket is essential because the distribution of real user tasks always has long tails.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-02T04:56:12.045490+00:00— report_created — created