At 4:47 on a Mumbai morning a file opened on my screen. The feed item carried exactly one populated field: cricket_asia. Title blank, source blank, date blank, fact list dead flat. In thirty-nine years of arguing with scorebooks I have opened plenty of cricket stories with no numbers in them. The difference is that those came off a teleprinter with a reporter's name attached. This one arrived as metadata. A tag does not testify to a claim; it only says which cupboard the file was put in.

My habit was set in February 2026. A left-knee injury ended a 42-match first-class career that month, and inside six weeks I was in Mumbai's team room at the Wankhede for the Ranji Trophy final against Tamil Nadu. I hand-coded all 1,180 deliveries — line, length, seam position, field placement, the batter's scoring zone. The sheet showed Tamil Nadu's second innings taking 68% of its runs square of the wicket, right up until Mumbai pushed a sweeper back in the 41st over. Mumbai won by 141 runs. The sheet became the team's first retention document. I kept the ledger ball by ball that week, and the legend did not survive it. Momentum left my vocabulary and over numbers arrived.

A category label is not evidence. cricket_asia does not tell you whether the item is a Test, an ODI, a T20 league fixture or an Asia Cup qualifier. It is compatible with all four, which means it selects none. When the information list is empty and the tag is full, two possibilities remain: the extraction stage failed — paywall, JavaScript page, truncated body, video transcript — or the item was genuinely thin enough to hold no discrete fact. Both lead to the same editorial decision. You do not fill it.

The urge to fill is the oldest disease in the trade. A hand that sees blank space will reach for "played under pressure", "fate was kind", "there was zip in the attack" — sentences that fit any match and therefore say nothing about one. Three decades of ledger-keeping left me with four stamps, and no claim goes to press without all four.

The first stamp is format. A Test average, an ODI average and a T20 strike rate are not comparable, and the commonest error in cricket commentary is quoting an IPL strike rate as evidence about ODI form. Role decides the metric before the metric decides anything: a finisher's 140 strike rate is a failure, an anchor's 140 in a collapsing innings is a rescue. The second stamp is sample. A T20 league season runs 14 to 17 innings, and a "next great player" label built on it is a marketing signal, not a forecast. The third stamp is the home-away split, which in the Asian context is decisive: records on dry turning surfaces and records on seaming away surfaces are two different documents. The fourth stamp strips luck out — toss, DLS revision, dropped catches, DRS umpire's call. What survives all four is a trend. A trend is a rumor that survived a sample size, and most of them don't.

Which is why I will not file the 19 November 2026 final in Ahmedabad as a pitch conspiracy. India were bowled out for 240, Australia reached 241 for four in 43 overs, Travis Head made 137. The sentence I object to is the one that says 240 was a defendable total on that surface. The ledger asks what the last ten overs yielded, what the first ten cost, and what the spinners conceded per over across the middle thirty. Blaming the pitch is easy; splitting fifty overs is hard. Same method at Barbados on 29 June 2026: South Africa needed 30 off 30 with six wickets in hand, and India won by seven runs. Memory says South Africa froze. The sheet says two specific overs — the 18th and the 20th — rewrote the required-rate arithmetic. That is an over number, not a phase of play.

Names and prices need the same discipline. In February 2026 Mumbai Indians paid US$975,000 for Sanath Jayasuriya, then 38; he made 514 runs at a strike rate of 160.62 in IPL 2026. Nine hundred seventy-five thousand dollars is an argument; a valuation is something else entirely. A bid is what one room decided under scarcity, nationality quotas and bidding-war inflation. What a player is worth across a season, an Impact Player rule and a mega-auction cycle is a separate column. Before I trust a number, I find the person who wrote it down — and if that person is a tag, the number does not get counted.

Now the turn. Publishing "insufficient information" is itself a cheap alibi if you never go back and re-request the file. Audit culture has produced a new defence: say nothing, and call it integrity. Integrity is not silence. Integrity is naming the fact that would change your conclusion. I keep two scenarios, not twelve. First: if the second pass returns one dated fact with a format stamp, the item becomes analysis and should be written. Second: if the second pass returns another label and nothing else, kill the item. Everything between those two is noise.

The industry's real problem is not invention; invented stories get caught and corrected. The real problem is plausible filler — prose that reads as true of every match, every team, every series, and therefore describes none. A category tag is what dresses that prose up as reporting.

The next time a file like that opens, the first question will not be what is in it. The first question will be how many hours a re-run takes, and the second will be whether the format stamp comes back on the second pass. Everything else — the excitement, the outrage, the trending hashtag — is borrowed noise.

What kind of story cannot name its source, and yet expects to be trusted with a scoreboard?

(Correction note: no match figure in this piece was filled in from inference. Where a source was unavailable, no number was printed — only the question that will be asked once the right source arrives.)