950
GOOGLE EMPLOYEES WHO SIGNED THE OPEN LETTER BACKING ANTHROPIC ON THE DOD CONTRACT
Anthropic refused to drop two redlines — no domestic mass surveillance use, no autonomous weapons. The Pentagon wouldn't accept the limits. OpenAI signed a deal immediately. Google signed despite an open letter from 950 of its own staff asking it not to.
The week the three frontier providers showed how they'd behave in a room with the Pentagon
On Monday and Tuesday, TechCrunch reported that employees at OpenAI and Google were publicly backing Anthropic's legal fight with the Pentagon. By the end of the week, Fortune confirmed the count: 950 Google employees had signed an open letter asking the company to follow Anthropic's lead and refuse a DoD contract without similar guardrails. Anthropic's two redlines were narrow and specific: no use of Claude for domestic mass surveillance, no use for autonomous weapons.
The Pentagon wouldn't accept those limits. Relations between the administration and Anthropic collapsed, and a judge granted Anthropic an injunction against the contract designation while the case proceeds. OpenAI moved in the other direction in the same week, signing a DoD deal on terms the Pentagon found acceptable. Google followed, despite the open letter. Three providers, three postures, all crystallised inside seventy-two hours.
This is the part of the AI-safety conversation that does not show up in alignment papers. The technical question of whether a frontier model can be controlled is, in the end, less consequential than the contractual question of who gets to use it for what. Two of the three providers answered that question this week by accepting terms their own employees objected to. The third answered it by losing the contract.
Underneath the policy fight, OpenAI shipped two substantive product updates: improvements to instruction hierarchy in frontier LLMs, and equipping the Responses API with a computer environment so the model can take action on a real machine. Both are interesting on their own. In the context of the same week's news, both also describe what a Pentagon-contracted assistant would need to do.
Anthropic drew two lines — no domestic mass surveillance, no autonomous weapons. The Pentagon refused. OpenAI signed instead. Nine hundred and fifty Google employees signed a letter. Google signed too.
Want to spot this in your own conversations?
CLEAR is the free six-lesson course on the patterns AI quietly runs on you.
Take the course →
Founder's note — Second issue of the catalogue. The DoD storyline carries forward through April; if you only read one back-catalogue issue, this is the one.
◆The Notebook
Anthropic and the DoD failed to agree a revised contract this month. The provider insisted on two specific carve-outs; the Pentagon insisted the military could use the model "for all lawful use." A judge granted Anthropic an injunction. The political question is contractual, not technical.
via TechCrunch
A capability post: the Responses API can now drive a real computer environment. Useful for agentic workflows. Worth reading the access-control section before you wire this into anything in production.
via OpenAI blog
A behind-the-scenes look at how OpenAI handles conflicting instructions between system prompt, developer message, and user input. Quiet post; relevant to anyone who builds agents.
via OpenAI blog
◆Worth Your Time
TechCrunch
The framing piece. Worth reading in full; the timeline matters more than the comment threads.
Fortune
Adds the 950-employee number. A useful counterweight to the official-statement narratives.
TechCrunch
The end of the storyline, published in late April. Worth reading alongside the March pieces to see how the same posture played out under contract.
OpenAI
Quiet technical post. Relevant if you are building agentic systems where the developer prompt and user prompt can fight.
OpenAI
A capability post. Read the access-control section before wiring this in.
The Probe · Test Yourself
A frontier AI provider refuses a major government contract on two narrow grounds. Two competitors sign the same week. From a market-trust standpoint, which signal is most useful to a customer trying to choose a provider for a regulated workload?
AThe price the contract was signed at
BWhich model performs best on a benchmark
CThe specific concessions each provider was and was not willing to make
DThe number of regulators publicly endorsing each provider
Reveal the answer
Answer: C — The specific concessions each provider was and was not willing to make
A and D track posture, not behaviour. B tracks capability, which is unrelated to the trust question. C is the one signal that tells you what each provider will do in a future negotiation when your contract has its own redline question. The published list of concessions refused — and accepted — is the actual market signal.
Reply and tell me what you've noticed. If you advise enterprise buyers on AI vendor selection, send me the criteria your better clients use. I'm collecting a non-public framework to share back in a future issue.
Free where it can be. Honest where it has to be.
— Three places to go from here —
Course
CLEAR
Six free lessons on the patterns AI runs on you.
Start →
Tool
LiveScope
Chrome extension that flags what AI cites without checking.
Install →
Read
The Agreement Trap
15-chapter book on living inside the exchange. £5.99 lifetime.
Read →