Something is happening to the word physics.
Over the last few years it has become the preferred adjective for artificial intelligence. We now have physics-informed AI, physics-based models, physics-aware systems, products named PhysicsAI, MultiphysicsAI, and—more recently—the emergence of Physical AI.
Each of these terms represents legitimate work. Each solves a real problem.
But they do not describe the same thing.
That distinction matters because these terms increasingly guide how industries evaluate trust, capability, and risk. When every system claims to be "physics-enabled," the vocabulary itself begins to lose meaning.
After more than thirty years building automation systems for steel plants, I have learned that the difference is not academic.
It is the difference between software that helps engineers design a system and software that earns the right to participate in operating one.
This essay proposes a definition for a term that I believe fills that gap:
Physics-grounded AI.
Physics as Teacher
Most of today's commercial physics-AI exists in the world of engineering design.
Finite element analysis.
Computational fluid dynamics.
Thermal simulation.
Structural optimization.
Electromagnetic analysis.
Multiphysics simulation.
Physics-informed neural networks constrain learning using governing equations.
Physics-based surrogate models learn from thousands of simulations to replace expensive numerical solvers.
The physics teaches the model.
That work has transformed engineering.
A simulation that once required days can now be approximated in seconds.
An engineer who previously evaluated fifty design alternatives can now evaluate fifty thousand.
That is genuine progress.
Yet this entire ecosystem shares one fundamental assumption that is rarely stated explicitly:
Mistakes are cheap by construction.
If a prediction is wrong, another simulation can be run.
If one design fails, another design can be evaluated.
The value proposition of "1000× faster" depends entirely on the ability to iterate.
Design is a world where learning happens through repetition.
The World Beyond Simulation
Every design eventually leaves the workstation.
It becomes a steel caster running at three in the morning.
A ladle suspended beneath an overhead crane.
A blast furnace approaching the end of a blow.
An aircraft on final approach.
A launch vehicle climbing through maximum dynamic pressure.
A glacial lake behind a weakening moraine.
In this world, physics is no longer simulated.
It is happening.
Once.
There is no second attempt.
There is no restart button.
There is no opportunity to rerun the previous hour of casting or replay yesterday's flood.
Consequences are paid in the oldest currencies industry has always understood:
People.
Material.
Machines.
Time.
This is the world that has historically kept AI at the door.
Not because the models lacked intelligence.
Because they could not answer the question every mission-critical operation eventually asks:
How do you know?
And do you know when you don't?
What Existing Terms Do Not Capture
Physics-informed AI explains how a model learned.
Physics-based AI explains where the data came from.
Physical AI explains that intelligence has a body capable of perception and action.
All of these are useful descriptions.
None of them describes the relationship between a deployed AI system and the physical installation it serves.
That relationship is fundamentally different from training.
It continues throughout the lifetime of the asset.
It changes as the installation changes.
It determines whether predictions deserve trust.
That relationship is what I call grounding.
A Definition
Physics-grounded AI is a system whose every output is anchored to, and bounded by, the verified physical state of one specific real installation—and which knows, quantifies, and declares the limits of its own knowledge.
This definition intentionally says nothing about neural networks.
Nothing about transformers.
Nothing about architectures.
Nothing about GPUs.
Grounding is not a model architecture.
It is not a training strategy.
It is not a software framework.
It is a contract between an AI system and physical reality.
Five Tests
A definition is useful only if it excludes.
A system is physics-grounded if—and only if—it satisfies all five of the following conditions.
1. Grounded to an Instance, Not a Class
General physics provides a starting point.
Grounding begins only after the system has reconciled itself with one specific installation.
Not a blast furnace.
This blast furnace.
Not a caster.
This caster.
Not an airport.
This airport.
Real assets age.
Sensors drift.
Equipment wears.
Operations evolve.
Grounding must evolve with them.
2. Continuous in Time
Failures rarely appear suddenly.
They accumulate.
Small physical changes propagate across hours, weeks, seasons, or years before revealing themselves in minutes.
Human organizations rotate through shifts.
Physical state does not.
A grounded system continuously carries forward the physical condition of the installation because physical state is the only memory that never leaves when the shift changes.
3. Uncertainty Quantified Against Physics
Many AI systems report confidence.
Often that confidence reflects how familiar the current input appears relative to training data.
That is useful.
It is also incomplete.
Mission-critical decisions require uncertainty measured against verified physical state.
Confidence should describe the world—not merely the model's memory of the past.
4. The Right to Remain Silent
Every grounded system must possess an explicit abstention contract.
It must know when available evidence is insufficient.
It must refuse to answer rather than fabricate certainty.
In simulation, an incorrect prediction usually costs another iteration.
In operations, confident ignorance is often the most dangerous output an AI system can produce.
5. Glass-Box Legibility
People remain accountable.
Therefore people must understand.
Grounded systems expose the physical mechanisms supporting their conclusions in the language of the discipline they serve.
Operators do not require fashionable explainability.
They require engineering reasoning.
Physics as Companion
The distinction between design and operations can be summarized simply.
In engineering design, physics is the teacher.
It trains the model.
In mission-critical operations, physics must become the companion.
It accompanies every decision.
Every update.
Every recommendation.
For the lifetime of the installation.
That continuous companionship—not merely physics during training—is what separates grounded systems from conventional AI.
A Property That Can Be Measured
Claims alone are insufficient.
If grounding is real, it should be measurable.
That is the motivation behind PhysicsIQ.
Rather than asking whether a system uses physics, PhysicsIQ asks how faithfully its outputs remain bounded by verified physical reality.
Grounding should not be judged by marketing language.
It should be evaluated through observable properties:
- Instance grounding
- Temporal continuity
- Physics-based uncertainty
- Abstention behaviour
- Glass-box legibility
A claim that cannot be measured eventually becomes marketing.
A property that can be measured becomes engineering.
Why Define It Publicly
Industries evolve by refining language.
New categories become useful only when they have clear definitions, practical tests, and measurable properties.
Physics-grounded AI is offered in that spirit.
Not as branding.
Not as a replacement for physics-informed learning, surrogate modelling, or physical AI.
Those fields remain valuable.
They solve different problems.
Physics-grounded AI begins where they end—at the moment software becomes responsible for decisions in the physical world.
The operating floor has always asked the same question before trusting a new technology:
How do you know?
And do you know when you don't?
Physics-grounded AI is an attempt to answer that question with engineering rather than confidence.
Because when physics is no longer being simulated—but is unfolding in real time—trust is no longer a feature.
It becomes the system itself.
Originally published on LinkedIn.