Start a project
Engineering notes · 4 min read

Why we compute before we generate

How a governed AI system keeps its numbers honest: deterministic maths first, then the model explains the result.

Code snippets on a screen
Shashidhar Sharma
DigiConduit engineeringLed by Shashidhar Sharma, Head of DigiConduit, and Anand Thakur, Chief Technology Officer

Ask a general AI model for last week's cost per acquisition and it will give you a number. It will be written with confidence. It may also be wrong, because the model never saw the data. It saw a question and produced the most likely-sounding answer. This is the single biggest reason businesses stop trusting AI on their reports.

Our answer to this problem is a rule we apply to every system we build: governed before generative. The numbers are computed first, in a deterministic layer, before any AI is involved. Only then does a model get to explain them.

What governed means in practice

Governed means the KPI (key performance indicator) maths, the deltas and the thresholds all run in code and in the warehouse. A pacing figure is plan versus delivered, day by day. A deterioration flag is a percentage above target for a set number of days. These are arithmetic, not opinions. They produce the same answer every time.

The AI never touches these figures. It receives them, already computed, along with a small amount of context. Its job is to phrase the result in plain English, suggest a likely cause from the patterns it was given, and recommend what to do next. If the language layer is unavailable, deterministic templates take over and the report still goes out.

Retrieval over prompt-dumping

The second rule follows from the first. We do not pour a whole dataset into a prompt and hope the model finds the right rows. We retrieve only the relevant, compressed slice. This keeps answers accurate, keeps costs predictable and keeps the system fast. It also means the context the model saw can be logged and reviewed later.

Structured outputs over rambling answers

Every answer our systems return has the same shape: insight, likely cause, recommendation, immediate action, and a confidence score out of 10. A fixed shape makes an answer easy to check, easy to route to the right person, and easy to compare with last week's answer. It also stops the model from wandering. When it is not sure, the score says so.

Why this matters commercially

Context-budget management, caching, response templates, output-length controls and full prompt and response logging are not extras. They are what keep an AI system affordable at scale and auditable when a leader asks why the system said what it said. A system that cannot answer that question will not survive its first difficult quarter.

This is the way OneView™ is built, and it is the way we build every insight layer, automation and assistant for the businesses we work with. Compute first. Then explain.

Why we compute before we generate
Abbreviations on this pageAI artificial intelligenceKPI key performance indicator
Start a project