Sam: Anthropic shipped two models yesterday — Claude Fable 5 and Mythos 5 — and the headline number that stopped me cold was this: Fable 5 completed a full code migration for Stripe in one day. A migration that Stripe estimated would have taken a human engineering team two months. That's not a benchmark score. That's a production codebase, with real dependencies, real edge cases, real integration tests. And then there's the other model, Mythos 5, which autonomously designed drug candidates — and which Anthropic is not releasing to the public because it also demonstrated offensive cyber capabilities they consider too dangerous for general access. We have a lot to unpack today.

Priya: Welcome to AI Revolution for Wednesday, June 10th, 2026. I'm Priya Nair, alongside Sam Kim. Big show today. We're going deep on both Claude models and what Anthropic's tiered release strategy means for how frontier AI gets deployed going forward. We'll also cover OpenAI negotiating for a 10-gigawatt data center with Nvidia backing the bill, China's $295 billion domestic AI infrastructure push, Google's real-time voice translation hitting 70 languages, and a clever energy-saving technique for LLM training out of the University of Twente. Let's get into it.

Sam: So let's start with what we actually know about these two models. Fable 5 is the publicly available one. It leads nearly every major benchmark, including SWE-bench Verified at 95 percent. For context, SWE-bench Verified tests whether a model can take a real GitHub issue from a real open-source project and produce a working patch. Ninety-five percent is extraordinary. A year and a half ago, models were in the twenties on this benchmark.

Priya: And the Stripe migration story is the more visceral way to understand that number. We're talking about a model that can hold enough context about a large, complex codebase — understand the architecture, the dependency graph, the testing requirements — and execute a coherent multi-step migration plan across it. The question I keep coming back to is: what does the human team do during that one day? Are they reviewing? Are they just watching?

Sam: From what Anthropic has shared, there's still human review and validation, but the model is doing the actual code generation, refactoring, and test writing. The human role shifts from authoring to auditing. Now, here's what's technically interesting to me — Anthropic is calling this the Mythos model class, with Fable 5 being the first publicly available member. The naming suggests they've made a generational architecture change, not just a training data or scale improvement. We don't have full details on what changed architecturally, but the jump in coding capability alongside the jump in scientific reasoning suggests improvements in how the model plans and executes multi-step tasks — likely better chain-of-thought reasoning, possibly longer effective context utilization, or both.

Priya: And then there's the pricing and the policy decisions, which tell their own story. Fable 5 costs ten to fifty dollars per million tokens, roughly double what Opus 4.8 costs. That's a significant premium, and it signals that Anthropic believes the capability gap justifies it. But there are two things that should raise eyebrows for enterprise users. First, their safety filters are blocking about nine percent of requests. That's nearly one in ten. For a developer relying on this in a production pipeline, that's a meaningful failure rate you have to design around.

Sam: And second — and this one is genuinely concerning — Anthropic has implemented a new 30-day data retention policy that applies even to customers who previously had zero-data-retention contracts. That's a contractual override, and for any organization dealing with regulated data — healthcare, finance, government — that's a compliance problem, full stop.

Priya: Now let's talk about Mythos 5, the restricted model. This is where Anthropic's release strategy gets really interesting. Mythos 5 apparently demonstrated the ability to autonomously design drug candidates, which is a remarkable scientific capability. But during safety testing, it also showed offensive cyber capabilities that Anthropic deemed too risky for general release.

Sam: So instead of a binary choice — release it or don't — Anthropic created a tiered access model. Full Mythos 5 goes to vetted cyber partners and trusted organizations. The public gets Fable 5, which Anthropic says has been deliberately constrained so it can't be used for cyberattacks. This is a new deployment paradigm. We've seen capability restrictions before, but this is the first time a frontier lab has essentially said: this model is too capable for the general public, but here's a version with the dangerous parts removed.

Priya: The question is whether this becomes a template. If the most capable models are always gated behind trusted-partner programs, you get a world where cutting-edge AI capability is available only to a small set of pre-approved organizations. There are legitimate safety reasons for that. There are also obvious concerns about concentration of power and who gets to decide who's trusted.

Sam: Let's shift to infrastructure, because the compute story is getting truly wild. OpenAI is in negotiations to lease a planned 10-gigawatt data center campus in Ohio, and Nvidia is reportedly in discussions to help finance it.

Priya: To put 10 gigawatts in perspective — today's largest AI data center deployments are typically in the 100 megawatt to 1 gigawatt range. Ten gigawatts is an order of magnitude beyond the current ceiling. That's roughly the output of ten nuclear power plants. It would be the largest single concentration of AI compute ever built.

Sam: And the Nvidia co-financing angle is significant. When your chip supplier is willing to invest in your data center, it tells you two things. First, the scale of compute needed for next-generation training runs has gotten so large that even well-funded labs need supplier co-investment. Second, Nvidia has enough confidence in sustained demand to put their own capital at risk. This isn't a customer-vendor relationship anymore — it's more like a joint venture.

Priya: Meanwhile, on the other side of the Pacific, China announced a $295 billion investment in a national AI data center network over the next five years. And here's the key constraint: at least 80 percent of the hardware must come from domestic suppliers, primarily Huawei. That's a mandate that will stress-test whether Chinese chip vendors can deliver at the scale and performance level required for frontier AI training.

Sam: Right. Huawei's Ascend GPUs exist, and they're being deployed, but they're generally considered a generation or more behind Nvidia's current offerings in terms of both raw performance and the software ecosystem around them. Mandating 80 percent domestic procurement means China is essentially accepting a near-term performance tax in exchange for long-term supply chain independence. And in parallel, Taiwan is considering criminalizing AI chip smuggling to China for the first time, which would tighten the enforcement regime around existing export controls.

Priya: We're watching the global AI supply chain bifurcate in real time. Two separate compute ecosystems, two separate hardware stacks, two separate sets of frontier models. That has implications for interoperability, for research collaboration, and ultimately for how AI capabilities diverge between the two systems.

Sam: Switching gears — Google released Gemini 3.5 Live Translate, and the technical approach here is worth understanding. Traditional machine translation systems work on sentence boundaries. They wait for you to finish a thought, translate it, then output the result. Gemini 3.5 Live Translate operates continuously — it's translating as you speak, without waiting for sentence boundaries. And it claims to preserve the speaker's prosody: tone, pacing, pitch.

Priya: That's a meaningful architectural change. Streaming translation that also captures paralinguistic features means the model has to simultaneously process incomplete semantic information and acoustic characteristics, then generate output in a target language that preserves both. Google Meet goes from supporting five languages to over 70 with this release. If it works as described, it essentially removes language as a barrier to real-time conversation at scale.

Sam: Quick hit on a research result I liked. A team at the University of Twente presented a technique at the Computing Frontiers conference that reduces LLM training energy consumption by up to 14 percent with no loss in training speed. The core idea is straightforward and clever: GPUs don't need to run at their maximum clock frequency during every phase of computation. There are moments — during memory transfers, during certain types of operations — where the GPU is bottlenecked by something other than clock speed. By dynamically adjusting the GPU's clock frequency to match what's actually needed at each moment, you eliminate the energy waste from running the clock faster than necessary.

Priya: Think of it like an automatic transmission versus keeping your engine at redline all the time. You match the RPMs to the actual load. Fourteen percent may not sound enormous, but when you're talking about training runs that consume tens of gigawatt-hours, that's real power and real money. And it's hardware-agnostic — any GPU-based training setup could potentially apply this.

Sam: Brief note on Germany: their National Security Council has approved the creation of DE-AISI, a German AI safety institute modeled on the UK's AISI. It will conduct independent security testing of frontier models. That makes three national-level safety evaluation bodies now — US, UK, and Germany. The pressure on frontier labs to support mandatory third-party red-teaming as a condition of market access is steadily building.

Priya: Looking ahead — the thread connecting today's stories is that we're entering a phase where capability is outpacing the frameworks for deploying it. Anthropic has a model it considers too dangerous for general release. OpenAI needs 10 gigawatts of power for its next training runs. China is spending $295 billion to build an independent compute stack. And governments are standing up new institutions to evaluate models they don't build and may not fully understand.

Sam: The Anthropic tiered-release model is the one I'm watching most closely. If Mythos 5 stays restricted and competitors don't adopt similar restraints, Anthropic faces a competitive disadvantage for being cautious. If competitors do adopt similar restraints, we end up in a world where the most powerful AI capabilities are only available to a curated set of organizations. Neither outcome is obviously right. That tension is going to define the next year of frontier AI deployment.

Priya: And the data retention change from Anthropic — quietly overriding zero-retention contracts — that's going to be a flashpoint. Enterprise trust is hard to build and easy to lose. I'll be watching whether that policy survives contact with their largest customers.

Sam: That's the show for today. Show notes and links to everything we discussed are at cleartext.fm.

Priya: Thanks for listening. We'll be back tomorrow.