A retrieval-augmented question-answering system can change its answers on the same questions when the retrieval corpus is expanded, even though the model identifier, prompt, retrieval policy, evidence depth, rendering, and generation controls are held fixed. The authors call this 'accuracy-blind answer churn' because aggregate accuracy can stay flat or even improve while the answer distribution shifts underneath it. To measure it, they propose a Snapshot Compatibility Audit that subtracts same-snapshot repeat disagreement from cross-snapshot disagreement, isolating churn attributable to the corpus update from ordinary generation variability.1
Context
The constraint this moves is in how RAG releases are evaluated. Standard practice treats exact-match or semantic accuracy as the release gate; the paper shows that two snapshots can be indistinguishable on aggregate accuracy yet incompatible at the answer level, with 40/400 repeat-stable semantic flips on Natural Questions. The requirement shifts from 'utility must not decrease' to 'answer compatibility must be audited, and if churn is excess, the update must be justified by utility gains.'1
Assessment
The evidence is methodologically careful: both main studies are preregistered; the replication is outcome-blind and uses a different generator and serving configuration. Effect sizes are consistent across benchmarks—semantic excess churn of 10.25 pp and 8.75 pp—while exact-match accuracy moves in opposite directions (-1.5 and +3.0 pp). The main unaddressed limitation is that the audit was applied to one index expansion protocol (FineWeb prefix 1-to-7 shards) and two datasets, so external validity across corpus types and model families remains open.1
Caveats
AI hypothesisThis analysis would change if independent replications on broader tasks found that the same-snapshot baseline overcorrects or undercorrects for generation variability, or if answer-level churn could be shown to be utility-irrelevant because the changed answers are semantically equivalent under the task's intended scoring. Also, the current evidence does not establish a cost threshold; a deployment could accept compatibility failure if utility gains are large and explicit. Without such a trade-off framework, the paper's recommendation to audit compatibility alongside utility is a safe but incomplete release policy.1


