Skip to content

Silent Revision: Measuring Undisclosed Change in the Safety Frameworks of Frontier AI Developers

Sep 2026 · 0 citations · 52 references
Computer Science

TL;DR

The silent revision rate, the share of material changes to a framework's commitments that the developer's published account does not identify, is introduced, and the versioned, hash-pinned corpus needed to compute it is released.

Abstract

Frontier AI developers publish safety frameworks that commit them to evidencing whether their models are dangerous. The European Union and California now treat these documents as instruments of accountability, and both already impose duties on their revision. Neither requires the revision to be legible, in the sense that a reader could learn from the developer's own account what changed. We introduce the silent revision rate, the share of material changes to a framework's commitments that the developer's published account does not identify, and we release the versioned, hash-pinned corpus needed to compute it. The corpus contains every public version of the safety frameworks of the twelve developers that have published one, together with each provider's changelog, redline or announcement. We trace 710 commitment instances across twelve consecutive version pairs, code them against a frozen codebook, and adjudicate 244 individually. Three findings follow. First, 67% of material changes (95% CI 62 to 72) are silent under a strict standard and 53% under a lenient one, falling to 49% at section granularity. Second, silence appears to track the form of the account, since narrative announcements run at 74% against 63% for itemised changelogs, whereas account length in words barely matters; on the test that respects nesting the difference is suggestive. Third, 77% of traced changes weaken or remove a commitment, and in seven of eight pairs weakenings are more often silent than strengthenings. The statutory remedy therefore exists and specifies the wrong artefact. A justification explains why a framework changed, an enumeration states what changed, and only the latter makes revision auditable. We argue that publication duties should carry an enumeration duty, which one provider already meets, voluntarily and incompletely.

View source

Similar papers

Preprint Sep 2026

VulContextBench: A Benchmark for Security Context Retrieval in Coding Agents

Vulnerability-detection benchmarks score the verdict an agent reaches, not the evidence it gathered. A model that recalls a CVE from pretraining therefore scores the same as one that traced the data flow. We study a task where this difference matters, deciding whether a commit introduces a vulnerability. Instead of sco...

Yi-Kun Li, Jin-Feng Jiang, Yuheng Yieh et al. · 0 citations
#artificial intelligence Review Sep 2026

It Is Not My Code Anymore

This research note examines distinctions and evaluation questions for AI-assisted software production through a hypothetical enrollment failure and a selective reading of the literature, and considers how quality engineering can evaluate both generated implementations and the processes that produce them.

Augusto Camargo · 0 citations
Preprint Aug 2026

What Proves You Wrong: Benchmarking Language Models on Falsifiable Research Ideation

The Lit2Test benchmark centers on a six-field contract organized around a falsifying outcome, so that every proposal precommits the observation that would prove it wrong, making its quality decidable in the first place rather than merely arguable.

Zi-Yue Wang, Aomufei Yuan, Yi-Ran Yao et al. · 2 citations
Conference Open access Sep 2026

Disclosure Failure in Compromised AI Coding Agents

Preliminary evidence is found that a single sentence added to the developer's own prompt substantially improves disclosure, and a benchmark scored on attack success alone cannot rank agents on the risk a developer actually carries.

Aaron Su, Rong-Xing Lu · 0 citations
#artificial intelligence Preprint Aug 2026

Commit-first LLM judging inherits the judge's own errors

commit-first judging does not remove the anchor that gets gamed, it moves it from the candidate to the judge's own answer, so evaluation is only as good as the judge is at the task, so evaluation is only as good as the judge is at the task.

Idil Gozel · 1 citation

Related blog posts

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.