A processor on a circuit board lit with cyan

The Determinism Gap

A system is either deterministic, or it isn’t.
There is no gray area.

Determinism is not a maturity level. No model earns it with enough parameters, enough training data, or enough compute. It is a property a system has or doesn’t. The probabilistic AI industry is asking regulators, boards, and courts to accept a guess as if it were a computed result.

The claim

A result is deterministic only if nothing between input and answer involved sampling from a probability distribution. A generative model samples, every time. That is the architecture, not an implementation detail.

Why scale doesn’t fix it

A larger model still samples. A better-trained model still samples. Scale changes how convincing the guess looks. It does not change that it is a guess. You cannot train a coin flip into a computed result.

Common Tricks

How some platforms fake it on paper.

None of these are theoretical. All three are being sold right now as “deterministic AI.” None of them are.

  • 01

    The Cached Answer

    Ask a question once, and the platform saves the answer. Ask the exact same question again, and it hands back the saved copy, calling that “the same input, the same output.” That is a photocopy of a guess, not a computed result. Change one word in the question and the illusion breaks immediately, because a new question has nothing saved to hand back.

  • 02

    The “Temperature Zero” Claim

    Setting a model’s randomness dial to zero reduces how much its answers vary. It does not remove the variation. The same input can still produce a different output after the model is updated, on different hardware, or simply because it ran alongside different requests in the same batch.

  • 03

    The “Trained to Be Consistent” Claim

    Training a model on a fixed set of examples, or distilling its behavior into rules, makes its answers look more alike more often. It does not make the model deterministic. A more convincing guess is still a guess.

The Six Properties

What a probabilistic system can never produce as its own monitor.

01

Reproducibility

Same question, same answer, every time, forever. Not usually. Not unless something changed. Every time.

02

Traceability

You can see exactly how it got the answer. Not just that it gave one.

03

Independence

The judge can’t be running on the same guesswork as the thing it’s judging. A probabilistic monitor watching a probabilistic system shares its blind spots exactly.

04

Self-Correction

It knows when it’s gotten worse, without a person telling it. A monitor with no fixed baseline has nothing to compare itself to.

05

Evidentiary Sufficiency

The proof holds up outside the company that made it. A log of what a model said is not a cryptographic proof of how it got there.

06

Composability

Stack two guessing machines and you get a bigger guess, not a fact. Uncertainty compounds. It does not cancel out.

The Regulatory Collision

The law is catching up to a distinction the industry has been blurring for years.

EU AI Act

Requires traceability of decisions. Traceability requires stored, reproducible evidence.

EU Machinery Regulation

Requires documentation that enables independent verification.

FAA AI Safety Assurance

Requires continuous, verifiable assurance evidence.

FDA 21 CFR Part 11

Requires records that are attributable, contemporaneous, and independently reproducible.

The monitored system can be probabilistic. The monitor cannot.

Ask Any Platform This

A checklist for any vendor claiming “deterministic.”

  1. 01

    Can you replay any historical result bit for bit and get the exact same answer?

    If replay ever produces a different answer, even once, it was never deterministic to begin with.

  2. 02

    Is that answer freshly computed right now, or is it a saved answer from the first time someone asked?

    A cached response to an old question is not a new computation. Ask something slightly different and find out.

  3. 03

    Does the same answer hold after the model is updated?

    Real determinism does not expire the next time the vendor retrains.

  4. 04

    Does the same answer hold on different hardware, or under a heavier server load?

    A result that depends on which machine ran it, or how busy the servers were, was never fixed to begin with.

  5. 05

    Is every result cryptographically chained back to its source data?

    Without this, there is no way to prove a result was not quietly edited after the fact.

  6. 06

    Can an independent third party verify the result without access to your model weights?

    If only the vendor can check their own work, that is not proof. It is a promise.

  7. 07

    Does the system report its own accuracy degradation, or does a person have to notice first?

    A system that cannot see itself slipping cannot be trusted to catch it in time.

  8. 08

    Is “deterministic” describing the final decision, or the generative step underneath it?

    Wrapping a coin flip in a rule does not change what produced the coin flip.

  9. 09

    If the randomness setting is at zero, does that hold true across the next five questions, not just the one you tested?

    One demo answer proves nothing about the next one.

Popcorn kernels sealed in a clear evidence bag on a dark surface

The Standing Challenge

We publish our own replay proof. We invite any platform claiming determinism to publish theirs.

Bring your evidence chain. We will bring ours.