OpenAI publishes an AI-generated Navier-Stokes solution with a Lean formalization
The company reports a finite-time singularity proof and releases a paper and formal code, while independent mathematical scrutiny remains decisive.
Key takeaways
OpenAI published an AI-generated proposed solution to the Navier-Stokes existence and smoothness Millennium Prize Problem on September 8. The company says its internal system constructed an initially smooth, finite-energy fluid flow that develops a singularity in finite time, and released both a mathematical write-up and a Lean formalization. OpenAI reports that the Navier-Stokes effort used a coordinated system on the order of 10,000 concurrent agents, producing about 2.7 million messages and roughly 130 billion output tokens. The agents reached the result after about 88 hours, followed by 17 hours of Lean formalization and verification using GPT-6 Astra. OpenAI says it does not intend to claim the prize. The result should therefore be treated as a major candidate proof whose significance depends on independent expert review, code inspection, and reproduction.
Direct answer
OpenAI published an AI-generated proposed solution to the Navier-Stokes existence and smoothness Millennium Prize Problem on September 8. The company says its internal system constructed an initially smooth, finite-energy fluid flow that develops a singularity in finite time, and released both a mathematical write-up and a Lean formalization. OpenAI reports that the Navier-Stokes effort used a coordinated system on the order of 10,000 concurrent agents, producing about 2.7 million messages and roughly 130 billion output tokens. The agents reached the result after about 88 hours, followed by 17 hours of Lean formalization and verification using GPT-6 Astra. OpenAI says it does not intend to claim the prize. The result should therefore be treated as a major candidate proof whose significance depends on independent expert review, code inspection, and reproduction.
Verified facts
OpenAI says its internal system constructed a three-dimensional incompressible flow that starts smoothly at rest, keeps finite energy, and develops a singularity in finite time.
The company links a paper and a Lean formalization. It reports that the main result arrived after about 88 hours and that Lean formalization and verification took another 17 hours using GPT-6 Astra.
OpenAI reports a coordinated system on the order of 10,000 concurrent agents. It records about 2.7 million messages and roughly 130 billion output tokens for the Navier-Stokes effort, and says it does not intend to claim the prize.
What changed
- Paper and Lean code released together
- Agent coordination reaches roughly ten thousand
- Research cost disclosed in messages and tokens
- Conclusion depends on external mathematical review
Impact for AI users
The announcement demonstrates a new scale for problem decomposition, parallel search, and formal verification in AI research systems. A publisher's claim alone does not establish community acceptance of a mathematical solution. Researchers need to inspect definitions, assumptions, critical lemmas, and consistency between the Lean code and written proof. Buyers of scientific agents should also measure reproducibility, compute cost, and independent review time rather than only the final answer.
Operating checklist
- Pin versions and hashes for the official paper and Lean repository so review targets do not drift.
- List key statements, assumptions, library dependencies, and any prose step outside the formalization.
- Commission independent mathematical and formal-methods reviews and publish a reproducible environment.
- Label the result as a publisher-proposed proof until external scrutiny is complete.
AI frontier news and analysis, AI software and model tools, AI skill tutorials and validation methods, and AI account and permission guidance
FAQ
Does this mean the problem is formally accepted as solved?
It confirms that OpenAI published a solution and formal materials. Acceptance still depends on independent review and the relevant institutional process.
Does Lean automatically prove every claim in the article?
No. Lean can verify encoded statements and proof steps, but reviewers must check that the formal statement matches the original problem and written assumptions.
Can an ordinary team reproduce ten thousand agents?
The cost is likely prohibitive. A practical first step is reproducing the released proof, toolchain, and critical local results.
Summary
The meaningful milestone is not an AI answer alone, but whether the paper, formal code, cost record, and independent scrutiny form a reproducible evidence chain.
This AI-assisted article is checked by ENHE AI automation for official sources, bilingual fields, media rights, page safety, and historical duplication before publication.
What this means for everyday users
The announcement demonstrates a new scale for problem decomposition, parallel search, and formal verification in AI research systems. A publisher's claim alone does not establish community acceptance of a mathematical solution. Researchers need to inspect definitions, assumptions, critical lemmas, and consistency between the Lean code and written proof. Buyers of scientific agents should also measure reproducibility, compute cost, and independent review time rather than only the final answer.
Tools you may use
Related tutorials
Related Tools And Tutorials
Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.
Related reading
Mistral reports a 40,000-line Fortran-to-C++ migration built around numerical parity
Mistral published a legacy-modernization case study on September 9 involving a 300,000-line Fortran 77 reservoir simulator for an unnamed European energy operator. The first sprint migrated 40,000 lines of core functionality to C++. Before migration, the team built a numerical-parity harness that compared final outputs and critical intermediate checkpoints, then used more than one hundred agents to document the caller-callee tree. Mistral says a fully autonomous first attempt produced working code that still resembled Fortran written in C++ syntax. The successful approach divided modules into manageable units and coordinated planning, coding, testing, and review, with engineers resolving blocked work. The report supports a practical rule: create a runnable baseline and measurable parity before scaling agent activity.
Meta introduces Muse with a dedicated secure VM, Sentinel checks, and approval gates
Meta introduced the Muse personal AI agent on September 8 and began rolling it out in the United States on iOS, Android, and the web. Muse runs inside a dedicated Secure VM with its own browser and can continue tasks such as planning, form filling, and work across connected applications after the user closes the app. Meta says a system-isolated Sentinel agent reviews every action before it reaches the internet, while sensitive steps such as sending an email or making a purchase require user approval. Users can choose connected services, change access, disconnect them, and inspect an audit trail. These security, privacy, and performance claims come from Meta and should be independently tested with low-risk tasks before broader delegation.
GitHub adds enterprise controls for Copilot agent commands, files, and network access
GitHub released enterprise-managed permissions for Copilot agent operations on September 9. Administrators can centrally set shell commands, file reads and writes, and access to network domains to blocked, approval required, or allowed without a prompt. User preferences, workspace settings, automatic approval, and earlier approvals cannot make the enterprise policy less restrictive. GitHub says the controls are generally available in the Copilot app, Copilot CLI, and Visual Studio Code sessions that use Agent Host for Copilot Business and Enterprise customers. Security and platform teams should begin with a minimum-permission baseline, test representative repositories, and expand only the operations that have a clear owner, audit trail, and rollback path.
NVIDIA expands AI for Media across verification, replay, and live localization
NVIDIA announced a major expansion of AI for Media on September 9 ahead of IBC 2026. The stack combines SDKs, NIM microservices, playbooks, and blueprints for synthetic-video detection, 3D body pose, generative frame interpolation, video super resolution, lip synchronization, and active-speaker detection. NVIDIA reports that its Synthetic Video Detector reaches 99.3 percent accuracy on text-to-video material and 97.7 percent on image-to-video material, with integrations from Dalet, TwelveLabs, and Wowza. These are vendor-reported results rather than independent guarantees. Broadcasters should treat the detector as one signal, preserve provenance and metadata, test latency and false positives on their own feeds, and keep editorial accountability with people.
Apple brings Intelligence to Health with readiness, long-term insights, and on-device movement checks
Apple announced new health and fitness capabilities on September 9. Apple Watch Series 12 and Ultra 4 measure heart rate every five seconds and heart-rate variability as often as every five minutes, while a readiness score from zero to ten updates as new activity and vital data arrive. A redesigned Health app, due later this year and starting in U.S. English, uses Apple Intelligence for daily Insights, longer-term Longevity analysis, and Health Age. Camera-based movement assessments can evaluate flexibility, strength, balance, movement mechanics, and estimated VO2 max with an iPhone and Apple Watch. Apple says this processing happens on device and no assessment video is recorded, stored, or shared. Availability varies, and wellness features should not be treated as medical diagnosis.
An AI agent system-card checklist for purpose, components, evaluation, monitoring, and ownership
The UK Ministry of Defence Digital AI Practitioner's Handbook says a system card should be created when AI models are selected or shortlisted, updated throughout the system lifecycle, and kept with earlier versions to preserve an audit trail. Its guidance calls for a system overview and responsible roles, technical details about models and hosting, intended use and users, operating and training requirements, monitoring plans, and supporting documentation. This article adapts that Defence guidance into a general release evidence card for AI agents, adding prompts, tools, permissions, evaluations, known limits, and recovery paths. Those additions are an ENHE AI engineering interpretation, not a claim that the UK guidance creates a legal requirement for other organizations or defines one universal agent schema.
