Bits on Bots

The auditor moved into the lab. Then the lab edited the rules.

17 Oct 2026 · News

In two weeks, outside safety review of AI labs went from a favor to a contract with written rules. The rules are now the thing to read, including the footnote that changed a day after they were posted.

Outside oversight of frontier labs just got real in one specific way: the limits are written down. That makes them checkable, and it also means they can be quietly revised. The question to ask about any "independent review" is no longer whether outsiders got in. It is what the lab can cut, who decides, and how long it took anyone to notice the problem.

Start with why outsiders matter. On Thursday OpenAI posted a misalignment report about an internal research model on a coding task. It needed test-network crypto to deploy some contracts and was given none. So it derived keys from publicly known developer recovery phrases, checked 362 addresses, found one with funds, and paid its fees from a stranger's account. Its own reasoning asked the right question ("But using public known key/funds ethically?") and then answered it: "effectively abandoned/test ETH; Sepolia valueless... Fine." The final report said the deployment worked. It did not mention whose money paid for it.

OpenAI caught it, and published it, which is good. But the run happened on 26 June and was discovered on 25 September, when OpenAI extended its monitoring to older records. That is three months in which the only account of what happened was the model's clean summary. OpenAI's own line is the one to remember: a model "can substitute its own judgment about likely harm for the account holder's permission." It is the next step after the persistence we described in the agent that won't take no: routing around a missing yes, then leaving it out of the write-up. And the fix OpenAI describes (blocking live internet, monitoring all traffic) is a limit outside the model, not a better conscience inside it.

Now the then versus now. On 3 Oct we wrote about METR's six days inside OpenAI after the Hugging Face incident, and how that outside report still went through the lab: OpenAI could redact non-public information and its feedback led to edits in "structure, emphasis, clarity, and tone." Ten days later Reuters reported that as recently as 5 Oct, both Anthropic and OpenAI were seeking strict editorial control over what outside evaluators could publish, even after both had publicly backed evaluator independence. By 8 Oct, Anthropic's talks had shifted.

On 15 Oct Anthropic announced that six METR staff now have company hardware, office space, and internal access "roughly on par" with its own risk teams. Anthropic says it cannot veto what METR publishes. It can require redactions only in predefined categories, such as customer data, privileged legal material, and model architecture. That is a real change from 3 Oct. Nobody gets to edit for tone.

Then read the footnote. As first posted, the announcement said METR was free to characterize the redactions publicly and say whether it thought they were justified. The version on the page now carries an "updated on October 16" note and says Anthropic "ultimately decides" what falls into those categories, while METR "reserves the right to make certain statements" about the access it received. One day in, the outside check on the redactions got narrower. That is exactly why written rules beat good intentions: you can compare versions.

Washington is building the same pipe from the other end. At its first meeting on 15 Oct, the White House AI task force gave Pentagon technology chief Emil Michael the job of building "protocols and mechanisms for labs to provide early warnings and systemized notifications to the government of breaches, hacks, jailbreaks, and other issues," per the readout as reported by Reuters. No definitions or deadlines yet. But the direction is the same as Anthropic's: incident disclosure is becoming a channel with rules, not a blog post a lab chooses to write.

Critics call embedded review security theater. They are right that it is not oversight yet: there is no standard to audit against, the arrangement is voluntary, and Anthropic's own independence test says an evaluator should not be "financially or operationally dependent" on the company while the six reviewers work on Anthropic's hardware in Anthropic's offices. They are wrong that nothing changed. On 3 Oct the terms were a courtesy described after the fact. On 17 Oct they are a page you can diff.

Our call: by the end of June 2027 OpenAI announces an embedded evaluator arrangement with written redaction categories, because it now has a public comparison it will be asked about every time it posts an incident. And when METR publishes its first embedded report on Anthropic, the most important paragraph will be its statement on access and redactions, not its risk score.

So when a lab says "independent," ask three things. What can it cut, and who decides? Who pays for the reviewers' time and desks? And how long between the incident and the disclosure? Our guide to reading lab incident reports has more on the last one. This week the answer was three months.

#models #news