Sam: A startup called Recursive just came out of stealth with $650 million and a stated mission of building recursive self-improvement as — and I'm quoting directly — "the fastest path to superintelligence." That's a lot of money and a very specific technical claim. We'll dig into what recursive self-improvement actually means architecturally, why it's contested, and what it would take to actually work.

Priya: Welcome to AI Revolution, I'm Priya Nair, here with Sam Kim. It's Wednesday, May 13th, 2026. Today's episode covers a lot of ground — we've got Isomorphic Labs raising $2.1 billion to push AI drug discovery into actual clinical trials, a new Medicare payment model that almost nobody in tech has noticed but could reshape AI in healthcare, Nvidia building micro data centers at power substations, and a security story out of Hugging Face that should concern anyone managing an ML pipeline. Let's get into it.

Sam: So let's start with Recursive, because the technical claim here deserves serious unpacking. Recursive self-improvement, as a concept, goes back decades in AI safety and capability research. The basic idea is that an AI system gets better at the task of improving AI systems — so each iteration produces a more capable optimizer, which produces a better next version, and so on. The theoretical concern has always been that if you cross some capability threshold, the improvement curve stops being linear and starts compounding in ways that are hard to predict or control.

Priya: And the reason this is technically contested is that it's genuinely unclear where the bottlenecks actually sit. Is it the optimization algorithm? The architecture? The training data? The evaluation criteria? Because if your self-improving system is optimizing against the wrong objective — even slightly wrong — each iteration amplifies that misalignment. The compounding works in both directions.

Sam: Exactly. And we don't know yet what Recursive is actually building — they emerged from stealth, they have the funding, but the technical specifics aren't public. What we can say is that $650 million is serious capital for a serious bet. This is one of the largest stealth-mode AI launches we've seen. The questions I want answered: what's their proposed mechanism for improvement, how are they thinking about the evaluation problem, and who's running safety work alongside capability work. Those aren't rhetorical questions — the answers will tell you a lot about whether this is rigorous or reckless.

Priya: Worth watching closely. Now, over to Isomorphic Labs — $2.1 billion Series B led by Thrive Capital. This one is different in character because Isomorphic has a concrete technical foundation to point to.

Sam: Right. This company was built on the AlphaFold lineage — the work that cracked protein structure prediction. Their platform, IsoDDE, extends that foundation toward drug design. Predicting protein structure was a huge unlock, but drug discovery requires more: you need to model how a small molecule actually binds to a target, what the binding affinity looks like, what off-target effects might emerge, how the molecule behaves in biological context. These are much harder computational problems.

Priya: And what this funding round signals is that Isomorphic thinks they've built enough of that pipeline computationally to justify moving candidates into actual clinical trials. That's the meaningful threshold here — going from "we can model this" to "we're running this in humans." Clinical trials are expensive, slow, and failure-heavy. The bet is that better computational screening upstream means the candidates entering trials are higher quality, which should improve success rates.

Sam: The honest caveat is that we won't know for years whether that bet pays off. Drug development timelines are long. But the capital commitment from sophisticated investors suggests real evidence of progress in the platform, not just extrapolation from AlphaFold's reputation.

Priya: Let's talk about the Medicare ACCESS model, because this is the story I suspect most of our listeners haven't seen, and it has significant practical implications.

Sam: So the gap being addressed here is structural. Medicare has historically paid for specific clinical encounters — a visit, a procedure, a test. There was no billing code, no reimbursement pathway for an AI system that monitors a patient between appointments, follows up on medication adherence, or coordinates a referral. The economic incentive to build and deploy those systems in healthcare didn't exist within the reimbursement structure.

Priya: ACCESS creates that pathway for the first time. It's a payment model specifically designed to reimburse AI agents performing care coordination and monitoring functions. And this matters enormously for adoption velocity. Healthcare AI has been technically capable of doing a lot of this work for a while — the barrier wasn't the technology, it was that there was no economic model for deploying it at scale within the existing system.

Sam: From an architecture standpoint, think about what these agents actually need to do: persistent patient state management, integration with EHR systems, decision-making about when to escalate versus handle autonomously, and auditable logs for compliance. These are non-trivial engineering problems. But the harder problem has been the business model. If CMS is now willing to pay for this, you should expect a significant acceleration in deployment.

Priya: The open question is oversight and error accountability. When an AI agent misses a medication adherence issue or doesn't escalate appropriately, the liability and clinical governance questions are complex. The payment model existing doesn't automatically resolve those.

Sam: Now let's shift to infrastructure. Two stories here that connect. Nvidia is building approximately 25 micro data centers — we're talking five to twenty megawatts each — directly at utility substations across five US utilities. The core idea is dynamic compute shifting: when power is available at one substation, route workloads there. When demand on the grid changes, shift compute elsewhere.

Priya: This is a genuinely different architectural model for AI infrastructure. The standard approach has been: build the biggest data center you can in a place with cheap power and good cooling, and route network traffic to it. What Nvidia is proposing flips the dependency — instead of moving data to compute, you move compute toward power. The compute is the mobile layer.

Sam: It works because inference workloads have some flexibility. Not all queries are equally latency-sensitive. You can queue certain workloads, shift them geographically within bounds, and optimize for power cost without meaningfully degrading user experience. Training is harder to distribute this way, but inference is a reasonable starting point.

Priya: And then there's the report about Google and SpaceX exploring orbital data centers. I'll be direct: the economics don't pencil out today. Power in orbit is expensive, latency for most applications is a real problem, and the cost per compute unit is dramatically higher than terrestrial. But the fact that this conversation is happening at all tells you something about how constrained terrestrial power and land are becoming.

Sam: It's a thermometer reading on the infrastructure pressure, more than a near-term technical development. Filed under: watch this space.

Priya: On the agent tooling side — AWS WorkSpaces now supports AI agents operating legacy desktop applications through computer vision and input simulation. No API required. Agents authenticate via IAM, get a managed virtual desktop, and interact with software the same way a human would — by looking at the screen and generating input events.

Sam: The technical context here is important. Computer vision-based agents are dramatically more expensive to run than API-based agents. The Reflex benchmarks cited show 45 times more token consumption for vision-based interaction versus structured API calls. So this is not the efficient path. But it's often the only path — there's an enormous installed base of enterprise software that simply has no API surface, and organizations aren't going to replace it quickly.

Priya: So WorkSpaces is solving a real problem, with a real cost penalty attached. Teams evaluating this need to think carefully about which workflows justify that compute overhead and which don't. It's a bridge technology, and it should probably be treated as one.

Sam: Before we look ahead — the Hugging Face security story. A malicious repository posing as an OpenAI release delivered infostealer malware to Windows machines. Approximately 244,000 downloads before it was caught, though that number may have been artificially inflated by the attackers to build social proof.

Priya: The mechanism here is worth understanding. Model registries work on trust signals — download count, organizational affiliation, community ratings. Attackers are learning to game those signals. A fake repo that claims to be from a well-known organization and inflates its own download count looks legitimate to someone doing a quick scan. The supply chain risk in ML pipelines is the same category of problem as dependency confusion attacks in software packages, just applied to model artifacts.

Sam: Any team pulling models from public registries should have verification processes — checking hashes, validating provenance, running behavioral analysis before anything touches production. This won't be the last time this vector gets exploited.

Priya: Looking ahead — what do today's stories point toward collectively?

Sam: A few threads. On self-improvement: I expect we'll see more technical detail from Recursive in the coming months, and the AI safety community will scrutinize it hard. The question of whether recursive self-improvement can be made safe and steerable is one of the most open technical questions in the field right now. The funding doesn't resolve it, but it puts resources behind one attempted answer.

Priya: On healthcare: the ACCESS model is a policy unlock, but the real technical work — reliable agents that can navigate heterogeneous EHR environments and make sound escalation decisions — is still being built. I'd expect significant investment flowing into clinical AI infrastructure over the next 12 to 18 months as the reimbursement pathway becomes real.

Sam: And on infrastructure: the Nvidia substation pilot and the orbital compute discussions are both symptoms of the same underlying constraint. Power availability is now a primary limiting factor for AI scaling, and the industry is starting to explore solutions that would have seemed exotic just a few years ago. Whether those solutions work at scale is an open question, but the direction of exploration tells you something about how seriously the constraint is being taken.

Priya: Lots to watch. That's the show for today — show notes and links to everything we covered are at cleartext.fm. We're back tomorrow with more. Thanks for listening.