An analyst in a trucking control tower built their dashboards with AI, and they still recheck every one of them in Python. In an r/ChatGPT thread from 2 November 2026 they explained why: if their bosses find a single inconsistency in the data, the analyst is the one in trouble. The top reply had 19 votes. It said, in short: stop asking the model to do the math, and ask it to write the code that does the math.
That is one thread from one person. It is not a measured trend. We think it gets the design decision right anyway.
The answer
In our view, users don't distrust AI analysis because the model is dumb. They distrust it because the model is doing the arithmetic, and nothing on the screen says where a number came from.
So split the job. Code computes every figure. The model only explains figures it was given. Each number keeps a pointer to the query that produced it. When the data has no answer, the report says "not found" and leaves the gap empty.
Thin input → a decision-grade read → the call stays with the person. The person can only make that call if every number in the read can be traced.
Why checking can't be the reader's job
One invented figure can end the product. In an r/AI_Agents thread from 23 September 2026, a user cancelled an AI summarizer the same day they found a date in a client document that nobody had ever mentioned. By their own account, two things would have kept them: every statement linked to its source or marked "not discussed", and a check by a separate pass that had not written the draft.
Most readers don't check. In an F-Secure survey from September 2026, 70.1% of respondents said they check AI answers rarely or never, and 47.3% said they stop doubting an answer once it sounds fluent.
Taken together, our reading is this: most readers who could catch the error never look, and the reader who does look leaves. Verification has to be built into the system. You can't count on the reader's habits.
How RE Intelligence does it
RE Intelligence works on Dubai's DLD registry: millions of raw transaction records in inconsistent formats, with Arabic names, duplicate areas and garbage rows. From that record it writes its own monthly and quarterly market reports. The product's rule is "Postgres owns the truth. AI owns the story." Every number comes from a deterministic query. The model narrates what the data has already proved.
The September 2026 report, dated 1 October, opens with: "Dubai real estate transacted value collapsed 70% year-on-year to AED 10.84 billion." The model did not compute the 70% or the 10.84 billion. A query did, and the model wrote the sentence around them.
Here is the pattern, simplified. It is an illustration, not our production code.
Step 1: code computes. The query is deterministic, versioned and can be re-run.
select
period,
sum(amount_aed) as transacted_value,
sum(amount_aed)
/ lag(sum(amount_aed), 12) over (order by period) - 1 as yoy_change
from transactions_monthly
group by period;
Step 2: the result becomes a fact sheet, and every value keeps its provenance.
facts = [
{"id": "f1", "label": "transacted_value", "value": 10.84e9,
"unit": "AED", "period": "2026-09", "query": "monthly_value"},
{"id": "f2", "label": "yoy_change", "value": -0.70,
"period": "2026-09", "query": "monthly_value"},
]
Step 3: the model gets the fact sheet, never the raw table.
You write the market summary.
- Use only numbers from FACTS. Cite each one as [f1], [f2].
- Do not add numbers, derive new ones, or round differently.
- If the outline asks for something FACTS does not hold, write "not found".
Step 4: a separate pass checks the draft against the facts, in code.
for number, ref in cited_numbers(draft):
fact = facts_by_id.get(ref)
if fact is None or not matches(number, fact):
reject(draft, f"{number} [{ref}] has no matching fact")
for number in uncited_numbers(draft):
reject(draft, f"{number} has no source")
In our experience, step 4 is the one teams skip. It is also the step that makes the r/AI_Agents user's two conditions mechanical: a number either matches a cited fact or it never ships.
The same rule shapes the rest of the product. The page-aware assistant can only run read-only queries. The product never presents an AI-generated number as fact without a deterministic query behind it. It never quietly "corrects" source data. Its forecasts are archived, graded against what actually happened, and the accuracy is shown to the user.
What it costs
The design has trade-offs, so here they are.
- Every answer needs a query someone wrote. The model can't make up a new metric when a user asks for one. A missing query shows up as "not found", and that looks worse in a demo than a confident wrong number.
- The prose is plainer. A model limited to a fact sheet writes less colorful copy. We accept that.
- The work moves into the data layer. RE Intelligence runs on 100+ custom database functions and pre-aggregated snapshot tables. The narration is the small part.
- Ugly source data stays visible. Since the registry is never silently cleaned up, a messy source looks messy. We think that is the honest result.
Four checks for your own report feature
1. Point at any number on screen. Can you open the query that produced it?
2. Change one input row. Does the summary change with it, or does the model
still "know" the old number?
3. Ask for a figure the data does not hold. Do you get "not found",
or a plausible number?
4. Who checks the draft? If the answer is "the same model" or "the reader",
nobody does.
A product that fails check 3 will eventually produce a date nobody mentioned.
What would change our mind: a model whose arithmetic, inside a long narrative, readers could verify faster than they could open a query. We haven't seen one yet.
FAQ
Can't a stronger model simply do the math correctly?
It may make fewer mistakes. In our view the error rate isn't the real problem, though. The problem is that a reader can't tell which number is wrong without redoing the work. You can re-run a query. You can only trust a model's arithmetic.
Doesn't the model end up writing the SQL anyway?
It can help a developer write it. What matters is when the query gets written: it is written, reviewed and versioned before the report runs, never improvised inside an answer. In RE Intelligence, even the assistant is limited to read-only queries.
Is it enough to have a second model review the first?
A second model is a common suggestion. For numbers, we'd rather check in code. Matching a cited figure to a fact sheet is a deterministic test, and a second model only adds another opinion. Use the model reviewer for tone and for claims that aren't numbers.
What about forecasts? They aren't facts yet.
That is why they are treated differently. RE Intelligence archives each forecast, grades it against what actually happened, and shows that accuracy to the user, so trust in a forecast is earned in public.
Related case
RE Intelligence turns Dubai's public but hard-to-use property registry into monthly and quarterly market reports, a news feed and ready-made charts, with every number backed by a query. You can read the case at iloblique.com/re-intelligence and try the product at reint.ae.
If you have something worth building, we'd like to hear about it.
Sources
- r/ChatGPT, "I Can't Trust AI Work", 2 November 2026: thread
- r/AI_Agents, thread on cancelling an AI summarizer, 23 September 2026
- F-Secure, survey on checking AI answers, September 2026
- RE Intelligence, "Dubai Real Estate Market Report: September 2026", dated 1 October 2026 (behind the product login; public site reint.ae)
Originally published at iloblique.com.?utm_source=devto&utm_medium=social&utm_campaign=devto_article_v1&utm_content=c1d39fa0
Top comments (0)