One Label, Zero Information Points: The Part of Cricket That Never Made It Into the File

There were thirteen lines on that screen. Twelve were empty. Where a one-sentence summary should have sat, there was nothing. Where the author's stance should have been recorded — the stance that tells you whether the man is sitting neutral or sharp-edged — it said 'Not Applicable'. Where time sensitivity should have been assessed, 'not assessed in Stage 1'. And where the piece's type should have been fixed — match report, preview, analysis column, administrative news — there was a single word: Unclassified. One box out of thirteen was filled, the one at the top: cricket_world.

At first I thought the page was blank. Then I saw the blankness was not one error in one place; it sat evenly in thirteen places. Information points: zero. Source quality was to be 'judged from the source fields' — and the source fields did not exist, no publisher, no byline, no date, no URL. The attached notes held instructions for the work rather than results of it, as if a clerk had arrived with a rubber stamp and found no paper on the desk.

The document belonged to no ground. It belonged to a server.

But in thirty-seven years of writing cricket I have learnt one thing: every cricket story passes through several doors before it reaches a reader. Headline, byline, date, series tag, venue code, tournament identity. The machine reads those doors. It does not read the ground, it does not read that evening when Parthiv Patel's eyes were wet, and it does not read the phone call that came from a village. When the doors are missing, there is nothing left for the machine to sit down with.

There was a contradiction in that document that made me stop. The article type could not be fixed, yet the domain was fixed with complete confidence. The two do not sit together. Domain identification is the bigger job of the two — it is what rises out of the inside of a story. So where did the domain come from? From the cheapest route available. The word 'cricket' was sitting in some URL, a sports label was stuck in some metadata. From that one word, cricket_world was born. The label was a guess, not a finding.

cricket_world must be read as a prior, not as a result. It tells you the topic space is cricket; it does not tell you that any piece of cricket was actually read.

In cricket that distinction is a matter of life and death, because time does not move at one speed for everything in this game. A match report goes stale in hours. A preview expires at the toss. Board, ICC, scheduling and finance stories run for months. A player profile runs for years, sometimes past his retirement. A document that never decided whether the piece was a matter of hours or a matter of years files a 2026 feature and today's team news in the same drawer. The reader will notice the difference. The file will not.

Now the part that matters most to me.

January 2026, Holkar Stadium, Indore. Gujarat chased 312 and won by five wickets. Parthiv Patel made 143. The state got its first Ranji title after sixty-seven years. I was not on the field that evening but in the third chair of the press box, and I remember that the final did not raise its voice; it waited for mine. I wrote twelve hundred words. More than a hundred and twenty thousand people read that piece.

What got recorded in that piece without any effort of mine was this: the byline, the date, the series tag — Ranji Trophy 2026-17 — the name of the ground, and the attached scorecard block. Eight or nine information points that made an emotional piece findable. My tears did not save it. Its tags did.

Now imagine the quarter-final of that same season. A match finished in three days. Two thousand people, half of them schoolchildren who did not know who was playing inside. A freelancer wrote it, three hundred words, no series tag, no venue code, 'Staff' where the byline should be. That piece exists. Go and find it today.

This is the gap nobody looks at. What gets classified gets remembered, what gets remembered gets funded, and what gets funded gets covered. Cricket's archive is built not from truth but from tags.

August 2026, Mount Maunganui. India beat Australia by eight wickets in the Under-19 World Cup final. Shubman Gill made 372 runs across the tournament. I went looking for a scoreline and found boys learning how to become. A youth sports network picked that piece up. Why? Because an international code was stuck to the event — an ICC tournament, a fixed set of dates, an eight-team structure. An event with an international code walks into the file by itself; a domestic event has to be walked in, and there is nobody to walk it.

The scoreboard is only the surface; beneath it, people change like seasons. At Mount Maunganui I saw exactly that — eighteen-year-olds with no tags, only a cover drive.

In recent years Hindi, Tamil and Bangla commentary have expanded. I count that as genuine democratisation, and I will not argue that the doors have not opened. But alongside that expansion runs a technical asymmetry we do not discuss. A page whose text loads late through JavaScript is an empty page to the machine. A page behind a paywall is also empty. A feed that sends only headlines never sends the article. The result is direct: an IPL press release written in English carries eight information points, a Ranji report written in Tamil carries zero. The language was democratised. The archive was not.

In the women's game this is sharper still. What happened at DY Patil Stadium in November 2026 will be filed a thousand times — every scorecard, every celebration, every tear. The calendar that should have been built after that win may not have a single date recorded anywhere with a tag attached. The trophy gets tagged; the calendar that follows does not. And when the next generation asks how many grounds women's cricket got in 2026, the answer will not be found in the tagged drawer.

Now the thing least likely to be said about all this.

People will say the machine failed. The machine did what it was told. Producing an empty result from empty input is not the machine's error, it is its honesty. The real miss is upstream, at the point this document came from. A truncated fetch, cut text, a page locked behind a paywall, a body that grows late out of JavaScript, or a feed that ships only the headline. None of those is a machine decision. All of them are publisher decisions — the choice of CMS, the setting that blocks crawlers, the habit of the feed, the hurry that strips the byline.

And here is an uncomfortable truth I accept about my own trade. We have arranged our newsrooms around what can be indexed. What cannot be tagged slowly stops being written. Once the editor asked, 'What is the story?' Now the question is, 'Where will the story sit?' That question sounds innocent and costs a great deal.

It is easy to say the print age was pure. That age was the same one in which the 2026 match-fixing scandal surfaced — the inquiry, the bans, the end of the careers of the biggest names of the day. The print archive was not holy. It was merely more completely filed. What was printed in a newspaper got bound into a bundle and could still surface thirty years later. What is published on the web dies when the link breaks, and a whole season dies with it.

The next time a Ranji knockout is played in an empty stadium — three days, no camera, no scoreboard update — the question will not be whether it was covered. The question will be whether it was filed. Because the archive is the second scorecard, and the next generation's cricket history will be written from the scorecard that was born with a tag.

The empty stadium taught me that silence files its own match report. My only job is to put a date at the top of it before the server forgets.