Deterministic layer

The division of labour is the whole architecture: the model proposes, the rules dispose. Prices come from the price list rather than from the reply. Eligibility is evaluated by a function against the record. Anything the business would be held to is computed, and the model's role is to phrase what the computation returned.

This is what makes the probabilistic part safe to use, and it is this practice's stated invariant for the work: a probabilistic component is only safe inside a deterministic boundary. The boundary is not a filter reading the output for bad words — it is the layer that owns the facts, so the output has no opportunity to disagree with them.

It also fixes the failure that appears in production rather than in testing. A model that is right ninety-nine times in a hundred is wrong once, at scale, in a way nobody sees, on a claim somebody acts on. A rule is right every time on the cases it covers, and the cases it does not cover are enumerable — which is a different kind of risk, and the manageable one.

Putting the guardrail after the answer instead of before it

A filter that inspects the generated reply is checking a finished claim against patterns, and it will pass a confidently wrong price that happens to look like a price. The rules belong upstream, owning the values the answer is built from. If your system can produce a number the price list has never contained, the boundary is in the wrong place.

A definition sits still. This does not.

The term is a reading taken at a point in a sequence that is already running. These are the sequences, with the place each of them jams.

From a customer’s question to an answer the business can stand behind

One question arriving at an automated agent, and everything that has to hold for the reply to be something the company would have said itself. 7 steps, buying the model and treating the material as content work is the arrangement that fails while looking reasonable.

Somebody will quote this number at you.

Knowing the definition is not the same as being able to check the figure. These are the procedures that do the second thing.

Accepting an automated agent

“The agent is trained on your data and ready to go live.” · 45 minutes, 6 questions.

Somebody is accountable for this number.

A definition is free. Being answerable for the figure it produces is the part that is bought, and this term is a working part of the engagements below.

Custom software development and AI engineering for Dubai

A probabilistic component is only safe inside a deterministic boundary.

---

The reply that arrives tonight

An agent that will not say "I do not know" is not a sales asset. It is a liability with a fast response time.

Hallucination

A fluent, confident claim with nothing behind it — and the reason it is dangerous is that it is indistinguishable from a correct answer at the moment it is read.

---

Grounding

Every sentence the system produces is traceable to a passage it retrieved — which means an answer can be checked without asking the model to explain itself.

---

Refusal path

The route the system takes when it has nothing — designed, tested, and the single most valuable thing in a deployment.

---

RAG

Look the answer up first, then have the model phrase it — an architecture that turns a question about the model into a question about your material.

All ninety-six termsWhat this is regulated by in the UAE

Is this one right in your own numbers?

The definitions are the easy part. Whether the figure on your dashboard was computed this way is a different question, and usually the more expensive one.