AIToday
Large Language ModelsAI Coding Assistantsnote AIPublished: Oct 24, 2026, 01:00 JST

DeepMind AI proves 26 Busy Beaver machines in Lean 4

Send on LINE
DeepMind AI proves 26 Busy Beaver machines in Lean 4

3 Key Points

  1. What happened

    The preprint reports that a Gemini 3.1 Pro pipeline, run on 1,163 open machines from BB(6), BB(2,5) and BB(3,3), produced 52 candidates and 26 machines with sorry-free Lean 4 proofs; 18 of the 26 came from a later Gemini 3.8 Flash system with access to the pipeline's proved code.

  2. Why it matters

    The halting question for all 11 newly discovered machines remains unresolved; the AI found acceleration rules, not answers to whether they halt. A reply: An AI system can turn raw tape output into formal proofs, but stopping verdicts for the 11 new machines remain open, and most of the proved results came from a second system.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The preprint sits at the boundary between problem-solving and theory-building. Earlier AI wins in mathematics, such as the IMO medal systems or the Lean 4 formalization of Fermat's Last Theorem, started from problems humans had already posed and defined. The Busy Beaver setting removes that scaffolding: the machine's tape gives no obvious statement to prove, and the paper's first stage compresses raw tape into repeating-block exponents so an LLM can look for patterns at all. It is that compression step, not the proving step, that defines what the system can see.

The paper's own Antihydra formulas show why the two-way Lean loop matters. The informal rules on page 5 and page 7 allow a parameter value of zero, which makes a step count come out as -1, yet the natural trajectory starting from a blank tape never reaches that boundary, so the error stayed hidden. The four-persona rewriting loop, with a Problem Setter that can change the theorem statement, is presented as the fix for exactly this kind of hand-waving, and the Stellar BB6 Protocol uses five anti-cheat checks to stop the system from rewriting a theorem into something trivial.

Two limits remain visible. The Stage 1 pipeline names only 8 of the 26 machines; the rest came from a later Gemini 3.8 Flash system that could read the earlier proved code and was rewarded for more compressed acceleration, which suggests template transfer rather than fresh discovery. And because Algorithm 1 and 2 hard-code a repeating-block, Collatz-like view, the pipeline found only 52 candidates among 1,163 open machines and none from BB(3,3), leaving most of the search space untouched by its chosen lens.

FAQ
What did the AI actually prove about the newly discovered machines?
It proved that each machine's low-level execution is equivalent to a closed set of Collatz-like macro transition rules, with sorry-free Lean 4 proofs. It did not prove whether those 11 machines halt or run forever.
How many of the 26 proved machines came from the pipeline described in the paper?
Only 8 of the 26 came from the Gemini 3.1 Pro four-stage pipeline alone. The other 18 came from a later Gemini 3.8 Flash automated research system given access to the pipeline's proved code.
Did every proved result get checked by hand?
No. The body says all final Lean statements were manually validated, but also says the 11 Stage 2 rediscoveries were formally proved yet not checked by hand, so the hand check strictly covers 15 machines.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGrok Bot hands-on: four casual bots, one costly catch