Zero Information Points: The Empty Dossier That Told the Truth About Cricket Coverage

A file opened on the desk on Wednesday afternoon. The top line carried a single label — cricket_asia. Below it: title, N/A. Source, N/A. Type, unclassified. One-line summary, empty. Author's stance, N/A. Purpose, N/A. And then the one field for which I have spent four decades learning to read a scorecard — information points: zero. Two notes were attached to the file. The first: "identify the entities from the information points above." The second: "judge source quality from the source fields of the information points." Both sentences belong to a scorer who hands you a blank sheet and asks you to pull the batsmen's names out of it. There was nobody in the chair, and the form was being filled in anyway. In December 2026, at the Adelaide Oval, I had seen another emptiness — a larger one. India collapsed for 36 in their second innings that day, Mohammed Shami's forearm bone broke, and the match was lost by eight wickets. The stands were empty, the press box was empty, and there was a silence in the air that sat beneath the noise of the scoreboard. Adelaide taught me that a collapse is a silence before it is a score. But at least the scoreboard was talking. Here, nothing spoke. The paper in front of me was not a deconstruction of an article. It was the output of a pipeline we had mistaken for an article — stage one, where title, source, genre, summary, author's stance, purpose and information points are pulled from raw content. That stage pulled nothing and printed the defaults. This is not a thin article. It is a null. And the distance between thin and null is the same distance that separates an unfinished innings from "36 all out." To understand it, you have to look at the pipeline. In a 2026 newsroom, no cricket story reaches an editor directly. A machine opens it first, separates its claims, and every decision downstream follows that separation — which story gets space, which gets a headline, which gets a single line. Identify the entities, grade the source, fix the genre. A fact the machine could not read does not publicly exist, because the answer engines lift from wherever they were given something to read. So the emptiness of this file is not merely a technical event. It is an editorial one. When the entire evidentiary base is missing, looking for depth means filling in some other article's content from your own head and then commenting on it — treating inference as conclusion. I have never done that, and I will not start today. One signal survived: cricket_asia. What that is, is not clear either. It could be the correct classification of an article about an Asian board, league or team. It could be the fallback tag that gets applied when the classifier receives no text at all. And it could be a fuzzy match on one fragment of a title or a URL that never made it into the output. Without a single information point, I cannot tell these apart. So where is the fault? There are four known causes of an all-defaults result. JavaScript-rendered pages, where the text arrives from the browser and not the server. Pages locked behind a paywall. Content in a non-Latin script or a mixed language. And PDFs or scanned images, where the words sit inside a picture. All four are technical causes. In cricket they carry a second meaning, and that is the real story. Think about where Asian cricket is actually written. District association circulars. Trial lists printed as PDFs. Scanned scorecards. The weekly paper's pages that are printed in the same town and never climb onto a server. The sports pages of Bengali, Tamil, Urdu and Sinhala dailies. In 2026 I was the Madras correspondent of Sportsworld and freelancing for The Telegraph. Even then the system had the habit of looking in the wrong place. Many languages were spoken in the press box; only one was written into the file. Which brings back an old habit — I have learned to read a scorecard for the names it leaves out. Today an index is doing that work, and it is leaving them out just as quietly. She was already batting before the ledger had a first line; the line was never drawn. Let me say plainly what I have understood. The machine can read the part of cricket that is in Roman script, cleanly attributed, and openable without anyone's permission — press releases, broadcaster quotes, franchise tweets, the mainstage noise of the IPL. And it rules out of every answer engine the part that is slow, regional, on paper, or that nobody has made free. The result is not that the game is covered less. The result is that the most honest part of the coverage falls outside the index. The biggest Asian cricket stories usually sit in that outside part — the franchise scout replacing the zonal selector, the Ranji professional whose name never reached the list, the second XI that would beat half the Test nations, and the scorecards buried inside a PDF. An old argument of mine holds: the IPL did not kill Test cricket in India; it made the tournament underneath it invisible. The pipeline is repeating the trick, only much faster and without any television commentary. One thing experience has settled. On the day Adelaide ended at 36, the numbers were everywhere within minutes. Numbers travel. I took not a single quote from the press box that day and wrote a long essay instead — on the sound of a team forgetting how to bat. That essay will never enter a list of "information points." At Derby in 2026, Harmanpreet Kaur made 171 not out off 115 balls against Australia and India won by 36 runs. The desk asked for it shorter; I filed it long, because what was in that innings was geometry — anger turned into angle — and no extraction tool keeps that. It keeps "171 (115)" and drops the rest. During the February 2026 mega auction week I spent more time with agents and trainers than with purse arithmetic. Mumbai Indians released Hardik Pandya; Gujarat Titans bought him for 15 crore rupees; by May he had captained the debut franchise to the title, beating Rajasthan Royals by seven wickets in the final. My personal rule: one human detail before any statistic. Fifteen crore is a number; the man behind it wakes at six. Information points keep the number and lose the man. So this empty file is not an accident. It is the system behaving as designed — and the design has a language preference. Now the part where the obvious reading fails. The obvious reading is this: extraction failed, therefore the problem is technical. Tell the engineering team, add OCR, install a JavaScript renderer, sign a paywall partnership, and next time it will be fine. That should certainly be done, and it is exactly the advice I gave — send the raw text first, then the analysis. The reading has force. The trouble is that it is incomplete, and its incompleteness is oddly comforting. Because the one good thing that happened in this file is that the machine did not invent. An empty box said plainly that it was empty. I trust that paper which reports it found nothing more than the dossier that serves five plausible-looking points with nobody checking where they came from. A virtual pitch still has a crowd that can go silent. The system that declared this void kept the crowd quiet. The truth is that "re-extraction" is an engineering answer to an editorial question. The article existed. Someone wrote it — in a district press, on a weekly's page, on a keyboard that night. The pipeline could not read it; fine. But before the machine was called in to help, no one in the newsroom had read it either. The real failure sits there. The machine honestly displayed what lay outside its reach; we called it a language problem and closed the file. Looking ahead. Before the next re-extraction round, run a single count — how many regional-language cricket bylines entered our index last month? The answer will surprise, and it will say more about which game we cover than any OCR upgrade. Copyright rules, paywall deals and scanning costs are now as much a part of a sports desk as a drop-in pitch reporter. The box is still open in front of me: information points — zero. One day it will fill. The question is not when. The question is whose voice will be inside it when it does — the press release that arrived at two in the afternoon, or the writer who watched that match in her city's language, at her own expense, and was never read by any index. She was already batting; the writer was already writing. The ledger had not yet drawn its first line.