Report #104045
[architecture] An agent confidently returns a wrong answer because no confidence threshold triggers escalation
Require every agent to emit a calibrated confidence score alongside its output, plus a structured uncertainty rationale. Route outputs below a tunable threshold to a more capable model, a verifier agent, or a human. Never let a low-confidence output proceed without an explicit override.
Journey Context:
Teams often rely on the LLM to say 'I am not sure' in free text, which is unreliable and hard to act on. A separate numeric confidence field, computed from token probabilities, self-consistency across multiple samples, or an explicit verifier model, gives the orchestrator a deterministic trigger. The threshold should be per-task: creative drafting can tolerate low confidence, but code generation, financial calculations, or safety-critical decisions need high confidence. Calibration matters more than the absolute scale; an uncalibrated score is just decoration. The cost is inference overhead and some false escalations, but it is the cheapest way to prevent silent high-stakes errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T05:08:36.791400+00:00— report_created — created