48-Hour AI
All Episodes

Claude’s Riemann Leap and NVIDIA’s Lightning Model

This episode dives into an unreleased Claude math agent that reportedly pushed progress on the Riemann Hypothesis and used Lean 4 to formally verify every step. It also explores NVIDIA’s Nemotron 3.5 Lightning, sparse MoE speedups, and how fast local open-weight models could reshape agentic workflows and AI economics.


Chapter 1

Claude Unreleased Math Agent and the Riemann Breakthrough

James Turner

Sixty AI subagents running in parallel inside Claude Code. Just let that sink in for a second. We are talking about an unreleased Claude model from Anthropic that just tackled the Riemann Hypothesis, a math problem that has stumped humanity for over one hundred sixty years. And it did not just tinker around the edges. It moved the proven bound of zeros on the critical line from forty one point six percent all the way to sixty seven point two percent.

James Turner

I mean, think about how insane that jump is. Mathematically speaking, progress on the Riemann Hypothesis usually moves by fractions of a percent over decades. But this system ran for thirty six hours straight. It executed twenty four hundred shell commands, cycled through six hundred fifty failed mathematical hypotheses, and finally landed on a unified geometric proof strategy. And the kicker? Every single step was formally verified by Lean four theorem provers, so we know the math actually holds up.

James Turner

Now, I know what some skeptics are already asking. Is this real mathematical discovery, or is it just ultra high speed brute force? You set up sixty subagents in a Lean four sandbox, throw endless compute at the problem, and let them guess until something sticks. Is that deep intuition? Well, here is my take on it. When a chemist runs six hundred fifty failed physical reactions in a laboratory before finding a synthesized compound that works, we call that the scientific method. Discarding six hundred fifty flawed proofs in a digital sandbox is not cheating, it is the digital equivalent of rigorous experimental science.

James Turner

And honestly, I, I, I have seen a glimpse of this dynamic firsthand. Last week I set up an overnight Claude Code agentic run on a complex codebase refactor. I went to bed expecting it to crash in twenty minutes. When I woke up and inspected the raw terminal logs, my jaw dropped. Around hour three, the agent hit an obscure dependency loop, failed ninety two times in a row, and then, without any human intervention, wrote a custom bash script to inspect its own memory state, isolated the bug, and fixed it. Seeing an AI self correct in real time after hundreds of failed execution loops is a strange, breathtaking feeling. It feels less like running a tool and more like managing an tireless junior engineer.

Chapter 2

Nemotron Three Point Five Lightning and Sparse Speedups

James Turner

So if multi agent workflows like Claude Code are going to execute thousands of commands over thirty six hour sessions, we hit a massive bottleneck very fast. Compute costs and inference latency. And that brings us to what NVIDIA just dropped with Nemotron three point five Lightning. This is an open thirty billion parameter Mixture of Experts model, but here is the trick, it only activates three billion parameters per token. And it hits eighty six percent on PinchBench while delivering four times faster output throughput.

James Turner

Why does that ultra sparse routing matter so much? Because suddenly, you can run long, one million token agentic reasoning sessions on a single NVIDIA H100 or DGX Spark board right at your desk, without needing a massive datacenter cluster just to hold model weights in memory. You get local, blazingly fast iteration cycles.

James Turner

Of course, there is a catch we have to push back on. Does sparse routing introduce subtle context degradation? When you only activate a three billion parameter specialist team for each token, do you lose the holistic, deep multi step reasoning of a monolithic seventy billion dense model? It is a real trade off. If the router misdirects a token mid proof, a long chain of thought can unravel. But when you combine open weights with local inference engines like vLLM and SGLang, the economics shift entirely. Local four times speedups allow developers to run ten attempts in parallel for the cost of one cloud API call.

James Turner

And that is where the real disruption lives. Closed model API monopolies rely on charging high per token fees for long reasoning chains. If local open weight models can deliver lightning fast agentic execution on developer hardware, the entire economic moat of closed APIs starts to look fragile. It is going to be a wild ride. Catch you all next time.