N/A Is Not the Same as Empty: Auditing Cricket's Legal Empty Shells

9:40 AM, Bengaluru. I opened a JSON file that looked complete. Every key in place — title, source, published_at, article_type, information_points, entities, source_quality. And inside every key, either N/A, or an empty list. The file would pass any schema validator. It would travel down any pipeline without raising a single error. I keep a spreadsheet from 2026 with all 3,360 deliveries of Royal Challengers Bangalore's fourteen IPL matches hand-coded. One column in that sheet has stayed empty to this day — I named it 'field-set: not recorded,' and the name is what makes it honest. This morning's file called its emptiness N/A. N/A and 'not recorded' are not the same thing. The first claims the value never existed. The second admits the value existed and nobody picked it up. Inside a reporting system that difference changes everything, because the first claim tells the reader the question was wrong, when the truth is usually that the answer was never requested. Cricket's recording system rests on exactly this confusion. A scorecard logs outcomes, not process. Six balls, how many runs, who was out. On what length the ball landed, which line the batter played, where the fielder moved, which intent the bowler abandoned — not one of these lives in the scorecard's vocabulary. So the default address for analysis becomes the total. Fifty overs, a hundred runs, five wickets. Complete structure, half the content. A tournament cycle accelerates the illusion. When three matches are played every day, output volume rises and volume gets mistaken for coverage. In this T20 World Cup there is some number floating on some channel every evening. I have watched this for ten years — cricket does not lack information. It lacks agreement about which information is worth recording. I let the ledger speak before I trusted the scoreboard, and the ledger always said something the scoreboard never did. In 2026 I was seventeen, four kilometres from the Chinnaswamy. RCB finished last that season with three wins. My sheet showed death-over economy of 12.1 runs per over, the worst in the league, with 61 per cent of those runs conceded off full-length balls to the leg side. That is a number no scorecard carries, because a scorecard does not keep a ledger of line and length. I built a nine-page PDF and sent it to the franchise's general enquiries address. Nobody replied. That unanswered email taught me the rule my work still rests on: a ledger can be right and still be inert, if its method does not travel with it. An email with conclusions and no methodology is a claim to the reader, not evidence. In 2026 the IPL moved to the UAE — sixty matches across Dubai, Abu Dhabi and Sharjah, September to November, empty stands. I was midway through a statistics degree and coding live for a data vendor. The pattern that surfaced: at Dubai, between overs seven and fifteen, sides that lost a powerplay wicket saw scoring rate fall 1.4 runs per over, while Sharjah's short boundaries inflated totals by roughly 19 per cent. I wrote forty pages. The outlet that commissioned it ran 900 words and cut the methodology entirely. That is where I learned the difference between a file and a format. I had a finding — stable, repeatable, thresholded. They had a slot — 900 words, no room for method. Three thousand three hundred sixty balls later the pattern stopped being noise, but it only looked distinguishable from noise because a ledger sat beneath it that no reader could see. February 2026, the mega auction in Bengaluru. Ten franchises, ninety crore each, six hundred names in the pool. I was twenty-two and building a rupee-per-win-share model off three seasons of phase data. My sheet put a 4.5 crore valuation on an uncapped nineteen-year-old left-hander. Mumbai Indians bought Tilak Varma for 1.7 crore, and he made 397 runs that season. The franchise kept the sheet. I kept the lesson. A spreadsheet can hold ninety crore rupees and still miss the point — I learned that the same February. The valuation was not wrong. The use was. The model said the market was underpricing the player; the franchise read it as advice rather than as information. That gap between information and advice is the same gap that sits between N/A and 'not recorded' in this morning's file. I stay explicit about method now, because without it a provocation and an analysis look identical. The rule is simple and dull: set the threshold before running the query, and publish it. If a finding only survives at forty balls, it is an anecdote with a spreadsheet attached. I do not chase outliers; I interview them until they confess — and the confession is usually that they are small-sample children. Which is why this morning's empty file does not frighten me, it instructs me. Three different things are dissolved inside it and they need separating. Measured and null. Never measured. Claimed to be measured and never measured. The first is a finding, the second is a limitation, the third is a fault. Cricket coverage is largest in the third category and it is the hardest to catch, because its output looks like the first — full structure, closed brackets, a confident sentence. Every clean column began as a messy argument with reality. The sheet that produced 12.1 spent three nights undecided on what counted as 'full length' — whether the yorker was in it. That small decision was the largest decision in the whole report, and nobody ever asked me about it. So now I publish the definitions first and the conclusions after. The most counter-intuitive thing I have learned: the 900-word version was more dangerous than the forty-page version, and today's empty JSON is more honest than both. An empty file does not lie; it says it has nothing. The 900-word version was ninety per cent true and silent on the tenth — and that tenth carried the whole claim. The reader saw the conclusion and never saw the method, so trusted a building whose foundation he was never shown. One more boundary, because 'absence is also a variable' is a phrase people ride too far. No reply to that nine-page email is not evidence of suppression. It is evidence that email to a general address lands in an unread inbox. Absence must be weighted, but the cause of absence must be named even more carefully, or a data audit drifts into conspiracy theory. I have made that mistake and I have corrected it. The question that matters in this tournament cycle is not any player's average. It is which field we failed to record this week. Ask an analyst for the number and he will give it to you, and it will usually be right. Ask which cell is empty and why, and the schema starts to change. The next round will be decided by when we first start talking about ball length, not by when we stay silent about it. In twelve years I have learned one thing: empty spaces do not fill themselves, but naming them is in our hands. And the day we start writing 'not recorded' instead of N/A, cricket's data will speak the truth for the first time. The question is not how many runs the next match produces. It is which column will appear on the next scorecard that does not appear today — and whether we will recognise it while it is present, rather than after it is gone.