Nobody at the Top Is Claiming They Know How to Keep AI Safe

Roman Yampolsky has been working on AI safety longer than most people in the field have known what to call it. So when a thread noting his recent podcast appearance began circulating, the sentence that landed hardest wasn't about timelines or threat models — it was this: nobody is currently claiming to have a viable safety mechanism.[¹] No lab. No paper. No concrete framework. The post drew no pile-on, no correction, no rival claiming otherwise. It just sat there.

That admission has a particular weight right now because of where Anthropic finds itself. The company built its entire identity on being the careful one — the lab that would slow down before shipping something it couldn't control. Then it shipped Mythos, a model capable of exploiting vulnerabilities across every major browser and operating system, and described the decision in terms that didn't quite square with that identity. The cognitive dissonance landed in safety-adjacent communities not as outrage but as something quieter: a kind of updating. If the lab most committed to caution can't hold its own line, the question of who's actually doing safety work — versus who's maintaining a safety-branded landing page — becomes harder to answer charitably.

One commenter put it with the economy of someone who'd been waiting to say it: "the market for AI safety landing pages with stock photos of shields is genuinely outpacing the market for AI safety research at this point."[²] It's a joke, but jokes in technical communities usually carry a precise claim. What's being described is a specific divergence — between safety as an institutional performance and safety as a technical problem with open solutions. The former is thriving. The latter, by Yampolsky's own account, remains unsolved.

Into that gap steps a different kind of argument, one that's been circulating in safety circles for a few weeks now: that framing AI governance as a corporate responsibility problem is itself the error. The structural version of this argument treats safety not as a feature labs might choose to implement but as a constitutional problem — something that requires external architecture, not internal virtue. It's a harder sell in a policy environment moving toward procurement guidelines and voluntary commitments, but it's gaining traction precisely because the voluntary approach keeps producing the same result: capable models, open questions, reassuring press releases.

What's notable about this quiet period is the quality of the skepticism surviving it. The AI ethics conversation generates enormous volume on its best days and tends to flatten into generalities. What's circulating now is narrower and more specific — focused on the gap between claimed safety commitments and the absence of any verifiable mechanism for honoring them. A Bluesky commenter asked whether AI safety standards would stifle innovation rather than prevent misuse,[³] the perennial counterargument, and it landed with less force than it might have a year ago. The people who'd normally push back with optimism about interpretability and alignment research are quieter than usual. That's not nihilism — it's the sound of a field waiting for something to actually work.