Who Owns the Two Minutes: From Delhi to DRS — A Ledger of How Decisions Are Made in Asian Cricket

Delhi, 6 November 2026. Smoke sat over the Arun Jaitley Stadium. Bangladesh against Sri Lanka, a World Cup group game. Charith Asalanka's 108 had carried Sri Lanka to 279. In the twelfth over Sadira Samarawickrama fell. Angelo Mathews walked out. The chin strap on his helmet snapped. He raised a hand towards the dressing room and asked for a replacement. What followed had not happened in 146 years of international cricket. Shakib Al Hasan appealed. The television umpire watched the replay, watched a clock, and gave Mathews timed out. The first such dismissal in international cricket. The dismissal is not the story. The gap is. Somewhere inside the ninety-odd seconds between the strap breaking and the appeal, a clock was running, and nobody wrote down whose hand it was in. The scoreboard carried one word: out. Behind that word sits a calculation with no accountant. I have kept a ledger of decisions since 2026 — I counted 118 decisions before I understood my own knee. In Delhi one column of that ledger stayed blank, and the blank column is what this piece is about. Law 40.1.1, MCC's 2026 Code. After the call of Time, and before the striker is ready to receive the first ball, the incoming batter must be in position to receive the ball within two minutes of the fall of the previous wicket. Before 2026 the limit was three minutes, under the 2026 Code. Seventeen years of cricketers had been built around three minutes. Then the law removed one of them. No coaching manual contained a drill for that minute, because a minute cannot be drilled. The law was written under the pressure of over rates, not the pursuit of fairness. The 2026 Code was the largest rewrite since 2026 — bat size, fielding restrictions, caught behind. The two minutes travelled inside that package. The administrative aim was the speed of the game. The aim was sound. But nobody writing the law asked who would operate the clock. The law says the batter must be ready within two minutes. The two minutes begin at the fall of the wicket. Not when the batter leaves the dressing room. Not when the umpire raises the finger. At many Asian grounds the walk from the dressing room to the pitch is longer than at Lord's. The same two minutes is therefore not the same distance. The law claims to be about time. It functions as a law about distance, and distance changes from ground to ground. Then there is the appeal. Under Law 31 an appeal is a question. If the fielding side asks before the next ball, the umpire must answer. Shakib appealed inside the law. The umpire answered inside the law. On paper the law worked. The question is not about the law. It is about the process. For seven years I have written to one method. Whether a decision was right comes second. First comes: where was he standing? Umpire's position, sightline, the direction his body turned. After I coded 118 decisions in Sydney in 2026, my writing changed shape. Every piece since opens with position, not law. Timed out is the one exception. No ball, no pitching, no stance, no impact. Position means nothing here. The method collapses because the thing being measured is not distance but time, and the instrument for time is not on the field. The field holds the umpire's eye, the stump mic, the ball-tracking cameras. None of them is a clock. The evidence that produced the Delhi decision was a clock in a broadcaster's graphics. The central proof for applying a playing law came from the screen of a commercial entity. The match referee keeps a separate record, but the match referee has no independent clock that can start and stop time on its own. The television umpire cross-checks against the broadcast feed. This is not a bad system. It is the absence of a system. I am not writing blame. I am writing a ledger. When a decision rests on the timing of a commercial feed, any doubt attaches to the evidence and to the process. And doubt that attaches to process later gets argued as a question of spirit, which is exactly what happened. Much of my work is audio. On 30 August 2026, watching the Grand Final at an empty Bankwest Stadium, I transcribed referee Chris Beath's on-field voice — 412 verbal instructions in 90 minutes, from no, no, no to green, green. Silence for ninety minutes can explain more than a thousand replays. I tried to apply that habit here. In Delhi the stump mic gave me the appeal, the deliberation, the announcement. It did not give me the one fact that would have settled everything: whether Mathews was genuinely held up by equipment failure or by his own pace. There is no stump mic in the dressing room. There is no mic in the tunnel corridor. The sound of a strap snapping is the only audio evidence, and no microphone caught it. Audio evidence here is half a witness. The second machine that manufactures decisions in Asian cricket is DRS. In 2026 I watched all 64 matches of the Russia World Cup and built a 41-column spreadsheet — 29 penalties, every VAR intervention, every review's duration. Four hundred hours, one lost university unit. Sixty-four matches taught me that one spreadsheet is never enough. In cricket the same problem sharpens, because here a ball may or may not strike a stump. The system has to predict. Umpire's call is defined by half a ball's width. If the ball is predicted to strike within that band, the on-field decision stands, out or not out. On first reading the rule protects the umpire. In my accounting it protects the ball-tracking. The reason is simple. Ball-tracking is an estimate — a projection from the post-bounce path to the stumps. Every projection has an error margin. If the rule were that whatever the tracking says is true, that margin would be publicly tested on every review. The half-ball band conceals it. The question now is how large that margin is on Asian pitches. This is a hypothesis, and I do not pass hypotheses off as evidence — I do not trust a pattern until it survives three different angles. The hypothesis: on Asian surfaces the ball deviates more laterally after pitching, bounces lower, raises more dust. Greater lateral deviation means greater predictive uncertainty. The same band of umpire's call therefore does more work in Kanpur or Galle than it does in Perth. There is a way to test this — the same bowler, the same length, two different pitches, several hundred tracking frames. I am not aware that anyone has. There is also a distance threshold in the review protocol. If the point of impact on the pad is far enough from the stumps, the tracking projection is set aside and the ball is assumed to have continued on its path. Cricket writing almost never mentions this threshold, yet on Asian spin pitches batters routinely come out to meet the ball. Where the threshold applies, the decision no longer rests on tracking. It rests on a human assumption that nobody records. My real interest is not decisions but intervals. Drinks, tea, stumps, rain — these are the game's hidden accounting. In Asia that accounting is more complex, because monsoon rain creates intervals nobody scheduled. The hybrid model of the 2026 Asia Cup, the Colombo rain, the reserve day: all of it is the politics of time. The two-minute timed out is the smallest member of that same family — a compulsory interval with contested ownership. Intervals have a price. In international cricket, slow over rates draw fines as a percentage of match fee. In the IPL the penalty is harsher: an in-match fielding restriction, an extra fielder inside the circle. Time has a direct market value. But in a timed out, the cost of time falls on one batter while the benefit flows to the fielding side's over rate. The accounting is uneven. Asian cricket now runs on a calendar where franchise leagues — IPL, BPL, LPL, ILT20 — sit in the gaps between international series. Who gets a player's best weeks is cricket's invisible rule. In that arrangement, the value of a player's two minutes is set not by a board but by broadcast contracts and league windows. So if a decision like Delhi is treated purely as a question of cricket law, we are arguing in the wrong room. The question is about the politics of the game: who owns the time, and who writes the ownership down. I offer one proposal, borrowed from technology outside the sport. Every DRS review, every timed out, every over-rate ruling is recorded somewhere, but the record is scattered, incomplete and revisable. If decisions had an immutable, public ledger — the core idea of a blockchain: write once, and no one can alter it afterwards — three things could be logged. One, the exact timestamp of when the clock started, and who started it. Two, the umpire's position and sightline. Three, the spoken reason for the decision. With those three lines, the Delhi question would have been a different question. Nobody would have had to guess. And a decision written immutably draws its criticism somewhere else — at the process, not at the person. Cricket's decision ledger today is a memory, not a document. Memory does not lie, but memory changes. After that day the argument went towards spirit. Was Shakib's appeal contrary to the spirit of cricket? Was Mathews humiliated? Those questions are sensitive and useless. Spirit has no definition, and what has no definition cannot be applied. The law has a definition, an application, a result. The law worked. My contrarian question is drier. Who was operating the clock for those two minutes, and why is that person's name nowhere? We spent days judging one man's morality while the part of the process that actually broke — a clock with unclear ownership — went unmentioned. That is my objection. If a decision stands on a clock, the clock's accountability matters more than the decision. The second contrarian angle concerns DRS. The common view is that umpire's call saves the umpire. I read it the other way. That half-ball band is not protection for the umpire but a covering for the technology's ambiguity. As long as the system's error margin is not publicly tested, everyone inside that band stays safe — the umpire, the tracking, the decision. Only the spectator is left not knowing what happened. One more point, from professional habit. Before arguing about whether a decision was right, I look at the place. In Delhi the only place worth looking at was the television umpire's chair. The man sitting there was looking at a feed and a clock. What we watched from outside was the same feed. Our viewpoint and his came from a single source. When there is no second vantage point, arguing about vantage points is meaningless. That is my largest doubt. I am not delivering a verdict, because the information needed is not in my hands, nor in anyone's — nobody recorded it. One thing is clear. The two-minute law was written as a law about time, yet it operates on an uneven field of distance, equipment and ownership. If the MCC or the ICC eventually mandates an independent match clock — visible on the big screen, controlled by the match referee, independent of a broadcaster's graphics — timed out will stop being a controversy and become a procedure. Alongside it, a definition of equipment failure is needed. If a broken strap counts as failure, whether that time is deducted from the clock should be written down in advance. In my ledger the column for that day is still empty. Seven years on I have not filled it, because the fact required was never recorded. The next time someone is late inside two minutes, my first question will no longer be whether he was at fault. My first question will be: whose hand was on the clock? And if the answer is not in the game's record, then cricket has written down another decision's arithmetic while leaving the accountant unnamed. — Root: Referee