The Half-Ball Law: Asia Cup's Third Umpire, Archive Gaps, and the Dhaka VAR-Log

I begin with a stopwatch. Under the Sharjah floodlights, the moment the ball-tracker froze on the big screen, the clock read twenty-seven seconds. In the third umpire's room the same frame was looping for the third time: where the ball pitched, where it struck the pad, and the projected path toward the stumps. The on-field umpire had raised his arm. Between two thin lines on the screen sat the centre of the ball and the outer edge of the stump, separated by a sliver. The verdict came back: Umpire's Call. The stands boiled over, the feeds filled up, and twenty seconds later the clip slid off the broadcast. Apart from what a few spectators recorded on their phones, no official copy of that frame survived. That is where my work sits. Not judging the game from the sofa, but rewinding the review frame by frame, timing it with a stopwatch, and then asking who preserved the evidence, who deleted it, and who answers for it. I started the VAR-Log because Dhaka made me; back then I logged penalty-area incidents in football with timestamps and confidence intervals in a spreadsheet. Moving to cricket, I found the problem unchanged, only the machine had a new name. Review technology entered international cricket not out of doubt but out of pressure. In July 2026, a Test between India and Sri Lanka at the Sinhalese Sports Club in Colombo became the first to use the player review system. The early fear was that it would break trust in the umpire. The opposite happened. Technology made decisions faster and, at the same time, split ownership of a decision three ways: the on-field umpire, the video room, and the ball-tracking company. Hawk-Eye, Virtual Eye, Snickometer, Ultra-Edge — these names are now as familiar as a scorecard. Some treat them as neutral instruments. I treat them as contractors. The data is sound, but how that data is read is a matter of contract, and that contract is negotiated between the ICC and the broadcaster, not in front of the crowd. The review is divided into three elements: where the ball pitched, where the impact occurred, and whether the ball was hitting the stumps. The first two allow a direct challenge to the on-field umpire. The third carries the half-ball law. If the centre of the ball falls inside the outer edge of the stump, the on-field call stands; if the centre falls outside, the call is overturned. That thin boundary is Umpire's Call. Impact has its own line: if the batter has advanced more than three metres from the stumps, the on-field umpire's view on impact becomes final. In June 2026 the ICC abolished the soft signal, which had let an on-field umpire's tentative instinct anchor the third umpire's reasoning on tight catches. Now inconclusive evidence tilts toward not out. The rule changed, but it changed in a committee room, not on a match night. Time is also a law here. Since 2026 a fifteen-second limit governs the review request; the clock starts once the ball is dead, and a captain must decide inside it. In Tests each side gets two unsuccessful reviews per innings, topped up after eighty overs. In ODIs and T20Is each side gets one. These numbers decide which matches are searched for evidence and which are left to luck. One review is a bet, and a bet cannot be priced when the tracking system's own confidence margin is never shown to the audience. The Asia Cup complicates this further, because the machine reads differently when the venue changes. The 2026 edition was staged in Dubai and Sharjah in the United Arab Emirates, on hard, even-bouncing pitches where the ball barely seams, so tracking projections are relatively stable. The 2026 edition ran across Pakistan and Sri Lanka, and Sri Lanka's humid air makes the ball swing, which is where projected paths are weakest. The same review, the same element, two venues, two levels of confidence. In the 2026 final at Colombo, Sri Lanka were bowled out for 50, with Mohammed Siraj taking 6 for 21; that night the ball seamed so sharply that fewer decisions depended on tracking at all, because much of the contest was settled before pad contact. Bangladesh's story runs parallel to this technology. A side granted Test status in 2026 recorded its first Test win in January 2026, against Zimbabwe in Chittagong, and had played its first ODI in the 2026 Asia Cup. Through the first decade and a half of Test status, Bangladesh's problem was not talent but decision-making: when to press, when to release. Reviews arrived exactly as the team was still learning the language of its own choices. Early reviews were taken on emotion, on the shout of a catch. That changed later, because a new habit grew inside the side — not one individual, but a practice. Now to the three frames I return to on every review. Frame one: pitching. The graphic shows a single straight line traced from a point on the pitch to the stumps. What it hides is spin, seam position, and the real character of that patch of turf. The same delivery landing two inches either side would produce a different result in a different match. I do not loop this frame more than three times; if pitching is clear I move on, and if it is murky I write down that clarity is absent. Frame two: impact. This is where the three-metre line operates. When a batter charges out to attack, the on-field umpire becomes final on impact — meaning the technology exists but its verdict does not apply. The quiet consequence is a shield built for the batter who stays home. Some describe this as protecting a batsman's freedom; I describe it as a deliberate design that keeps a human above the machine. Frame three: the geometry of the stumps. The ball is a sphere, the stump a narrow pillar, and the relationship between the sphere's centre and the pillar's outer edge produces the half-ball boundary. The machine offers a probability, a distribution. The rule slices that distribution into two halves, yes or no. A centimetre either way becomes an entirely different decision, and two teams are invited to read it as justice. Here lies my deepest objection: the technology has reduced error without increasing precision. The precision was manufactured by the rule, and the rule was never written in the machine's language. Once the three frames are done, my rule is simple: no more rewinding. I select three decisive frames, match one rule citation to them, and stop writing. I started the VAR-Log because Dhaka made me, because in my city a decision is made in a room of thirty feet and the raw data of that decision never leaves the room. This log is a habit of watching that door. The economics of time is the least discussed part. The fifteen-second clock pressures the team, but who owns the clock? The broadcaster. When the camera goes close, how many times the replay loops, when the graphic appears — all three choices belong to the production team, and they decide how informative those fifteen seconds will be. A team that decides quickly is really a team that reads quickly, or knows what it should be looking for. The keeper's tone in the captain's ear, the experienced slip fielder's gesture, the coach's signal from the boundary — three separate currents that must merge inside fifteen seconds. That is strategy, and it is now a cricket skill with no official statistic. One review per side in ODIs produces a structural distortion. A team that knows it can only be wrong once raises its hand only in clear cases, and clear cases flatter the numbers. Nobody reviews in the uncertain zone around impact, because the risk is asymmetric. In Tests, two reviews plus the eighty-over top-up changes the whole equation: burning both in the first two sessions is folly, while being too conservative wastes the tool. That gap shows that the justice of a decision shifts with the format — same law, same machine, different fairness. The archive question is the most uncomfortable. The raw ball-tracking data — coordinates per frame, seam angle, confidence bands — generally sits with the broadcaster and the technology provider. The audience sees an animation of a ball travelling a fixed path, plus three words in three colours. The underlying data is never published. So the broadcast claims evidence while storing that evidence inside a commercial contract. After the match, the clip slides off air within twenty to thirty seconds and lands in no central archive. Who is the archive for: accountability, or the broadcast? A simple question with a slippery answer. This gap defines the limits of my own accounting. From broadcast replays I log the time of each review — seconds to referral, seconds to verdict, which element flipped the call. But I cannot verify coordinates or confidence bands, because I do not have them. A column that claims evidence must first declare where its own blind spot sits. I started the VAR-Log because Dhaka made me, and in that log every number carries a note beside it: verified, or merely inferred. There is a myth that Bangladesh are weak at using the technology. The problem is not skill but information flow. A side clear about its own bowling plan knows how much a given delivery used the pitch, and that makes its review arithmetic better. Reviews are not taken on the shout of a catch; they are taken by reading the pattern of where the ball lands. The judgement of an experienced all-rounder like Shakib Al Hasan, or of a keeper like Mushfiqur Rahim standing behind the stumps, matters here, because the memory of a pitch carries more information than a camera does. In the age of technology, the most valuable skill has become an old-fashioned patience. A parallel suggests itself. The prices placed on young players in franchise auctions are the price of possibility, not of certainty. At the IPL auction held in Jeddah in November 2026, Rishabh Pant went for 27 crore rupees, the highest of that auction. The review system runs the other way: here certainty is the most expensive commodity, and it cannot be bought, because the confidence margin is never shown. In both places numbers are spoken aloud, but which number is a control limit and which is a gamble is never separated on the page. This is my counter-intuitive observation. When a crowd rages at Umpire's Call, the anger travels toward the machine. The machine is blameless; it reported a probability, and the rule made the decision. The boundary that preserves the on-field call was drawn in a committee meeting, deliberately, so that a grey zone exists between the machine's clear verdict and human judgement. That grey zone is the real politics. Why direct fury at the instrument when the line was drawn out of sight? The second uncomfortable angle is the graphic itself. The tracking animation is a simplification that flattens a distribution into a single line, much as a heatmap hides a player's role. In cricket its familiar form is the wagon wheel. A wagon wheel shows where a batter scored; it does not show against which deliveries, against which field settings, in which match situation. The review graphic works the same way — three words, three colours, with an entire calculation of uncertainty hidden underneath. The third angle is the theatre of waiting. The suspense built on screen during a review is not accidental. Stadium lighting, the looping logo, the slow frame changes — together they turn the wait into a product. I have timed it: in one match a review took forty-four seconds, in another ninety. The information did not differ; the presentation did. When the wait stretches, an invisible advantage forms between two sides — the side that already knows what it wants to see. So where does improvement lie? First, a public review log. For every review in every match: the time, the decision, which element flipped it, how many seconds it took. Published centrally. This reveals no secret; it only puts the arithmetic in front of everyone. Second, a minimum retention period for clips. If review footage is deposited in a central store for a defined period after the match, anyone can return five years later and verify. Third, fix accountability to a name. The laws are written by the Marylebone Cricket Club, playing conditions by the ICC Cricket Committee, regional conditions by the Asian Cricket Council, and the tracking by a private company. Four layers, four different accountabilities. When a decision is disputed, who answers? If that question has no clear answer, every Asia Cup will end with the same grievance and every review will end in the same empty space. I stop the stopwatch here. Those twenty-seven seconds in Sharjah now live on someone's phone, in someone's memory, and in someone's argument. When the tracker freezes on the big screen again at the next Asia Cup, if the crowd sees only colours, the question stays open — in the room where the decision is made, whose permission is nailed to the door?