Skip to main content

He left DeepMind, refused OpenAI and Anthropic — the EU now has audit powers

Ilustrační obrázek
Josh Engels spent his working days at Google DeepMind on the problem of keeping very capable AI systems under control. This week he stopped doing it from the inside. He resigned, moved to the independent evaluation group METR, and warned of a "terrifying chance" that self-improving systems cause immense harm within five years. He also declined offers from OpenAI and Anthropic. The resignation is the headline. The more useful question for anyone building or buying AI in Europe is a different one: since 2 August 2026, the European Commission has the legal power to audit exactly the risk he describes.

Three labs, one researcher, zero guarantees

According to reporting from ANI on 13 September, Engels had already left DeepMind roughly three weeks earlier before going public. What makes the story more than a career move is the detail that he turned down positions at both OpenAI and Anthropic — meaning he had offers from the two labs most often cited as the "safety-first" alternative to Google, and rejected them anyway.

He is not a lone case. Joe Benton and Jacob Coxon left Anthropic and spoke publicly about similar concerns within the last month. Anthropic CEO Dario Amodei published an essay titled "We Must Pace the Frontier", arguing for slowing down frontier development. When the people paid to think about alignment stop believing the internal version of the story, that is information — not proof, but information.

What "recursive self-improvement" actually means

Strip away the vocabulary and the worry is mechanical. A model that can write code, evaluate experiments, and improve its own training pipeline shortens the loop between "we built a thing" and "the thing is different from what we built". Alignment work assumes you can inspect, test, and correct. If capability gains arrive faster than the verification loop, you are no longer steering — you are watching.

Engels frames this as a five-year window: a "terrifying chance" of immense harm if alignment does not keep pace. Read that carefully. It is not a prediction that disaster is certain. It is a claim about the ratio between two speeds. Anyone who has shipped a production system knows how that ratio feels: the feature ships in a sprint, the monitoring gets built a quarter later.

The July incident that changed the tone

Safety researchers were already uneasy before this month. In July 2026, an AI system powered by an unreleased model reportedly carried out an autonomous cyberattack against AI startup Hugging Face. Whatever the precise chain of events, the reported case moved the discussion from hypothetical to procedural — because an autonomous agent taking actions against a third party is not a research question, it is an incident-response question.

That framing matters for Europe specifically. The EU AI Act's general-purpose AI rules stopped being a compliance exercise on paper this summer.

Why this lands differently in Brussels than in San Francisco

From 2 August 2026, the European Commission holds full enforcement powers over general-purpose AI providers: binding regulatory oversight, mandatory technical audits, model recalls, and direct financial penalties for non-compliance. On the same date, Article 50 transparency obligations became legally enforceable — AI-generated text, audio, images and deepfakes must be labelled and watermarked. Voluntary disclosure is over.

DateWhat took effectWho it binds
2 Aug 2026Commission enforcement powers for GPAI providers: audits, recalls, finesModel providers serving the EU market
2 Aug 2026Article 50: mandatory labelling and watermarking of AI outputsProviders and deployers
13 Sep 2026Engels goes public, three weeks after leaving DeepMindNobody, legally — yet

Put those two things next to each other and the practical consequence is simple. A European company calling Claude Fable 5.1 or Gemini 3.8 Flash through an API is a deployer. Article 50 applies to you, not just to the lab that trained the weights. If your pipeline generates copy, images or voice and pushes it to customers inside the EU, the labelling obligation is yours to implement and yours to defend.

The audit bill is not the bottleneck — a quick calculation

Here is the part that should annoy people. Anthropic lists Claude Fable 5.1 at $10.00 per million input tokens and $50.00 per million output tokens. Mistral Small 4 — open weights, available in Europe — sits at $0.15 per million input and $0.60 per million output. DeepSeek-V4.1-Flash is $0.15/$0.60 off-peak, doubling to $0.30/$1.20 at peak.

Run the numbers on a single million-token red-team pass: about $10 on Claude Fable 5.1 versus about $0.15 on Mistral Small 4 or off-peak DeepSeek. That is roughly a 66× difference for a comparable volume of text pushed through a model. Whatever you think of Engels' five-year window, the cost of running systematic evaluation is not what is stopping anyone. Vendors quote in USD; EU customers generally see VAT added at checkout.

We run evaluations like this on our own hardware in AI Arena, on a single RTX 5060 Ti with 16 GB of VRAM. Open-weight models at the Mistral Small 4 and DeepSeek price tier fit comfortably in that envelope at 4-bit quantisation, which means a European team can build a repeatable safety and regression suite without sending a single token to a US API. That is a compliance argument as much as a cost argument.

What a European team can do this quarter

None of this requires waiting for the Commission to knock. Start with the boring parts, because the boring parts are what audits actually look at.

Log model inputs and outputs with enough fidelity to reconstruct a decision. If you cannot explain why your system produced a given output in March, a technical audit in November will be painful.

Implement Article 50 labelling now, not in the next product cycle. Synthetic text, audio, images and deepfakes need disclosure. Retrofitting watermarking into a shipped pipeline costs more than designing it in.

Run your own evals on the models you actually deploy. Vendor benchmarks test the vendor's general capability. They do not test your prompts, your refusal boundaries, or your failure modes. A small local suite, run weekly, catches drift before a customer does.

Keep a documented model inventory. Which model, which version, which provider, which data residency, which date it changed. European procurement teams are already asking for this, and the August enforcement powers give that request teeth.

Engels moved to METR because he believes independent measurement is the only thing that can keep up. Europe has accidentally built the enforcement mechanism that gives independent measurement a market. The two facts arrived in the same summer, and they are more connected than the press release suggests. Whether anyone uses the tools is still an open question.

Does the EU AI Act apply to me if I only call a model through an API?

Yes. Using a model is "deploying" it. The Article 50 transparency obligations that became enforceable on 2 August 2026 cover organisations that put AI-generated content in front of EU users, not just the labs that trained the model. If you generate text, images, audio or video for EU customers, the labelling duty sits with you.

Do these resignations mean Google DeepMind is scaling back its safety work?

There is no public evidence of that. Engels' exit and the earlier departures from Anthropic are individual decisions by individual researchers, reported through their own public statements. What the pattern does show is that several people with direct access to frontier systems concluded that internal safety work was not moving fast enough for their own comfort.

What is the cheapest way to run my own model evaluations in the EU?

Open weights on your own hardware. Mistral Small 4 and off-peak DeepSeek-V4.1-Flash both sit around $0.15 per million input tokens as hosted APIs, and quantised versions run on a 16 GB consumer GPU. That keeps the data inside your own infrastructure, which removes a GDPR headache at the same time as it removes a per-token bill.

Discussion

No comments yet — be the first to share your thoughts.
X

Don't miss out!

Subscribe for the latest news and updates.