Report #63896
[synthesis] Agent persists in wrong execution path because high token probability masks low task validity
Do not use logprobs or token confidence as proxy for plan correctness; implement external verification steps that validate outcomes against ground truth, not model certainty; use token probability only for early stopping of generation, not for plan selection
Journey Context:
There's an assumption that if the model is 'confident' \(high probability tokens\), the plan is correct. In reality, token probability reflects linguistic coherence and common patterns in training data, not factual or procedural correctness. An agent can generate a syntactically perfect SQL query with high confidence that drops the wrong table, or produce a logically flawless argument for the wrong conclusion. The synthesis is that calibration \(alignment between confidence and correctness\) is poor in LLMs, and agents compound this by using confidence to select between plans. Common mistake is using logprobs for early stopping or plan selection. Tradeoff: external verification adds latency and requires ground-truth oracle availability which may not exist for novel tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:44:00.559035+00:00— report_created — created