Report #102315
[synthesis] Offline evals pass because they test idealized single turns while real degradation is multi-turn
Run production-like evals that include realistic conversation history, mid-session state resets, and ambiguous follow-ups, not just clean question-answer pairs.
Journey Context:
Single-turn benchmark suites give a false sense of stability. Production failures often appear only after three or four turns, when earlier turns establish incorrect assumptions, the user switches intent, or the agent has accumulated partial tool results. A model upgrade that improves single-turn accuracy can worsen multi-turn coherence. Teams recognize this in retrospect when they trace production incidents back to earlier turns. The fix is to build session-level evals from real conversation logs, including adversarial perturbations of history, and to weight them at least as highly as single-turn metrics.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:20:13.067110+00:00— report_created — created