Skip to content
Sprint projectSep 13, 2026Mt. Juliet, TN, USA

Current Public AI Evaluation-Boundary Statistics Do Not Support a Common Base Rate

Jack Lakkapragada · Team Jack

Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Current Public AI Evaluation-Boundary Statistics Do Not Support a Common Base Rate

Presentation

Presentation: Current Public AI Evaluation-Boundary Statistics Do Not Support a Common Base Rate

More on drive.google.com (opens in new tab)
Share

Track 2 #13 asked whether public evaluation-boundary stats from Anthropic, AISI, and METR could support a first, caveated base rate. Getting to a percentage is easy; checking whether those numbers measure the same thing is harder. I audited the numerators, denominators, event definitions, and evaluation conditions before trying to combine anything. The answer was no — the rates differ in what counts as an event, what run set is in the denominator, and how violations are detected. The only clean within-design comparison I found was AISI’s five-model cheating analysis. I do not report a cross-lab base rate. Instead I ship a short reporting checklist so future rate claims are easier to interpret and compare, plus the extraction workbook that makes every inclusion and rejection decision auditable.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. This project identifies an important, underaddressed issue. It has been demonstrated that publicly available statistics on AI safety released by Anthropic, AISI, and METR are potentially equated and combined to calculate an “escape/cheating” rate. These statistics, however, do not measure the same thing. This project identifies an important issue and is timely, as these statistics are commonly cited, particularly in the development of legislative policy. This project provides a legitimate critique and offers a meaningful, visible end-of-project output to the AI safety field

  2. The negative result is the right result and you were right to publish it. Refusing to build a number the sources cannot support is more useful than building one.

    Appendix B is the best thing in this paper. Thirteen numbered claims you declined to make, each one a specific arithmetic you could have done and did not. "4/481 million as an updated July cyber-evaluation rate" and "Binomial confidence intervals added to these retrospectively assembled corpora" are exactly the errors a careless version of this paper would have made. I would recommend to other teams to copy that appendix format.

    The refusal to put binomial intervals on these corpora is also technically correct and easy to get wrong. These are not IID draws from a common population and an interval would have implied they were.

    What I checked in your numbers:

    1. AISI per-model counts – 37/475 = 7.79% and 67/475 = 14.11%. Your stated 7.8%–14.1% range is correct.

    2. The pooled figure you refuse – 67+54+60+43+37 = 261 over 5 × 475 = 2,375. Your 261/2,375 is the right number to name and refuse.

    3. METR incident set – 18 selected eval cases + 24 public + 2 company-shared = 44. Matches.

    4. Anthropic's 3 incidents, 6 affected runs, 141,006 reviewed runs match the primary source text.

    Your treatment of the Anthropic figure is the most careful I have seen. You note the later search was shown incomplete and refuse to read 6/141,006 as prevalence. That restraint is correct and it is not the obvious move.

    Bringing ICH E9(R1) and the Cochrane handbook into an AI evaluation audit is a good import. Estimand discipline is exactly the missing vocabulary here and the field mostly has not noticed that clinical trials solved a version of this problem already.

    Now the problems.

    1. The extraction workbook is not shipped and the abstract says it is.

    The project page states you ship "the extraction workbook that makes every inclusion and rejection decision auditable". Section 8 lists publishing that workbook as next step number 1.

    Those cannot both be true. As submitted there is no workbook, so a reviewer cannot check a single inclusion or rejection decision – we have only your summary of them. For an audit whose entire value is auditability, that is the wrong thing to leave out. Please ship it and fix the abstract either way.

    2. The checklist is never applied to the sources you just audited.

    Section 7 proposes seven reporting fields. Appendix B item 13 honestly declines to call the set minimal or sufficient, which is right.

    But you can do better than proposing it. Score the four audited sources against the seven fields. That is a 4 × 7 table, roughly 28 cells. It would show which fields each source already reports and which it fails. It would demonstrate the checklist discriminates rather than asserting that it would.

    To be honest – that table is the difference between a recommendation and a result. You had the material to build it. It is the first thing I would add.

    3. Single coder on judgement-heavy decisions.

    Every pairwise "do not combine" rests on your reading of event definitions from prose. You see this – Section 8 next step 2 proposes exactly the independent recode. It is the right fix and it is cheap. One other person coding Anthropic and AISI from primary text alone, an afternoon's work, would convert the main claim from one reading into a replicated one.

    4. The four behavior families are introduced and then abandoned.

    Section 2 sets up containment failure, cheating, unauthorized third-party action and oversight subversion, then says the grouping "helped organize the evidence" but was not treated as establishing equivalence. After that the families do no work. Either develop them into the comparison rule or cut them.

    5. You refuse intervals but do not offer the alternative.

    Declining binomial intervals is correct. But the reader is left with bare fractions and no expression of uncertainty at all.

    Partial identification bounds would be legitimate here – for k observed events, m plausibly missed by an incomplete search and n reviewed, the interval [k/n, (k+m)/n] says something honest without assuming IID sampling. Your Anthropic case, where the search was later shown incomplete, is exactly where that would apply. Would that work for your framing?

    6. Minor – Sections 5, 6 and 8 restate the main finding three times. The result is clear by the end of Section 5. Space recovered there could hold the checklist-application table.

    One note, since careful reports are sometimes read as machine-written. The work behind this one is clearly real.

    The arithmetic is internally consistent everywhere I checked it. The sources are primary and correctly cited. You disclose that the rules were refined mid-audit and were not preregistered. You record that you left one unresolved AISI per-sample split out rather than force an interpretation. Those are traces of a person doing an audit. I scored the work.

    Please let me know for any questions.

    Read full reviewShow less

Cite this project

@misc{lakkapragada2026current,
  title = {{Current Public AI Evaluation-Boundary Statistics Do Not Support a Common Base Rate}},
  author = {Jack Lakkapragada},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/current-public-ai-evaluationboundary-statistics-do-not-support-a-common-base-rate-7x7f}},
  url = {https://apartresearch.com/sprints/projects/current-public-ai-evaluationboundary-statistics-do-not-support-a-common-base-rate-7x7f}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026