Timed Out: The Two-Minute Case File, a Broken Strap and the Oracle Problem

I rewound the feed four times. Each time it froze on the same frame — 6 November 2026, Arun Jaitley Stadium in Delhi, Sri Lanka's innings, and after a wicket falls, Angelo Mathews walks to the crease, the chin strap of his helmet snaps, and he signals for a replacement. The clock that was not in the corner of the screen was the real witness. Two minutes. Bangladesh needed a win to keep their semi-final hopes breathing. Shakib Al Hasan's appeal, umpire Marais Erasmus's finger, and the first timed-out dismissal in the 146-year history of international cricket. The frame stopped. The question started breathing. After the match Mathews called it disgraceful; Shakib said it was within the laws. Both sentences are true, and both are incomplete. Nothing malicious sat at the centre of this — a time limit did, and where that limit begins and ends is still not clear enough in cricket's lawbook. Law 40.1.1: after a wicket falls or a batter retires, the incoming batter must be ready to face the next ball within two minutes; otherwise the umpire calls Time and the batter is Timed out. The MCC tightened the wording in 2026, clarifying that it also applies after retirement. The law is not new. It entered the lawbook in 2026. Forty-three years, more than two thousand ODIs, more than two and a half thousand internationals — and nobody had ever been dismissed this way. People will call that an accident. I call it information: a rule existing on paper and a rule operating on the field are two different things. The match context matters — for Bangladesh it was nearly the last chance, for Sri Lanka a fight for pride. In a game under that pressure, no one expects an umpire to apply a law like this for the first time. Erasmus and Richard Illingworth did. That is the weight of the moment. Now I watch it not through the match replay but through the clock's eye. To me, timed out is the first law in cricket where the decision is made not by an event but by a duration. Every previous dismissal had a visible cause — ball hits pad, stump flies, catch completed. Here the cause is an absence: what did not happen within two minutes. In the DMC era we are trained to obsess over when — where the ball pitched, how in-line it struck the pad, whether the ball touched grass before the catch. This clock clause is a different species. It is not camera evidence, it is clock evidence, and the clock is cricket's oldest, most neglected technology. Here is my second problem. Feed-first verification means I chase latency and provenance — which frame reached whom, and when. At the ground, spectators watch a batter walk in, fix his helmet, wait. On the TV feed, no official clock runs alongside that wait. The stump mic carries Erasmus and Illingworth talking, but nobody on the broadcast shows exactly when the countdown began at the timing controller's desk. So a decision is built on information the viewer does not have and the replay cannot show. I am not assuming the clock miscounted; I am saying the clock was never called as a witness. In the same stadium, a catch in doubt gets thirty angles and ultra-edge. A time limit in doubt gets nothing. Now look through the referee's eye. Erasmus has nearly three decades of experience, an ICC Elite Panel umpire, arguably among the best of his generation. Mid-match, under pressure, facing something that had never happened before in international cricket, he had to stand up not only the law but a whole career of instinct. The referee's eye is not a camera; it is a compromise under pressure. When Shakib's appeal came, Erasmus genuinely had two paths — the letter of the law for timed out, or a small allowance for reality. He chose the law. That choice is hard, because no formal buffer for leniency is written anywhere. Nothing says a snapped helmet strap earns mercy, and nothing says it does not. That gap produced most of the argument afterwards. So my suspicion becomes clear — the problem is neither Mathews nor Shakib. The problem is that cricket's lawbook wrote a clock-dependent clause and never put the clock on the witness stand. We measure where the ball pitched and how high it struck the pad to the millimetre, yet there is no scrutiny of the millimetres inside the phrase two minutes. The fate of a whole dismissal rested on an invisible clock, and its explanation arrived in one-sided commentary. Now the emotion-versus-rule angle. There is a phrase called the spirit of the game, and some use it like a weapon. I believe in the ethics of that spirit, but only when it first marks where the lawbook's blank space actually is. Otherwise the spirit becomes a canopy for guesswork — the losing side cries spirit, the winning side cries law. I know this double accounting, because reporting on sporting discipline in Singapore showed me the same incident judged differently on different stages. In the background sits the world of migration documentation and corporate compliance, where a deadline is not a word but a test — one minute late means the door shuts. But at least there the deadline clock runs in public. This is where my small cross-domain comparison comes in. In the world of modern smart contracts there is a famous problem — the oracle problem. The code is fixed, but who feeds the truth of the outside world into it? Deadlines, dates, events are measured by an external oracle, and if that oracle is alone, invisible and unproven, even the most flawless code can reach the wrong decision. The timed-out law is exactly that — the clause is precise, but the oracle measuring two minutes stayed alone, invisible and unproven. I respect my own limit here: I am not using this analogy to claim the law should be broken, only that making the clock's evidence public would halve the dispute. The real test is simple — if the clock were public, would the outcome change? Maybe not. But the legitimacy of the decision would change, and that is the real issue. So what is needed going forward? I put three proposals on the table, each small, cheap and realistic. First, a visible countdown shown on the broadcast, the way football's added time runs in public. Second, a clear equipment-breakage protocol: whether the clock stops when a helmet or bat breaks should be written in advance. Third, fixed language for announcing the decision, so that leniency and strictness become two proven branches of the same law. It is worth remembering the final result — Sri Lanka made 279, Bangladesh won by three wickets. But the argument over Mathews's dismissal never made it into the run column. The clock is a curious thing. DRS, smart ball, semi-automated offside, boundary cameras — we have imported every technology to measure ball and crease. But cricket's only law that runs purely on time has no technology at all. The finest justice in the game still depends on a clock in some control room that nobody sees and nobody verifies. A final does not end at the trophy; it ends when the last frame is explained. Cricket has still not explained that frame from 6 November.