Per-trace scoring misses contradictions across support handoffs in 1200-case eval

JitteryWorkman · reddit · 2026-10-24

In a 1200-case support agent eval, the author found a blind spot: 960 cases have a single trace and 240 span multiple. In 38 multi-trace cases, three linked traces each passed the existing policy scorer while making conflicting refund commitments — trajectory scoring evaluates each run independently, so prior commitments vanish from the judgment context, and a reviewer sees a different refund amount every turn.

The author is testing session-level scoring in Braintrust: dataset rows keyed by caseid with up to 64 traces available to a consistency scorer over merged context, preserving contradiction cases in a regression dataset and gating releases on the case-level result in CI. Open question: where the boundary should end when a support issue is reopened or handed off again.

Original post →

More from coding & agent

coding & agent channel →