The Empty File Match: Who Decides When the Feed Goes Quiet

The Empty File Match: Who Decides When the Feed Goes Quiet One Screen, Thirty Rows of N/A Half past seven in the evening, Singapore. The last light in the office is the one above my desk. On screen sits an open document. Title: N/A. Source: N/A. Article type: unclassified. One-sentence summary: empty. Information points: empty. Entities involved: “identify from the information points above” — meaning I am being asked to find names inside data that does not exist. Time sensitivity: not assessed. I have seen many empty files in my working life. This one is different, because there is no lie inside it. There is nothing. And that is exactly where cricket's deepest procedural crisis lives. When evidence does not arrive, what is the correct thing to do? The match keeps moving, the scoreboard keeps changing, and a verdict must come out anyway. In a third umpire's booth, that moment arrives in every serious match. Ball-tracking is loading. UltraEdge draws a flat line. Between two frames the catch goes soft. The stump mic carries wind and the scrape of a pad. The review has happened. The answer has not arrived. That is when the real question starts breathing — not the scoreboard's question, the evidence question. The whistle blows, and the real question starts breathing. How Cricket Learned the Language of Proof Cricket was never only a game. It became an evidence system a long time ago. When the player-referral version of the Decision Review System was first trialled in 2026 during India's tour of Sri Lanka, nobody imagined that within eighteen years the bat-pad-ball boundary would become so political. At first the review was a player