Zero Information Points: The Report That Looks Complete and Says Nothing

The file contained zero information points. The structure was intact — eight dimensions, a table under every dimension, every cell of every table filled in. The only problem was that the cells held no answers, only the words 'N/A — insufficient information'. No article title, no source, no author stance, article type logged as Unclassified, the entity list unresolved, time sensitivity never assessed. And at the very top, the field the whole framework rests on — Information Points — a completely empty array.

To a reader this is dull technical paperwork. To me it is one of the most useful files to land on the desk in nine years, because it is the thing every data desk should publish at least once and almost none does: a clean, structured null result. An empty payload is a finding, not an error. Telling those two apart is the entire job.

Start with what an information point is. It is a fact that can be counted, sourced and re-checked — for instance, that Mumbai won the tenth-season final by one run. Everything else — opinion, atmosphere, seniors are confident, the body language looked good — is not an information point. The desk rule has been the same since day one: every conclusion must state which information point it derives from. The day that rule breaks, analysis becomes commentary.

I did not arrive at that rule comfortably. In 2026, at fifty-two, after twenty-nine years in newsrooms and twelve running a digital desk, I walked out and launched a one-man paid briefing. The first number I published was a squad model putting Mumbai Indians' title share at 19.4 per cent, the highest of the eight sides, built on death-overs economy. On 21 May, Mumbai beat Rising Pune Supergiant by one run in Hyderabad. By June there were 1,142 paying subscribers, a fixed 6 a.m. publish time, and no editor. Where there is no editor, the information point is the editor.

The desk was paid for by the tenth season, but the data had to be clean. That is why the most important thing about this file is not that it arrived empty — it is that it declared its emptiness out loud. Data pipelines around the world do not do that every day.

Look at the pipeline in two halves. Stage 1 lifts fragments out of an article and converts them into information points. Stage 2 runs the eight-dimension analysis on those points. The weak joint sits between them, and this file is an X-ray of that joint. When the minimum input is missing, only one honest output exists — a null result.

Now the part that carries the most value: why the null result happened. Three possibilities fit the pattern. The article body was never fetched, because of a paywall, a JavaScript-rendered page, or a blocked crawler. The body arrived but encoding broke the parser. Or the document the first stage ran against was empty to begin with. What all three share is the actual lesson: this is a pipeline fault, not a judgement on the article. Nothing in these lines claims the article was poor, because the article was never read.

One fine-grained signal stung more than the rest. The domain label came back as cricket_world, while the expected value is Cricket. That is not a small thing. The label decides which analytical template opens. A schema drift like this can quietly route an article into the wrong template, and the writer will never know that football-shaped data is being placed on a batting average. I made that mistake once — in 2026, carrying cricket's phase templates into the Russia World Cup. Six of the final sixteen group matches were flagged as rotation risks and my numbers beat the closing line on four of them, but I had to write down which parameters survived the transplant and which were cricket-only artefacts. Cricket taught me the rhythm; football taught me the variance; the World Cup taught me the translation.

The second structural signal is worse: a circular dependency. The first-stage template instructs that entities be identified from the information points above. When that array is empty, the instruction refers only to itself and can never resolve. A small design flaw with a large effect — one empty payload arrived and all eight dimensions stayed blank, because there was no path to resolution.

Which produces the table every data desk should pin to a wall: what each dimension costs to unlock. Format first. Test, ODI, T20 — without that tag, batting average and strike rate cannot be weighed on one scale, and doing so is precisely the error my framework calls mixing formats. Format is the precondition for every metric.

Second, team plus format — two tokens. That alone restores the entire team-landscape dimension, which makes it the cheapest in the framework. By contrast the industry-transmission dimension is the most expensive: at least three independent information points are needed before a single channel can be traced at medium confidence. On zero points it is a guaranteed failure.

Third, time sensitivity. The field was empty, and this is the costliest omission of all. A commercial analysis built on an auction, a rights deal or an injury goes stale in days. Undated commercial analysis is not merely incomplete, it is actively misleading, because the reader takes it as current. At the November 2026 Jeddah auction my wins-added ledger priced Rishabh Pant at 19.5 crore; Lucknow paid 27 crore. I published the gap as a value flag, not a verdict on the cricketer. But that gap only means something when the date travels with it.

Fourth, article type. News, analysis, opinion, rumour, listing — each carries a different source grade. Unclassified does not mean the article was mysterious. It means no lexical signal reached the classifier at all, which points again to an empty body.

Fifth, author stance. Supportive, critical or neutral — the input without which narrative analysis is impossible, because narrative analysis is framing analysis, and framing never emerges from a summary that does not exist.

Those five produce one clean repair instruction, and in my reading it is the real achievement of the exercise: a hard sufficiency gate. The rule is simple. The moment the information-point count is zero, Stage 2 does not proceed; the document is stamped NULL RESULT at the top; it is not indexed into any knowledge base or feed. And if the subject is match-day, auction-day or injury news and the source is more than forty-eight hours old, close it out rather than re-run it — a correct number delivered late is still a wrong number.

And this is where the real danger sits: an empty payload propagates silently. The document looks finished — correct headings, correct subheadings, all eight dimensions present. Anyone glancing at the screen will assume the analysis is done. That is the deception I call structural-integrity theatre: a hollow form reads exactly like a filled one. At pipeline level there is one cure, and it is a gate that closes.

Here is an uncomfortable point, and it applies to me too. Filling a blank cell is technically very easy. The pressure does not come from above; it comes from the market. Readers want a confident number, and a desk filing twelve pieces a quarter does not survive on insufficient information. I know this from my own ledger. In 2026 the IPL's Impact Player rule arrived and I dismissed it as noise for two months. Scoring climbed, my in-play numbers lagged, and a compiler client walked. I rebuilt in eleven days by adding a twelfth-man substitution variable. In 2026, when the stadiums were empty and Sharjah's dew dragged my home-advantage coefficient for four weeks before I zeroed it in print, the lesson was the same — rules do not change the coefficient, they change the noise around it. A desk that cannot publish its own miss will not publish its own blank cell either. They are two faces of one habit.

The null result is not bravery. It is the minimum condition. Bravery is the moment a plausible number exists and the desk declines to print it. That exam did not come up this time, because there was nothing to fill in.

The commentary box has the same problem with higher stakes. In cricket the data desks won the tactical argument years ago — phase-based models, death-overs economy, opposition-adjusted rates. The holdout is commentary, which still prices milestones above match situations. It is the first to fill a blank cell, most often with he-was-charged-up or the seniors trusted him. Those are sentences, not information points. Until the vocabulary of commentary makes room for the information point, its numbers cannot be audited.

What comes next. My job before the season opens is to register the sufficiency gate as a pre-flight check, not write it up afterwards as an apology. Three signals I will watch weekly: the average number of information points returned by Stage 1, the body length at fetch time, and whether the domain label conforms to the enum. If any of the three stays red, the model is not ill — the pipeline is. A desk with no room to print zero will eventually print something other than zero, and that question belongs not to today but to the first week of the next season.