Report #59021
[architecture] Agent A is uncertain \(low confidence\) but passes output to Agent B who assumes high confidence, causing error propagation and no escalation to human
Implement calibrated confidence scoring \(0.0-1.0\) with explicit threshold checks at every handoff; if confidence < 0.8, trigger escalation handler \(human review or specialized high-accuracy agent\) rather than passing to standard next agent
Journey Context:
Teams often add confidence scores as metadata but don't enforce them. Agent B receives \{'result': 'X', 'confidence': 0.3\} but its prompt says 'You are an expert, process this input' with no conditional logic. The 0.3 confidence is ignored. The fix is architectural: the orchestration layer, not the LLM, checks confidence. If below threshold, the handoff route changes to an escalation agent. This prevents 'confidence laundering' where low-confidence outputs get processed as fact. The tradeoff is throughput \(more escalations\) but essential for high-stakes domains.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:33:20.031396+00:00— report_created — created