Papers for

software reliability teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Certifying when machine learning predictions are reliable and detailed

Available Guardrails: Certifying Selective Prediction across ML Systems

Abstract: A selective predictor acts as a safety gate: it returns an output only when the prediction appears sufficiently trustworthy. Deployments increasingly require this reliability to be certified at a target precision for every reporting unit of interest, such as a tool, policy label, or patient subgroup. The main difficulty is often not whether a granted certificate is valid, but whether finite calibration data can produce one at all. As the gate becomes safer or more fine-grained, some units may receive too little evidence to certify. We make this notion of availability computable through classical exact-binomial inversion and formulate reporting-partition selection, under a fixed group order, as a dynamic program that exposes the trade-off among safety, granularity, and served traffic. The resulting frontier reveals a large population opportunity that finite-sample estimation nearly erases: a truth-informed planner gains $0.157$ mean coverage over support balancing, whereas a naive estimator recovers only $0.005$, making recovery from finite data the central challenge. Constructing candidate partitions on one planning split and selecting among them on another recovers part of this gap, improving mean coverage over support balancing by $0.060$, with the direction reproduced in $59$ of $60$ model effects across three intent-routing datasets and two architectures. A complementary validity-preserving lever, reallocating the familywise error budget across reporting units, recovers additional coverage both with population quantities and noisy estimates. The same frontier recurs, with predictor-specific ceilings, across LLM tool-calling, content moderation, lesion classification, and recommendation. Certified availability is therefore a plannable deployment resource that determines when a safety gate can be certified, at what granularity, and over how much traffic.

Fri 18 SeptMachine Learning
The gist
Machine learning systems often need to decide when to share predictions they can trust and when to hold back. The authors focus on figuring out when these "safety gates" can confidently say a prediction is safe, especially for different groups or categories within data. They developed a method to measure and plan this reliability, balancing how safe the predictions are with how many predictions they make and how specific those predictions are. Their results show that careful planning using their approach improves the amount of trustworthy predictions systems can safely make, validated across diverse applications like content moderation and medical diagnosis.
Open 2609.22048v1

Efficient evaluation methods improve testing of evolving AI agents

Efficient Benchmarking in Production: A Study of an Evolving LLM Agent

Abstract: Production LLM agents are evaluated repeatedly as they evolve, but full agent benchmarks are costly to rerun. We study efficient recurring evaluation for a production analytics agent serving tens of thousands of monthly active users and report first-hand deployment experience. Using 574 historical runs of the production benchmark, split chronologically into calibration and held-out periods, we compare random sampling, historical caching, fixed representative subsets, and IRT-based adaptive testing. The results show that multidimensional 2PL adaptive testing achieves the best overall score fidelity: executing 200 questions, 38.5% of a full run, yields 1.03 pp of MAE. We nevertheless deployed difficulty-stratified fixed subsets because of their operational simplicity, and show they transfer without recalibration to five other agent families and remain stable across calibration windows as short as one day. Drawing on this deployment experience, we report practical recommendations for recurring production-agent evaluation.

Fri 18 SeptArtificial IntelligenceSoftware Engineering
The gist
Testing AI agents frequently is important but can be very expensive and time-consuming. The authors studied different ways to make repeated testing of a large AI agent more efficient using past test results. They found that a smart adaptive testing method worked best but chose a simpler fixed subset of questions for day-to-day use because it was easier to manage. This fixed method also worked well for other similar AI agents without needing changes. The paper shares advice from real-world experience on how to test AI agents in production regularly.
Open 2609.21267v1

Large language models create diverse fault tolerant system code

DiverseFT: Diversifying Fault-Tolerant Systems using LLMs

Abstract: Fault-tolerant agreement protocols fail if replicas share a common flaw that simultaneously affects more replicas than the tolerable threshold. Therefore replicas should ideally fail independently, which can be achieved through diversification. However, in practice, often the same protocol implementation is shared by all replicas which is not surprising given that the provision of multiple diverse implementations is difficult and highly laborious. This poses a major risk, as a shared protocol implementation is a prime candidate for common bugs due to its complexity. With DiverseFT, we demonstrate how, given a reference implementation, Large Language Models (LLMs) can be utilised for the automated and scalable generation of code that compiles, passes tests, and crucially differs semantically/binary-wise, that can re- place code in the reference implementation, thereby significantly reducing diversification costs. We demonstrate the feasibility of diversification of replication protocol implementations using LLMs by diversifying three implementations: PBFT, HotStuff, and Raft, showing how up to 65% of the codebase can be diversified.

Wed 16 SeptDistributed, Parallel, and Cluster Computing
The gist
Fault-tolerant systems need many copies (replicas) of software that don't fail in the same way at the same time. Usually, all copies run identical software, which risks all failing together if there's a common bug. The authors show that large language models can automatically generate different versions of the same system code that still work correctly but differ enough to avoid shared bugs. They tested this on common protocols and managed to change up to 65% of the code, which could make systems safer and more reliable.
Open 2609.18512v1

Continual search improves AI failure diagnosis in long tasks

Root-Cause Attribution Is a Search Problem: Continual Search for Long-Horizon Agent Failures

Abstract: The increasing deployment of AI agents in long-horizon tasks yields massive execution logs. Diagnosing failures within these records is crucial for reliability, as it transforms outcome-level signals into actionable interventions. The sheer scale of the data renders human review impractical, driving the need for automated root-cause attribution (RCA). However, automated RCA methods using LLMs suffer from low diagnostic accuracy, especially as execution traces grow larger. They struggle because relevant information is often sparse, distributed across distant actions, and disconnected from the visible failure, reducing root-cause attribution to a massive search problem. Existing RCA methods typically rely on one-shot LLM judgments to diagnose failures from execution traces. While effective for shorter trajectories, these judges tend to settle on a plausible diagnosis early, leaving critical evidence in longer traces unexamined. We introduce Continual Search, an iterative framework that nudges the judge, over successive turns, to keep searching for unresolved diagnostic evidence. We evaluate Continual Search across four existing RCA benchmarks. Recognizing the lack of massive execution traces in current benchmarks, we introduce MegaRCA-Mix to evaluate RCA at scale. MegaRCA-Mix provides a challenging testbed of 50 human-annotated failure trials spanning long-horizon, execution-heavy tasks. Across multiple benchmark suites and model families, Continual Search consistently improves attribution performance. On MegaRCA-Mix, for example, it improves GPT-5.5's F1 score by more than 40\%, from $0.349$ to $0.498$. More interestingly, within the same model family, lower-tier models can even surpass their higher-tier counterparts, demonstrating that effective search supersedes raw model scale.

Fri 11 SeptArtificial IntelligenceHuman-Computer InteractionMachine Learning
The gist
When AI systems work on long and complex tasks, they generate huge records of their actions, making it hard to figure out why they fail. The authors found that current methods using large language models (LLMs) have trouble pinpointing the true causes because the clues are hidden across many steps. They created a new approach called Continual Search that repeatedly prompts the AI to keep looking for important evidence instead of stopping too soon. This method significantly boosts the accuracy of diagnosing failures, even helping smaller models outperform larger ones when guided properly.
Open 2609.13463v1