Lifetime-valid decisions by continually evolving AI analysts
AI agents that act as statistical analysts evolve through model upgrades, prompt edits, and new tools, but each change risks inflating Type I error. This paper introduces continual validation: before any update is deployed, it is frozen and tested on newly simulated null data using exact binomial confidence bounds with a decaying per-update risk budget. The result is a lifetime guarantee that no invalid version passes, which matters because classical fixed-procedure guarantees break under adaptive, open-ended evolution.
The paper makes a rigorous and practically motivated contribution. Theorem 1 and Corollary 1 cleanly establish that the lifetime probability of ever deploying a version whose Type I error exceeds the validation level $\alpha'$ is at most $\delta$, and that every subsequent study controls error at the target $\alpha = \alpha' + (1-\alpha')\delta$. However, the guarantee is strictly confined to the null scenarios used for validation; as the authors note, "the theoretical guarantee strictly applies to the null scenarios covered by validation. It does not automatically provide a mathematical bound for unobserved data generating patterns."
The strongest parts are the formal characterization of failure modes and the algorithmic fix. Theorem 2 shows that individually valid analyses do not compose, Proposition 3 proves a fixed benchmark can be overfitted, and Lemma A2 shows that fixed-level repeated validation accumulates risk. Against these, continual validation uses an exact Clopper-Pearson bound with a decaying per-update risk budget $\delta_r = 6(\delta - \delta_0)/(\pi^2 r^2)$, ensuring the familywise error over an infinite horizon stays below $\delta$. The paired bound is especially elegant: "The paired bound compares the version with the reference analysis on the same simulated studies. It therefore needs to resolve only how often the version adds a rejection that the reference analysis would not make."
First, the empirical demonstration uses simplified agent configurations. Example 1 is described as "an early, simplified configuration of this broader agent," which limits confidence in how the method scales to fully open-ended LLM reasoning where allowed paths may be hard to enumerate. Second, while the authors acknowledge the gap, the guarantee does not cover off-grid scenarios: "the theoretical guarantee strictly applies to the null scenarios covered by validation. It does not automatically provide a mathematical bound for unobserved data generating patterns." The reported robustness on 666 of 690 off-grid scenarios is empirical, not proven. Third, computational cost is partially addressed but not fully quantified in the main text; the appendix notes that validation from scratch can require nearly 800,000 simulated studies per scenario for tight margins. Finally, the improvement-test baseline is allowed to reach a 0.817 Type I error rate in Example 2, which is a useful cautionary tale but arguably a strawman if interpreted as a competing safe method rather than an ablation showing why power-only checks fail.
The evidence generally supports the claims. The comparisons to related work are fair and accurately characterized. The authors correctly distinguish their goal from Sengupta (anytime-valid certificates for self-improvement) and from their own prior Reuse framework, noting that neither targets Type I error control for hypothesis testing. The Sun et al. Reuse abstract confirms it certifies "every promoted modification is a genuine population improvement on the underlying task distribution," which is a performance guarantee, not a Type I error bound. The static-benchmark failure in Example 1 and its success in Example 2 neatly illustrate that a fixed benchmark is only as good as its scenario coverage, and the criticism of Learn then Test for requiring a prespecified finite menu is accurate.
Reproduction would be difficult. Although the authors specify parameters such as $\alpha = 0.05$, $\delta = 0.005$, and $\alpha' = 0.0452$, and provide pseudocode in Algorithm 1, they do not report a public code repository, random seeds, complete prompt templates, or model snapshots. The validator must "run each version on simulated studies, either through its allowed paths or in full," and "each study is decided by one binding run, because rerunning a stochastic version until it rejects is a different procedure," but implementing this requires access to the exact bioequivalence agent and GrowthBook integration described only at high level. The reliance on specific models without pinned snapshots further complicates independent validation.
AI agents increasingly act as analysts whose decision can often be cast as hypothesis tests. Classical tests control the Type I error rate, the probability of rejecting a true null hypothesis, for fixed procedures. However, AI analysts introduce internal randomness and can evolve continuously over time. As AI analysts evolve, the risk of approving versions with Type I error rates above the target can accumulate, and adaptive use of evaluation feedback can lead to overfitting. We introduce continual validation, which evaluates each proposed AI analyst version before deployment using simulated data under the null hypothesis, with scenarios that can be randomized and expanded over time. We prove that, regardless of how updates are chosen or how many are proposed, the lifetime probability of ever deploying a version whose Type I error rate exceeds the allowed level remains bounded. This guarantees that every subsequent decision controls the Type I error rate at the target level across these scenarios. At the same time, updates with sufficiently low Type I error rates pass validation with high probability, allowing the analyst to continuously improve its performance without sacrificing rigor. In two examples involving evolving AI analysts for bioequivalence studies and product A/B tests, Type I error rates reached 0.098 and 0.183 without continual validation, compared with at most 0.045 and 0.044 with it, while retaining 82% and 96% of the power from optimally selected valid updates.
Pick a starting point or write your own. Challenges run in the background, so you can keep reading while the AI investigates.
No challenges yet. Disagree with the review? Ask the AI to revisit a specific claim.