poisson-proveprove-runs

Condition task_id refund · tool_fail_rate 0.55

comparison
mock-agent@v0 2026-10-14 a → mock-agent@v0 2026-10-14 b 055a6cb1953b
before
mock-agent@v0 2026-10-14 a
after
mock-agent@v0 2026-10-14 b
hash
7b806df50938571e

violated (kind not given)

lowerviolated fell from 0.840 to 0.290 (-0.550) (the paired test (McNemar), q 3.3e-16)

before
0.840 [0.756, 0.899] 95% wilson interval; 84 of 100 episodes · list them (mock-agent@v0 2026-10-14 a, 20261014T035339Z-1add)
after
0.290 [0.210, 0.385] 95% wilson interval; 29 of 100 episodes · list them (mock-agent@v0 2026-10-14 b, 20261014T035345Z-8381)
change
-0.550 [-0.658, -0.437], 97.778% Tango interval
test
the paired test (McNemar): 0 pairs had the event only after, 55 only before; statistic 55; p 5.6e-17, q 3.3e-16, Holm 8.9e-16
rise
0.148
fall
0.253
limits
computed by the paired test at level 0.003 over 18 tests, power 0.8 (4 times in 5), from the observed baseline; the smallest possible p here is 1.6e-30, so this condition can be flagged (yes)
incidence of violated, each run · open
Cumulative incidence of violated, each run: task_id refund · tool_fail_rate 0.55The share of each run's episodes in task_id refund · tool_fail_rate 0.55 that had ended in violated by each time, before in grey and after in violet, to the horizon (20 tool_calls).0.0000.2000.4000.6000.8001.00005101520horizon 20before: 0.840 at the horizon (84 of 100)after: 0.290 at the horizon (29 of 100)before 0.840after 0.290t (tool_calls)

timeout (kind not given)

highertimeout rose from 0.160 to 0.470 (+0.310) (the paired test (McNemar), q 4.2e-06)

before
0.160 [0.101, 0.244] 95% wilson interval; 16 of 100 episodes · list them (mock-agent@v0 2026-10-14 a, 20261014T035339Z-1add)
after
0.470 [0.375, 0.567] 95% wilson interval; 47 of 100 episodes · list them (mock-agent@v0 2026-10-14 b, 20261014T035345Z-8381)
change
+0.310 [+0.173, +0.440], 97.778% Tango interval
test
the paired test (McNemar): 37 pairs had the event only after, 6 only before; statistic -31; p 1.6e-06, q 4.2e-06, Holm 2.0e-05
rise
0.253
fall
0.148
limits
computed by the paired test at level 0.003 over 18 tests, power 0.8 (4 times in 5), from the observed baseline; the smallest possible p here is 1.6e-30, so this condition can be flagged (yes)
incidence of timeout, each run · open
Cumulative incidence of timeout, each run: task_id refund · tool_fail_rate 0.55The share of each run's episodes in task_id refund · tool_fail_rate 0.55 that had ended in timeout by each time, before in grey and after in violet, to the horizon (20 tool_calls).0.0000.1000.2000.3000.4000.50005101520horizon 20before: 0.160 at the horizon (16 of 100)after: 0.470 at the horizon (47 of 100)before 0.160after 0.470t (tool_calls)

How to read this page