Threshold Watch
Every frontier lab publishes a safety framework: the capability thresholds that are supposed to trigger stronger safeguards. None of them publishes a version history. The thresholds differ between labs, change without notice, and changes are how commitments soften. This page does the versioning for them: each framework is fetched on a cadence, normalized, hashed, and archived. When the content changes, the new snapshot lands here, dated, with a diff where the source is text.
As of September 2026, Threshold Watch tracks six frontier labs (Anthropic, OpenAI, Google DeepMind, xAI, Meta, Amazon). All six publish a safety framework. None publishes a changelog a third party can verify, and one framework (Meta's) rejects automated retrieval outright.
This is commitment one of the Control Stack Compact run in reverse: thresholds should be published in a common format and versioned like a changelog by the labs themselves. Until they are, the changelog lives here.
Subscribe to changes: RSS feed (a new item means a framework changed or entered tracking). Related: the Frontier Incident Timeline and the Compact Clauses for procurement.
For reporters: when a lab edits its safety framework, the change lands here first, as a dated snapshot with a hash and a line-level diff against the previous version. Subscribe to the RSS feed above to see edits the day they are captured, and cite the diff, not our summary. Questions or verification requests: hello@majormatters.co.
| Lab | Framework published | Fetchable by tooling | Versioned by the lab | Diffable changelog |
|---|---|---|---|---|
| Anthropic | Yes | Yes | Yes (v3.4) | Announcements only |
| OpenAI | Yes | PDF only; page blocks tooling | Yes (v2) | No |
| Google DeepMind | Yes | Yes | Yes (3.1) | Blog summaries only |
| xAI | Yes | Yes | Dated editions | No |
| Meta | Yes | No; PDF rejects automated retrieval | Yes (v2.0) | No |
| Amazon | Yes | Yes | Unclear | No |
Six labs publish a framework. None publishes a changelog a third party can verify. That last column is what this page exists to fill.
The fix costs a lab an afternoon, so we published it: the Safety Framework Publication Format (v0.1, CC0) is a machine-readable format for safety commitments plus a hash-anchored changelog, with a stdlib validator and an unofficial reference mapping of one real framework. It defines what any threshold, gate, or safeguard should be published as, and deliberately says nothing about what they should be. The scoreboard columns above are its conformance levels: published (L0), fetchable (L1), structured (L2), changelogged (L3). As of September 9, 2026, no tracked lab is past L1.
Responsible Scaling Policy
| snapshot | sha256 | bytes | files |
|---|---|---|---|
| 2026-09-21 | 4384a9234160f7a8… | 23,469 | raw · diff |
| 2026-09-09 | 8e136c441a49cbee… | 23,478 | raw · diff |
| 2026-09-08 (first) | 860f164836fea18c… | 24,960 | raw |
Preparedness Framework
| snapshot | sha256 | bytes | files |
|---|---|---|---|
| 2026-09-08 (first) | fae6e4cc6f7212a0… | 170,399 | raw |
Frontier Safety Framework
| snapshot | sha256 | bytes | files |
|---|---|---|---|
| 2026-09-08 (first) | ad10d2d240e0d557… | 447,155 | raw |
Frontier AI Framework
| snapshot | sha256 | bytes | files |
|---|---|---|---|
| 2026-09-08 (first) | 2c3c6313bd2fb6ee… | 203,142 | raw |
Advanced AI Scaling Framework
| snapshot | sha256 | bytes | files |
|---|
Frontier Model Safety Framework
| snapshot | sha256 | bytes | files |
|---|---|---|---|
| 2026-09-21 | a15d9539661774c8… | 2,103 | raw · diff |
| 2026-09-09 | ea8786711a50108d… | 2,086 | raw · diff |
| 2026-09-08 (first) | 513f9ba04df1f865… | 30,392 | raw |
Read-only fetches of each lab's canonical public document. HTML sources are reduced to visible page text before hashing so cosmetic markup changes don't register as framework changes; PDFs are hashed byte-for-byte. A snapshot is kept only when the hash changes. Fetch failures are shown as-is rather than papered over. Source code ships in the major-labs repository (threshold-watch/fetch.py).