FLOW: A Beautiful Vortex Is Only the Beginning

The first thing a vortex asks of you is attention. A bright curve turns inward, a narrow region seems to accelerate, and the eye supplies the rest: depth, force, inevitability. Before a single quantity has been named, the picture already feels explanatory.

FLOW starts at that moment. The aim is to turn the impulse to watch into a habit of asking: what is moving, what is being colored, and what would count as a fair test?

A picture needs a question

An image can be faithful to its data and still invite the wrong conclusion. A bright patch might encode concentration, speed, local rotation or merely a lighting choice. The same geometry can be used for all four. Without a legend, the viewer has to invent a measurement.

That is why the useful first question is smaller than “is this realistic?” Ask which quantity each visible mark represents. Then ask whether the picture is a snapshot, a particle history, a numerical experiment or an illustration of an argument. Those are different objects, even when they share a visual language.

The three buttons are not a ladder from bad evidence to good evidence. A picture is excellent evidence for an appearance. A numerical run is useful evidence about a particular computation. A proof has a different job: establishing a conclusion under stated assumptions. Trouble begins when one object is asked to do another object's work.

The spark, and the separation

OpenAI’s Navier–Stokes announcement pairs a visual explanation with links to a reported proof and formalization. It was an inspiration for this project. OpenAI reports a three-dimensional result with smooth external forcing. FLOW does not reproduce or verify it.

The Clay Mathematics Institute announcement describes an evaluation process. The official problem statement is the place to read the assumptions. Treat those sources as sources, with dates and attribution, rather than converting an attractive image into a claim of mathematical acceptance. These links were checked on 31 October 2026.

FLOW asks a more accessible question. Can a small two-dimensional experiment help us distinguish an intervention from a change in presentation? It has velocity on a finite grid, a passive dye field and specified numerical methods. It also has error, boundaries and a finite duration. Those restrictions belong in the explanation, not in fine print after the conclusion.

The experiment inside the image

Imagine making two copies of the same fluid state. Keep their initial data and their clock identical. Change one parameter in the second copy. Then inspect the difference using the same field definition and the same display scale.

This is the central idea of FLOW. It turns “these pictures look different” into a question about what was held constant. It also creates a valuable failure condition: with identical parameters, the copies should continue identically on the tested implementation. If they do not, the comparison is already broken before it teaches any physics.

A second kind of failure is quieter. A simulation may continue producing beautiful pictures while slowly losing the tracer that makes it visible. Part 7 keeps such a failure in view. The appearance was persuasive; a mass measurement was less forgiving.

What you can open today

The public FLOW preview contains a fixed solver recording and its settings, explanations and export. It is not a live fluid laboratory. The live tools remain under scientific and device review. Selecting a guide does not produce a new recorded experiment.

That boundary does not make the recording useless. It gives you a stable object to read carefully. Find A and B. Read the viscosity labels. Find the matched time. Ask whether the colors mean what you first assumed.

A useful first result: you can learn to read a fluid image before learning to build a solver. You just need the image to tell you what it is.

Next: remove the ink, and ask what keeps moving.