IOanyT Innovations

Lesson 2 of 10 · 7 min read

Deterministic AI, defined

In one paragraph

"Deterministic AI" describes AI-built systems whose production behaviour is deterministic: the same input always produces the same output, because the decision path runs as fixed, reviewed logic rather than a fresh model generation on every request.

In this lesson

  • Define deterministic AI in one sentence
  • Name four things deterministic AI is not
  • Use the core vocabulary of the course: decision path, build time, run time, deterministic execution

The video version of this lesson is in production. The full lesson is below.

The last lesson ended with a problem: language models can give different answers to the same question, and a business owns every one of them. This lesson gives the problem’s opposite a name.

The definition, unpacked

“Deterministic AI” describes AI-built systems whose production behaviour is deterministic: the same input always produces the same output, because the decision path runs as fixed, reviewed logic rather than a fresh model generation on every request.

Three parts of that sentence do the work.

“AI-built systems.” AI is in the picture. In this approach, language models do a lot of the engineering: they read policies and documents, draft logic, and generate the tests that check it.

“The same input always produces the same output.” Ask the system the same question tomorrow, or a thousand times, and the answer doesn’t change. That is what makes it testable, supportable and auditable.

“The decision path runs as fixed, reviewed logic.” The decision path is the part of a system that decides what a customer is told or what happens to their case: approve or decline, the price, the refund, the next step. In a deterministic system, that path is code a person has reviewed and versioned, not something a model improvises on each request.

What deterministic AI is not

The term is easy to misread, so it’s worth being explicit.

  1. It’s not “no AI.” Models still do much of the work. They just do it before release, under review.
  2. It’s not temperature 0. Turning a model’s randomness down reduces variation, but production systems can still drift (batching, model updates, context changes). A setting is not a guarantee.
  3. It’s not error-free. Deterministic logic can still be wrong. The difference is that a mistake is repeatable: it shows up the same way every time, so it can be found, fixed and covered by a test.
  4. It’s not a product you buy. It’s a property of how a system is built. Anyone who claims it should be able to show it.

Where the AI goes instead

If the model isn’t making the decision at run time, where is it? Mostly at build time: the phase when software is designed, written and tested. Run time is when it serves real customers. The approach of using models at build time and deterministic code at run time is called compiled AI, and it’s the subject of lesson 3.

Models can also have bounded roles at run time. For example, a model can read a messy document and fill a strict form, which code then checks, with a person taking over when something doesn’t fit. How much of that is appropriate is a judgement this course gives you a framework for in lesson 4.

Deterministic, generative, agentic

You’ll hear three words used loosely. Here is how this course uses them:

TermGood atCan go wrongBelongs
GenerativeDrafting, summarising, conversationDifferent answers to the same questionWhere a person reviews the output
AgenticMulti-step tasks across toolsErrors compound, and actions are taken on themReversible, low-value tasks with hard limits
DeterministicDecisions that must repeat and be explainedMisses cases nobody anticipatedAnywhere customers, auditors or regulators rely on the answer

Most real systems mix all three. The skill is putting each where it belongs.

The vocabulary for the rest of the course

These terms come up in every lesson. Each one is defined in the glossary.

  • Run-to-run variance: different outputs for the same input (lesson 1).
  • Decision path: the part of a system that decides outcomes.
  • Deterministic execution: running that path as fixed, reviewed, versioned code.
  • Build time / run time: when software is made versus when it serves users.
  • Golden dataset: real examples with answers your team agrees are correct, used to measure accuracy (lesson 5).

Try it yourself: the one-question test

Take any AI-assisted workflow in your organisation and ask:

“If we ran this decision again tomorrow with exactly the same input, would we get the same result, and could we show why?”

If the answer to either half is “no” or “not sure”, the decision path isn’t deterministic yet. That isn’t automatically a problem. It is a choice your team should be making deliberately rather than by default.

What comes next

Lesson 3 shows how teams get deterministic behaviour without giving up AI: using language models to write the logic, then running the logic, not the model.

Deterministic AI is about the decision path Not about banning models, and not about pretending a model is predictable. IT IS: Repeatable, Traceable, AI-built. IT IS NOT: No AI at all, Temperature 0, Error-proof. Both meet at: Answers you can defend. IOANYT ACADEMY / LESSON 2 Deterministic AI is about the decision path Not about banning models, and not about pretending a model is predictable. IT IS Repeatable same input, same output Traceable every result to a line of code AI-built models write and test the logic IT IS NOT No AI at all models still do the engineering Temperature 0 a setting is not a guarantee Error-proof mistakes surface before release Answers you can defend TO CUSTOMERS AND AUDITORS models stay where they have proven consistent

Key takeaways

  • Deterministic AI is about the decision path: the part of a system that decides what a customer is told or what happens to their case.
  • It doesn't mean no AI. Models still do much of the engineering; they just don't improvise the decision every time.
  • Temperature 0 is a setting, not a guarantee. Determinism comes from how the system is built.
  • Deterministic doesn't mean error-free. It means mistakes are repeatable, so they can be found, fixed and tested before release.

Check yourself

Pick an answer, then open the card to compare.

  1. 1. Which statement best describes deterministic AI?

    • A.An AI system that uses no language models
    • B.An AI-built system whose decision path gives the same output for the same input
    • C.A language model running at temperature 0
    Show the answer

    B. An AI-built system whose decision path gives the same output for the same input The definition is about production behaviour on the decision path. Models can still be used to build the system.

  2. 2. A team says their chatbot is deterministic because they set temperature to 0. What's the problem?

    • A.Nothing; that makes it deterministic
    • B.Temperature 0 reduces variation but doesn't guarantee identical outputs in production
    • C.Temperature 0 makes answers less accurate
    Show the answer

    B. Temperature 0 reduces variation but doesn't guarantee identical outputs in production Batching, model updates and context changes can still shift outputs. Determinism comes from fixed logic in the decision path.

  3. 3. What is a decision path?

    • A.The steps a user clicks through in an app
    • B.The part of a system that decides what a customer is told or what happens to their case
    • C.The training data of a model
    Show the answer

    B. The part of a system that decides what a customer is told or what happens to their case Deterministic AI focuses on the part of the system where consistency matters most: the decision.

Common questions

Is deterministic AI a product I can buy?

No. It's a property of how a system is built: whether its decision path runs as fixed, reviewed logic. Any vendor that claims it has to show it, for example by running the same inputs many times and getting identical outputs.

If the logic is fixed, how does the system improve?

Through new versions. When rules or data change, the logic is updated, re-tested and released, like any software change. You always know which version made which decision.

Where do language models still fit?

At build time, writing code, extracting rules and generating tests, and in bounded roles at run time, such as reading an unstructured document into a strict format that code then checks. Lesson 4 covers how much model belongs where.

How is this different from traditional rules engines?

The output can look similar: explicit, testable logic. The difference is how it is built. Language models do much of the drafting and testing, which makes the logic faster to create and easier to update.