Evaluation and debugging
One safe rollout does not prove the absence of a rare destructive action
A preprint formalizes the one-shot audit problem. The same agent task sometimes
completes safely and sometimes causes harm; one successful demonstration does
not measure the tail of the distribution. The authors propose separating
task-level failure probability from severity and running sequential trials with
a predefined detection budget.
The abstract gives no universal number of repetitions—none exists. It depends
on tolerable risk, a non-stationary backend, and execution cost.
The methodological conclusion is direct. pass@1 asks whether an agent can pass
once. Safety asks how often harm occurs and how severe it is. A rare catastrophic
action does not become acceptable because the average session looks clean.
Source: one-shot agent audits.
In a long trajectory, the hardest task is finding the first step after which failure became inevitable
LongRCA Bench contains 1,140 naturally failed trajectories across five domains,
with a median length of 145 steps. Humans labeled the responsible role and the
earliest decisive root cause. The strongest baseline found the exact root step
in only 13.2% of cases. Training-free RCTA, using segment summaries and handoff
tracing, reached 51.1% role accuracy and 24.1% exact-step accuracy.
These are different tasks, so their percentages cannot be compared directly.
The dataset selects only failures and may carry selection bias; the results have
not been independently reproduced.
The final error is almost never the cause. In a multi-role run, one agent makes
an early false assumption and the rest rationally continue from corrupted state.
Debugging requires preserving the handoff and finding the first decisive
transition, not the last executor.
Source: LongRCA Bench.