Today's content converges on a structural reshaping of the OpenAI-Microsoft relationship, a surprisingly consistent cross-domain argument about verification as the real bottleneck in AI progress, and a detailed look at what deploying intelligence onto physical machines actually requires.

---

The AGI Clause Dies: OpenAI Escapes Microsoft's Orbit

Simon Willison did the archival work worth reading carefully. He traced how the artificial general intelligence (AGI) clause evolved from OpenAI's April 2018 charter ("highly autonomous systems that outperform humans at most economically valuable work") through December 2024 — when The Information revealed the clause was secretly operationalized as $100B in generated profits — to October 2025, when an "independent expert panel" was supposed to adjudicate. Today's language is different: revenue share payments continue "independent of OpenAI's technology progress." Willison reads this — and The Verge independently agrees — as the AGI clause being simply dead.

What changed structurally is significant. OpenAI can now distribute via any cloud — Amazon Web Services (AWS) Bedrock, Google tensor processing units (TPUs), not just Azure. Microsoft's IP license becomes non-exclusive. Andy Jassy confirmed OpenAI models are coming to Bedrock "in the coming weeks." Microsoft keeps a revenue share through 2030 and Azure-first launch access through 2032 but gives up the exclusivity that OpenAI said was limiting its enterprise reach.

The downstream implication flagged in Swyx's AINews: OpenAI can now access AWS Trainium and Google TPU capacity for inference, a real change for economics. Simultaneously, GitHub Copilot announced a move to usage-based billing starting June 1 — agentic workflows are consuming significantly more runtime than chat, and the industry's pricing models are catching up to that reality. Codex usage multipliers are now explicit: GPT-5.4 fast at 2x, GPT-5.5 fast at 2.5x.

---

Verification Is the Hard Problem Everywhere

Three separate pieces today converge on the same meta-challenge from different angles: how do you know something actually works?

Dwarkesh Patel makes the sharpest argument about science and reinforcement learning (RL). The common assumption is that AI will be disproportionately good at scientific breakthroughs because "science is verifiable" and models crush domains with tight verification loops. But the verification loop for scientific theories is often decades or centuries long, and even then, experiments don't definitively rule out alternatives. Copernicus's heliocentric model was actually less accurate than Ptolemy's geocentric model in 1543 — you couldn't have known ex ante it was more productive. The anomalous precession of Mercury led astronomers to hunt for a planet "Vulcan" for decades before Einstein resolved it with general relativity in 1915. What looks like the wrong research program in retrospect required unreasonable, idiosyncratic persistence to preserve until vindication.

Big conceptual breakthroughs require exactly what an RL loop can't reward: pursuing a hypothesis relentlessly across decades of ambiguous or even disconfirming evidence. Patel's conclusion is that you can't easily train an RL loop for conceptual scientific breakthroughs, and that a society of AI scientists would still need individual instances with idiosyncratic biases committed to keeping dormant research agendas alive.

Applied Intuition's founders arrive at a parallel conclusion from physical AI. Peter Ludwig describes the shift in their own validation work from binary verification ("did the car pass this specific Euro NCAP test?") to statistical validation ("how many nines of reliability, what's the mean time between failures?"). As models get better, finding the remaining faults becomes harder — the evaluation problem scales in difficulty with model capability. Qasar Younis adds that statistical validation is necessary but insufficient: Cruise's collapse wasn't purely a technology failure, it was also about how the company communicated with regulators and the public after an incident. There's a version, Younis argues, where Cruise still exists.

Swyx's AINews surfaces a third instance of the same problem in agent benchmarking. A new study on coding agents shows that agentic coding can consume roughly 1,000x more tokens than chat or code reasoning, with usage varying 30x across runs on identical tasks, and more spending not monotonically improving accuracy. Sarah Hookr's argument is gaining traction: most agentic benchmarks are overfit to automatically verifiable tasks, while the important frontier is "open-world, uncertain, non-fully-verifiable work." Cost-aware evaluation is becoming a first-class concern. AgentIR reframes retrieval for research agents by embedding the reasoning trace alongside the query, with a 4B model hitting 68% on BrowseComp-Plus versus 52% for larger conventional embedding models.

---

Physical AI: Deployment Constraints, Not Model Intelligence, Are the Bottleneck

The Applied Intuition podcast is the richest single piece of content today. Qasar Younis makes a point worth sitting with: "We're not really constrained right now by the intelligence of the models. It's actually deploying them on the hardware you're given." For physical machines, the binding constraints are latency (milliseconds, not seconds), power budget, physical size, and safety-critical reliability — not reasoning capability.

Peter Ludwig explains the "onboard vs. offboard" distinction that the screen-AI world doesn't have to think about. Off-board (data center) models can be arbitrarily large and slow; onboard models need millisecond-level latency, minimal power, and small footprint. The work is essentially distillation under extreme constraints — getting a capable model running on embedded hardware with multiple redundancies for when cosmic rays flip bits. That's not a metaphor: they design for hardware fault tolerance explicitly.

The operating system layer is underappreciated. Physical machines today are like phones before Android — so fragmented across dozens of operating systems that deploying an AI application uniformly is nearly impossible. Applied Intuition's OS product exists to consolidate that before layering autonomy on top. Without a common platform, there's nothing for AI to reliably run on. Ludwig built this after realizing existing operating systems weren't good enough — real-time sensor streaming, latency-critical actuator control, reliable over-the-air updates (bricking a car is a much bigger problem than bricking a phone) all require purpose-built infrastructure.

The production gap between demos and deployment is something Applied Intuition has accumulated hard-won pattern recognition about. Ludwig: "I can now look at any robotics demo and write down the next 20 problems they're going to hit." Humanoid robotics demos are impressive and brittle. The marathon China is running for humanoid robots is a deliberate prize-policy move to force reliability — like the DARPA Grand Challenge did for autonomous vehicles — because the industry knows the brittleness is the problem, not the capability demos.

On AI coding adoption: Claude Code has apparently overtaken Cursor as the hottest internal tool at Applied Intuition, tracked via an internal leaderboard. Ludwig notes a bimodal distribution emerging — engineers who are all-in on AI tooling versus those who haven't invested the hours — with "a productivity gap that is just enormous." Even embedded systems and GPU shader programming, which Ludwig would have said 6 months ago were outside AI's useful range, are now seeing meaningful assistance from current models.

---

China's Open-Weights Agent Push and the Infrastructure Race

The open-source model activity on the Chinese side is notable in volume and framing. Xiaomi released MiMo-V2.5 under MIT license with 1M-token context. The Pro variant is roughly 1T total parameters / 42B active, trained on 27T tokens in FP8; the smaller variant is 310B total / 15B active, trained on 48T tokens. Both are framed explicitly as agent-oriented systems, not chat models. Xiaomi paired the release with a 100T token compute grant for builders.

Kimi K2.6 from Moonshot is now #1 on OpenRouter's weekly leaderboard, described as handling up to 300 concurrent sub-agents across 4,000 coordinated steps. Practitioners are split: Kimi sometimes fixes bugs DeepSeek V4 cannot, but is materially slower. DeepSeek V4 Flash continues to see uptake as the speed-quality tradeoff option. The recurring pattern across Chinese labs is smaller or cheaper variants often outperforming their larger siblings on practical agent benchmarks.

Infrastructure support is maturing fast. vLLM 0.20.0 landed with DeepSeek V4 support, Flash Attention 4 (FA4) as default for multi-head latent attention (MLA) prefill, and TurboQuant 2-bit KV cache. A fix to FA3's two-level accumulation improved 128k needle-in-a-haystack accuracy from 13% to 89% while retaining FP8 decode speedups. Google bifurcated TPU v8 into training-specific (8t) and inference-specific (8i) variants — the first time Google has split custom silicon by workload — claiming 2.8x faster training and 80% better inference performance-per-dollar than prior generation. OpenAI, Anthropic, and Meta are reportedly buying TPU capacity.

Sakana AI's Conductor is worth flagging separately: a 7B model trained with RL to orchestrate a pool of frontier models in natural language, deciding which agent to call, what subtask to assign, and which context to expose. It reportedly reached 83.9% on LiveCodeBench and 87.5% on GPQA-Diamond, beating any single worker in its pool. "AI managing AI" as a distinct axis of test-time scaling is now a thing multiple labs are exploring.

---

Today's content surfaces a question that sits uncomfortably across all these themes: the domains where AI is making the fastest practical progress — coding, agent orchestration, mathematical reasoning — are precisely the domains with tight, cheap, fast verification loops. The domains where verification is expensive, delayed, or genuinely uncertain (science, physical deployment, open-world agent tasks) are where the gap between benchmark performance and real-world impact is widest. Dwarkesh's point about RLVR being ill-suited for big scientific breakthroughs, Applied Intuition's point about deployment constraints mattering more than model intelligence, and Swyx's point about agent evals being overfit to verifiable tasks are all the same observation from different vantage points. The scaling question that doesn't get asked enough: what does more model capability actually unlock in domains where you can't close the verification loop cheaply?

---

TL;DR - OpenAI-Microsoft: The AGI clause is effectively dead; OpenAI can now run on any cloud, losing Azure exclusivity while Microsoft keeps a revenue share through 2030 — a structural shift in how OpenAI reaches enterprise customers. - Verification is the meta-bottleneck: Dwarkesh on science, Applied Intuition on physical AI, and AINews on agent evals all independently argue that RL loops break down wherever ground truth is uncertain, delayed, or expensive — which is most of the domains that actually matter. - Physical AI: Applied Intuition's founders argue model intelligence is not the constraint on deploying autonomy — safety-critical hardware limits, latency requirements, and the OS fragmentation problem are — and the production gap between demos and real deployments remains enormous. - China open-weights: Xiaomi MiMo-V2.5 (MIT, 1M context, agent-first) and Kimi K2.6 lead a wave of agent-oriented releases, while infrastructure support matures rapidly across vLLM, Google's newly bifurcated TPU silicon, and multi-agent orchestration frameworks.

Compiled from 4 sources · 9 items

• Simon Willison (5)
• Swyx (2)
• Rowan Cheung (1)
• Dwarkesh Patel (1)