Jekyll2026-10-07T04:28:21+00:00https://phvpavankumar.github.io/feed.xmlPavan Kumar PHVPavan Kumar PHV — applied AI, backend engineering and practical notes on building reliable systems.The number that meant two things2026-08-31T00:00:00+00:002026-08-31T00:00:00+00:00https://phvpavankumar.github.io/weekly/the-number-that-meant-two-things
tl;dr

What follows is a composite — a pattern I have seen play out more than once across enterprise programmes, not an account of any single company or project. If you work in finance, you will recognise it anyway.

It is Monday morning. A finance director opens the executive dashboard and looks at a cost number. Down the hall, a colleague pulls the same number from the source system. Same name on both screens. Different values. Not slightly different — different enough that one of them must be wrong.

Except neither is wrong.

The Monday morning, replayed

[01] // DIAGNOSIS

Two honest answers, one name

When someone finally traces it, the story is always some version of this: one screen shows the figure as it was actually posted in the books. The other shows an estimate, calculated a different way, from a different system, for what was once a perfectly good reason. Two honest answers to two different questions — wearing the same label.

And when you ask who decided which one is the official number, the answer is usually silence. Nobody decided. One version was built one day, the other already existed, and the two have quietly disagreed for months without anyone noticing.

0.0MPOSTED VARIANCE · FINANCE SOURCE SAME KPI 0.0MDERIVED ESTIMATE · DIFFERENT MODEL

[02] // AMPLIFICATION

Then you add AI

Here is the part that should worry anyone putting AI on top of company numbers. The AI does not notice the conflict either. Ask your question one way, and it serves the first definition. Ask another way, and it serves the second. Both answers arrive instantly, fluently, and with total confidence. Nothing in either answer tells you a rival number exists.

The machine has not lied. It has done something quieter and worse: it has taken a disagreement nobody had settled and delivered it at scale, in a confident voice, to everyone who asks.

Try it yourself

Same company, same quarter, one KPI. Ask the AI two ways. (Illustrative numbers.)

AI does not resolve an undecided definition. It industrialises it.

[03] // CORRECTION

The fix is embarrassingly small

Once the disagreement is found, fixing it usually takes a day or two: someone with authority picks the official version, and the screens are aligned. A day of fixing, after months of quiet confusion. That ratio repeats everywhere.

Which means the prevention is cheap, and none of it needs a model or a budget:

  • For every number an AI system can serve, write one sentence: how it is calculated, and from where. No sentence, no automation.
  • Where two calculations exist, a named person chooses one. An estimate is fine — as a decision, not as an accident.
  • Before launch, check every AI-served number against its source system. Before launch — not after a director does it for you on a Monday morning.

Pick one number on your own dashboard. Could you say, in a single sentence, exactly how it is calculated and from where — and would the team next door give the same sentence?

]]>