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

The record had every field in place. Title: N/A. Source: N/A. Type: Unclassified. One-sentence summary: blank. Information points: zero. Entities: none extracted. Time sensitivity: unevaluated. Source quality: could not be assessed, because there was nothing to assess. One valid signal survived the whole structure — the domain tag: cricket_asia. It reads like a result. The schema validated, the fields appear populated, the format is correct. That is precisely the problem. A record carrying zero information moved forward labelled a success, because no stage in the chain had been told that being empty is itself a failure. Cricket has been producing these records for years. For decades we have printed fields that looked valid and contained no new information, and then called them verdicts. The three-stage pipeline — extraction, classification, analysis — is an extension of a habit the sport already had. Extraction happened, classification happened, analysis began. Nobody in the middle stopped to ask what was actually in hand. The fault sits in the schema, not the technology. Cricket's rulebook is built almost entirely from positive tests. The LBW sequence is a set of yes-or-no questions: was the ball going on to hit the stumps, was the point of impact in line, did the batter attempt to play? Nowhere in the Laws is there a question that asks whether the information needed to decide the thing actually exists. When the third umpire, ball-tracking and UltraEdge arrived, they learned the rule the system already carried: treat the default as a decision. In March 2026 I was handed the 1 a.m. shifts on a Dhaka digital desk, which meant the Confederations Cup in Russia — the first senior FIFA tournament with VAR. I watched all sixteen matches with a printed copy of the Laws open and logged 23 video reviews in a notebook I still open whenever a cricket third-umpire sequence begins. Both sports keep asking the same question, and both keep losing it. Take Umpire's Call. The graphic shows the ball hitting the stumps, the screen turns red, and the record reads: Umpire's Call. To a viewer that is a binary outcome. In fact it is a threshold report. The projection stays Umpire's Call until the centre of the ball is more than half a ball's width inside the outside edge of the stump. The information is not whether the ball was hitting; it is how much margin there was. Two sentences live inside that graphic, and newspapers print them as one. The first: the original decision was correct. The second: the review could not overturn it. They are different claims. The first needs the projection to strike the stumps. The second needs only a margin below the threshold. The day that distinction is printed alongside the score, half the arguments end — and half the columns with them. The soft signal was the cleanest specimen of the disease. For years the on-field umpire recorded a default before the evidence arrived, and that default sat in the record as a decision. If the third umpire's angles were inconclusive, the answer was whatever the field had filled in blind. That could produce a bad call, but the deeper flaw was a schema that accepted an empty value as a valid one. The ICC removed the soft signal, first applied at the World Test Championship final in June 2026. That was not the correction of a call. It was the removal of a null value that should have gone a decade and a half earlier. Net run rate creates the same problem from the other side. The column looks like a measurement; it is a ratio of rates — runs scored per over minus runs conceded per over. There is a technical quirk the column never shows. A side bowled out before its overs are complete still has its run rate calculated across the full quota. So a collapse to 70 has half its damage hidden, and the table claims a precision it does not have. A reader who does not know the arithmetic treats the column as a verdict; a reader who does knows it as an estimate dressed in scoreboard language. The overthrow in the 2026 World Cup final belongs on the same list. Martin Guptill's throw deflected off Ben Stokes' bat to the boundary, and England were awarded six runs, four of them for the boundary. The outcome was valid under the Law as it then read. But the number in the record cannot be reconstructed by a reader from the text of the Law. The number exists. The information does not. The Impact Player added a fresh example in 2026. Introduced in the Indian Premier League, the rule puts a role into the scorecard that no previous format had — a player who batted and never took the field, or bowled and appeared nowhere in the innings. The card does not lie. It also does not say which condition produced the entry. And here the matter moves past technique. A data chain that cannot distinguish empty from valid runs on the same architecture as the real-time feed — the feed that reaches markets in seconds. A wrong number can be corrected later. An empty number the system has already marked correct never gets corrected, because no error was ever logged. Discussion of data literacy usually misses this: the danger is not what arrived wrong, it is what arrived blank and passed. Kazan, June 16, 2026, the 58th minute. Griezmann went down, the referee walked to the monitor, and the first VAR penalty in World Cup history was awarded — France 2-1 Australia. I filed 900 words in forty minutes that night, before the television panel had agreed on a verdict. Across 64 matches I logged the tournament's record 29 penalties, and by the final — France 4-2 Croatia, turned partly by the Perišić handball — my column was the desk's most read. One lesson came out of all of it: the screen wins the argument. From the moment a referee walks toward the monitor, the decision belongs to the screen, not the room. Our pipeline behaved exactly like one of those decisions the room did not know it was making. I have kept a review log for such decisions for years, and this time there was not a single line to write in it. In March 2026 the domestic league stopped and my week shrank to three days. Over four months I re-watched 212 matches from the European season with commentary muted, charting referee positioning, sprint lines and signal timing across 300 pages of notebook. When the Bundesliga returned on May 16, 2026 — Dortmund 4-0 Schalke in an empty Westfalenstadion — I published The Quiet Whistle. Its lesson still holds: strip the noise, then check whether the decision reads on its own. The noise had already been stripped from this record. Nothing was left. The easy move is to point at the scraper, or the board, or the broadcaster. All three are the wrong target. The technology committed no new offence; it did what it was taught. For thirty years cricket has taught that a filled form is a closed matter. The soft signal's decade and a half is the cleanest proof — a field default recorded as a decision, and nobody called it empty. The moment a system cannot report that it lacks information, every output it produces is potentially hollow. The most honest thing that happened here was that zero stayed zero. Nobody generated a picture. The difficulty is in the publishing trigger, not the fact. Not a scandal yet. Just a missing paragraph. And do not read cricket_asia as evidence. On empty input it is not the output of classification but the residue of a default. A tag that describes what an article is about is attached to an article with no sentences in it. Treating it as a subject is the same error as treating Umpire's Call as a verdict. The question ahead is not when the scraper gets patched. It is whether every cricket report — scorecard, review log, net run rate column, calendar entry — passes one check before publication: what is the new information here? The day that check becomes mandatory, plenty of reports that look complete today will be shown to be empty. And the argument will, for once, start from the evidence rather than the ending.