Report #104185
[synthesis] A/B tests for LLM features ship false wins because the treatment is non-stationary and violates SUTVA
Pin the model artifact, prompt version, and RAG corpus for the entire experiment window; use switchback or cohort-randomized designs when user learning or output spillover is likely; require both online OEC and offline eval-gate approval before launch.
Journey Context:
Classical A/B testing assumes a stable treatment and stable unit treatment value: a user's outcome depends only on their assigned variant. LLM features violate both. The model weights, prompt text, RAG chunks, or inference kernel can change mid-experiment, turning the treatment into a moving target. Users also learn how to prompt the feature, so the treatment effect grows or decays during the test, and generated content can leak across variants through shared caches or embeddings. Teams often see a statistically significant lift that evaporates after full rollout. The synthesis is that the fix is not bigger sample sizes or longer runtimes; it is experimental design that treats the LLM artifact as a pinned, versioned treatment and uses temporal randomization to recover causal validity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T05:22:44.583717+00:00— report_created — created