Urgent.News

What's breaking now, across thousands of outlets.

AI

The Navier–Stokes Problem Has Survived for a Century. Did AI Find Something New?

Imagine dropping a small stone into a perfectly calm lake. You see the ripples moving outward. It looks simple. Now imagine trying to predict the exact position of every ripple, every tiny swirl, every change in speed, and every interaction between those ripples several minutes later. Suddenly, it doesn't look so simple. Now make the problem even harder. Instead of a calm lake, imagine ocean…

The Navier–Stokes equations, developed in the 19th century by mathematicians Claude-Louis Navier and George Gabriel Stokes, are a set of mathematical descriptions that account for various factors influencing fluid motion, such as velocity, pressure, viscosity, and external forces. These equations are fundamental to understanding the behavior of fluids in various scenarios, from ocean waves to aircraft turbulence.

Despite their widespread use in engineering and science, a fundamental question remained unanswered for over a century: if a fluid starts off smooth and well-behaved, will it always remain smooth, or could the mathematics eventually lead to something so extreme that the solution breaks down? This question became one of the famous Millennium Prize Problems.

In September 2026, OpenAI announced that one of its internal AI systems had supposedly produced a solution to this century-old problem. However, the significance of this claim lies not just in the fact that AI solved a 100-year-old problem, but in understanding the nature of the problem itself, the context in which it arose, the work that mathematicians have been doing towards a solution, and the challenges of verifying an AI-generated mathematical discovery.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

I Asked AI to Review My Code. It Found Bugs I Didn't See.

For a long time, I used AI in software development for one primary purpose: Write the code. Give it a requirement. Get some Python. Ask for a function. Get a function. Describe an API. Get an API.

  • AI reviewed author's code as senior software engineer
  • Identified potential bugs, edge cases, security concerns
  • Influenced author's coding process to anticipate problems

Agent Oversight Needs Metrics, Not Just Logs

Anthropic has published a snapshot of how it measures three parts of frontier AI development: the share of research led by AI, the oversight of internal agents, and the allocation of research compute.

Your AI Agent Has Too Many Permissions: A Practical Guide to Not Getting Burned

Somewhere right now , an AI agent has a standing API key with more access than the intern you'd never hand your prod credentials to.

  • AI agents often have excessive permissions beyond typical intern credentials.
  • Traditional security models don't account for the decision-making nature of AI agents.
  • Implementing short-lived, scoped tokens and human oversight can mitigate risks.

More from Friday 18 September →