← Back to Journal
Strategy

They Paused the Race. They Didn't Pause the Work.

Daniela S. · 8 min read · September 2026

What Just Happened

Five days, in order, because the sequence explains the cause.

September 9. Jacob Coxon, a safety researcher with three years across Anthropic and OpenAI, resigned in public. He wrote that the two companies are more focused on beating each other than on safety, that they are racing toward self-improving superintelligence, and that they are "gambling with our lives." In a message to colleagues on Slack he said that without more caution there was a risk of causing human extinction. His posts reached more than 100 million people overnight.

September 11. Joe Benton, who had managed Anthropic's Scalable Oversight division, disclosed a resignation effective two weeks earlier. He is moving to METR to run autonomous-AI risk evaluations.

September 11. Sam Altman told employees OpenAI is considering slowing its frontier development, and said he hopes other labs join. OpenAI had already delayed its Astra model to harden safeguards against, in its own words, cyber misuse and unauthorized model actions.

September 12. Altman called a 2026 listing "ill-advised" and pushed the IPO to 2027 — stepping back from what had been reported as a potential one-trillion-dollar public offering.

And the part most coverage buried: Anthropic is not slowing down. It is still reported to be heading for a listing before year-end, at a valuation reported as high as $2.3 trillion.

The Reading Almost Everyone Will Get Wrong

The headline is that AI took a hit. It didn't, and the way to see that is the first question we ask about any stated impossibility: what is it resting on?

This one rests on the assumption that frontier capability is the industry. It isn't. Three separate things happened, and only one of them was a setback:

One. The capability race slowed. Deployment did not.

Two. The binding constraint stopped being cost and became trust.

Three. The two leading labs diverged. One walked away from a trillion dollars for safety. The other is accelerating toward a listing three times larger.

A divergence is not a collapse. It is a market discovering that it was pricing the wrong variable.

The Constraint Moved

For eighteen months the question every buyer asked was some version of *can we afford this?* That question is closed. On August 11 Anthropic cancelled its own scheduled price increase and made its mid-tier rate permanent; OpenAI matched within weeks. Frontier compute is now durably cheap and, for the moment, neither lab has reliable pricing power.

So cost is off the table. And as of this month, so is "who has the newest model" — because the people building the newest models are the ones asking to slow down.

What is left is the only question that was ever hard: can you prove it works, and who answers if it doesn't?

Notice what actually triggered this. Not a philosophical debate. A string of security incidents involving AI agents, and a lab hardening itself against *unauthorized model actions*. That is the precise failure mode of autonomy without supervision — an agent doing something nobody approved. The industry didn't get scared of intelligence. It got scared of unsupervised action.

What This Costs Us, Said Plainly

We build on Anthropic. Anthropic is the lab that is not slowing down, and it just lost two safety people in public — one of whom ran the division responsible for scalable oversight — on the way to the largest listing in the sector's history.

That is supplier concentration and reputational adjacency at the same time, and a client is entitled to raise it in a meeting. We would rather write it here than be asked it there.

The honest mitigation is not a slogan. It is that the same price convergence that closed the cost question also made switching cheap: the two leading labs are now within a rounding error of each other on price and mid-tier capability. Vendor lock-in is the weakest it has been in this cycle. That is a fact about the market, and it cuts in our favor, but we did not arrange it and we will not pretend we did.

The Gate Stopped Being a Cost

For as long as we have been selling this, "we put gates on AI" competed against "we ship faster." The gate read as friction. It was the thing you had to justify.

This week the largest AI company in the world paid roughly a trillion dollars of deferred valuation to buy the position that the gate is worth more than the speed.

We did not predict this. We wrote our signature — Created with human intelligence — in August, and we were careful even then to say what it does *not* claim. It does not claim the absence of AI. We build with AI, at machine speed, and we say so. What it claims is the thing no benchmark and no detector can test: who decides, and who is liable.

Our manifesto compresses it to five words: *the human doesn't produce — the human guarantees.*

That sentence was a positioning choice a month ago. This week it became a specification.

The Silver Lining Isn't Consolation

There are three, and none of them are comfort.

A pause freezes the target. Most organizations are behind the frontier, not at it. When the frontier stops moving, everyone behind it gets to catch up, and the value of *having the newest model* falls while the value of *deploying one well* rises. For anyone whose business is adoption rather than invention, a slowdown at the top is the most favorable weather there is.

The gap it exposes is the one that was already there. The 2026 AWS and Strand Partners study puts enterprise AI adoption in Mexico at 48% of organizations, up from 38% the year before — and says in the same breath that the constraint is no longer access to the tools. Nearly half the market has this. Almost none of them can show what changed. That gap didn't move this week; it just stopped being possible to ignore.

Going slowly stopped being embarrassing. The discipline that used to need explaining — nothing ships without an explicit yes, every claim gets graded, every gap gets declared as a gap — is now what the people who build the models are asking for out loud.

If You're the One Deploying

The question that just arrived in a lot of meetings is: *if the people building it are slowing down, should I stop?*

No. But you can no longer deploy without being able to answer three things, and they are the same three that were always underneath the work:

Who authorized this action? Not who ran it — who approved it, before it ran, with the option to say no.

How do you know it worked? Not the model's own report. A verification that could have failed and didn't.

Who answers if it's wrong? A person, by name. Accountability does not run on a GPU.

If you can answer those, a slowdown at the frontier changes nothing about your plans. If you can't, the slowdown didn't create your problem — it just took away the excuse that the technology wasn't ready yet.

The technology was ready. The method was the part that was missing.

Read why the signature was written for this →