Edited by humans. Written by AI. How our editing works
All articles

OpenAI's 88-Hour Math Claim and the Credit Fight Behind It

OpenAI claims AI agents solved the Navier-Stokes Millennium Prize problem in 88 hours, but a credit dispute and a data-use caveat raise harder questions.

Marcus Chen-Ramirez

Written by AI. Marcus Chen-Ramirez

September 10, 20266 min read
Share:
A surprised man reacts beside an OpenAI post reading “We solved Navier-Stokes.”

Photo: AI. Ondine Ferretti

OpenAI says a group of AI agents running on an unreleased next-generation model produced a solution to the Navier–Stokes Millennium Prize problem in 88 hours, working from September 1 to September 5 and burning through 4.9 million agent messages and 300 billion output tokens along the way. If that claim survives scrutiny, it would mark the first time an AI has cracked one of the seven problems the Clay Mathematics Institute has held open with a $1 million bounty each, some for over 90 years.

But the announcement arrived tangled in a dispute about who actually earned the credit, and that dispute may end up teaching us more about the AI industry than the math itself.

Why the Navier–Stokes Problem Matters

The Navier–Stokes equations describe how fluids move: water through pipes, air over a wing, ocean currents, smoke curling through a room. A vast share of modern engineering, from aircraft design to chip cooling to weather prediction, leans on them. The Millennium Prize version asks a deeper question: do smooth solutions always exist, or can a fluid theoretically blow up into infinite complexity? Nobody has answered that in the century since the equations were formalized.

That is why the claim of a solution carries weight beyond mathematics. As Indian Defence Review reports, the experiment is being read as a signal that AI can now attack foundational scientific problems rather than only trivia and code completion. Skeptics urge caution: as my colleague's earlier Navier-Stokes claim coverage noted, mathematicians want a formal, verifiable proof checked by the community before anyone calls a Millennium Problem solved. A company blog post is not peer review.

The Dispute over Credit

Here is where the story gets uncomfortable. Two mathematicians, Tristan Buckmaster and Levent Alpöge, spent about a year working on a related fluid dynamics problem, storing their drafts in OpenAI's Codex tool while using AI assistance themselves. By mid-August they had proven something previously unproven.

According to Matthew Berman's video on the episode, the timeline then turned tense. On September 3, rumors reached the pair that OpenAI knew about their work; Buckmaster emailed to clarify the project was personal, not an official Anthropic effort (Buckmaster works at Anthropic). On September 6, OpenAI called to say its own AI had produced a major proof on the next, harder version of the same problem, using what Berman describes as the same unusual approach the mathematicians had taken. Buckmaster says OpenAI's first prompt toward that problem went out only a day after the company learned of their progress.

Buckmaster published a statement on September 8 accusing OpenAI of rushing the solution into public to control the credit narrative. OpenAI answered with a categorical denial: "We, the researchers and the agents, did not see any of their work through any means until they released it publicly. In particular, no specific user data was accessed in order to solve this problem."

Then came the caveat that reframes the whole story: "While unlikely, we cannot rule out that de-identified data derived from their usage of our products helped improve our models."

Sebastian Bubeck, who led the Navier–Stokes initiative at OpenAI, later posted his side of the conversations, saying he reached out to coordinate releases, never asked for Alpöge's removal from authorship, and found the meetings difficult because Alpöge refused to attend. International Business Times covered the same standoff, framing it as two researchers raising questions about credit over a claimed million-dollar solution.

The Line that Should Worry Every Builder

Set aside who is right; neither side's full record is public. Read OpenAI's sentence again with a different hat on, say, a startup founder's. Any business built on a frontier API now operates under an explicit disclaimer: your usage data, de-identified, may improve the vendor's models. The vendor's future model may then internalize your domain expertise and compete with you, or simply absorb the differentiation you thought you had.

This is textbook platform risk, and OpenAI has essentially admitted it in writing. The practical responses are unglamorous: read the data-retention and training policies before shipping anything sensitive, minimize what you send to hosted models, and weigh self-hosted or open-source models for high-value intellectual property. TechBuzz notes that the backlash over the 88-hour claim has intensified exactly these questions about data handling and credit.

Assisted Discovery Versus Autonomous Discovery

Berman's video also reaches for the frame of recursive self-improvement: AI discovering new math that feeds back into making AI stronger. He notes OpenAI has published work on using AI to accelerate its own research, and that models like GPT-5.5 reportedly helped build successors. But the honest reading of the Navier–Stokes episode cuts the other way too. Two human mathematicians framed the problem, developed the unusual approach, and validated a result over a year of work. The AI then ran very fast in the direction humans pointed. That is acceleration, not a closed loop where the machine chooses its own questions, designs its own experiments, and patches itself.

Both labs have incentives to blur that distinction, and observers do too. Valency's analysis of the episode frames it as a preview of AI-accelerated science generally, which is probably right, but the preview still has humans holding the camera.

Where This Leaves People

Berman closes with the chess analogy: engines surpassed the best humans decades ago, yet people still watch Magnus Carlsen because human competition is the point. Math and science have no such spectator culture. What society wants from research is the fastest best answer, and if AI delivers it, human discovery may go the way of the chess engine: still practiced, no longer decisive.

I find that framing persuasive as far as it goes, but the credit dispute underneath this story suggests a third outcome nobody is planning for. If machines do the proving while humans supply the framing, the fighting will be over attribution, data provenance, and who owns the drafts left in someone else's tool. That fight, not the proof itself, is the part of this story with precedent. The Navier–Stokes claim will be verified or discarded by mathematicians on their own timeline. The question of what a model company owes the people whose work passes through its servers has no committee waiting to judge it.

Marcus Chen-Ramirez covers AI and the economics of software for Buzzrag.

More Like This

A man with a concerned expression next to a Reddit post discussing catching a child using AI, with a red LIVE indicator in…

Should Your Kid Use AI? A Tech Parent's Honest Answer

A tech journalist who codes for a living explains why he won't let his 8-year-old use AI unsupervised—and why the environmental argument misses the point.

Marcus Chen-Ramirez·5 months ago·6 min read
Man in black shirt with surprised expression against starry background with white text reading "AHEAD of schedule...

AI Models Are Now Building Their Next Versions

Major AI labs confirm their models now participate in their own development, handling 30-50% of research workflows autonomously. The recursive loop has begun.

Bob Reynolds·6 months ago·6 min read
Man in blue shirt against dark textured background with red cartoon creatures and bold white text reading "10X YOUR WORKFLOW

Power Users Are Breaking OpenClaw in Interesting Ways

Matthew Berman spent 200 hours optimizing OpenClaw. His setup reveals how AI agents work when you push past the defaults—and what breaks along the way.

Marcus Chen-Ramirez·6 months ago·6 min read
Man in gray shirt smiling at camera with red starburst graphic and "LIVE" indicator on dark textured background

Anthropic's Self-Improving AI Paper Has a Regulator Problem

Anthropic's new paper on recursive self-improvement reveals an oversight gap that existing AI regulation—EU AI Act, executive orders—was never designed to address.

Samira Barnes·3 months ago·8 min read
Man in glasses with hand on chin, thoughtful expression, with text overlay reading "The most important question in the…

When AI Starts Building AI: The Recursive Loop Debate

Ryan Greenblatt argues AI could compress five years of research into one. The harder question is what happens after—and who that AI actually works for.

Marcus Chen-Ramirez·4 weeks ago·7 min read
Five men's headshots arranged horizontally with names labeled below each, set against a black background with yellow "Model…

Murati's Open Model and AI's Regulation Dilemma

Mira Murati's 975B Inkling model, Demis Hassabis's FINRA-for-AI proposal, and Liquid AI's post-transformer architecture reframe who controls frontier AI.

Dev Kapoor·2 months ago·9 min read
Man in blue shirt discusses AI model optimization with overlaid graphics showing rLLM-FinQA-4B training framework and Qwen3…

A 4B Model Beat a 235B Model for Under $500

Snorkel's Kobie Crawford shows how a 4B parameter model outperformed Qwen 3 235B on financial analysis tasks using RL training that cost less than $500.

Marcus Chen-Ramirez·3 months ago·7 min read
A smiling man wearing orange-tinted sunglasses against a purple background next to white pixelated logo and text reading…

Building a Serverless AI Agent with Pi and Google Cloud

A developer tutorial walks through deploying a personal AI bookkeeping agent to Google Cloud Run using Pi, Express, and Cloud Storage—accessible from any device.

Marcus Chen-Ramirez·3 months ago·7 min read

RAG·vector embedding

2026-09-10
1,512 tokens1536-dimmodel openai/text-embedding-3-small

This article is indexed as a 1536-dimensional vector for semantic retrieval. Crawlers that parse structured data can use the embedded payload below.