Frontier ai safety frameworks often hide changes in commitments
Silent Revision: Measuring Undisclosed Change in the Safety Frameworks of Frontier AI Developers
Computers and SocietyArtificial IntelligenceSoftware Engineering
Summary
Many AI companies publish safety promises to show how they keep their models safe. The authors found that these companies often make important changes to those promises but don’t clearly say what changed or why. Most hidden changes tend to weaken safety commitments. The authors say rules should require companies to clearly list every change, making it easier for people to check if AI safety is really improving.
What this means in practice
- •For ai policy makers: Introduce rules requiring AI developers to publish detailed lists of changes in safety frameworks to improve transparency and accountability.
- •For ai governance teams: Track and audit changes in AI safety commitments to detect weakening promises and inform risk management.
Authors
Louis Yiven Zhu
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.