Six Runs, Five Runs, and the Empty Cell in the Protocol

Lord's, 14 July 2026. New Zealand 241 for 8. Fifteen needed off the last over, six balls, Ben Stokes on strike. Trent Boult's first two deliveries bring nothing. Off the third, the ball brushes Stokes' bat and skids into the leg side; as the pair set off for the second, Martin Guptill's throw back hits Stokes' bat and runs away to the boundary. Kumar Dharmasena's arms go up for six — two runs, plus four overthrows.

One signal fed into a Super Over. The Super Over finished level at 15 apiece, so the ledger moved to boundary count: England 26, New Zealand 17. The trophy went to England. I watched that night from a studio floor in Chattogram, the commentary feed on the monitor beside me, the MCC Laws open on the desk. Before the match was over I had written a line in my notebook: the problem that night was not the six runs; it was that cricket had no route to question six runs at all.

Start with what the law actually said. Law 19.8 deals with overthrows: where the boundary results from an overthrow, the runs scored are those completed by the batters, plus the run in progress if they had already crossed at the instant of the throw, plus the boundary allowance. So if two runs were complete and the batters had crossed for the third when the throw left the fielder's hand, six was correct. If they had not crossed, five was the number. Everything therefore turns on a test the law itself calls 'the instant of the throw' — a judgement made by eye, not by clock.

Eighteen years of watching matches, of breaking footage into frames, of reading documents teaches one thing plainly: Dharmasena had no replay available to him in that moment. The ICC's 2026 playing conditions contained no mechanism to challenge an award of runs. DRS jurisdiction is limited to dismissals — caught, bowled, lbw, stumped, run out, hit wicket, obstructing the field. A boundary can be checked. Whether five or six runs were earned cannot. The third umpire sat metres away with no key to unlock that question. The review architecture was built to overturn dismissals, not to audit run accounting.

The debate splits in two. One camp argues Stokes and Adil Rashid had crossed, so six was right. The other argues the second run was incomplete when Guptill released, so five was right. Dharmasena said in a 2026 interview that on the field they believed six was correct, and that watching the footage later left him in doubt. That is unsurprising. Judging whether two exhausted batters crossed inside a fraction of a second is not a task the naked eye was designed for. The larger failure that evening sat with the system's silence, not the umpire's eyesight.

Now the arithmetic. England needed 15 to win, 14 to tie. Two dot balls. Six runs off the third ball left 8 needed from three. Had five been awarded, 9 would have been needed from three — a six would have been mandatory off the final delivery. In pure numbers, the margin of one run on the umpire's signal could have pushed the trophy from England's cabinet into New Zealand's. But the spreadsheet illusion must be resisted. Batters chase a target; with 9 required, Stokes plays a different shot and Rashid runs differently. Counterfactuals never become facts — that discipline is the referee's eye.

Time to open the precedent ledger. I opened the file, and the ledger answered. On 19 March 2026 at the MCG, Bangladesh met India in a World Cup quarter-final. Rohit Sharma, on 90, was reprieved by a waist-high full toss from Rubel Hossain that was never called a no-ball. Rohit finished on 137; India won by 109 runs. I watched that match from a newsroom desk in Dhaka. Lord's 2026 and Melbourne 2026 belong to the same family: decisions outside the dismissal code, with no audit trail. The labels must be separated — regulation (Law 19.8), precedent (the 2026 incident), custom (umpires finalise calls on the field), opinion (frame-by-frame commentary). Blur them and the wrong conclusion follows.

Open the domestic file next. In September 2026, Chittagong Abahani versus Sheikh Russel KC was abandoned in the 89th minute; applying Article 63 of the BFF Disciplinary Code and two precedents from 2026, the panel deducted three points and fined BDT five lakh. There, the question was what penalty follows. At Lord's the question was what happens when the decision itself was never reviewed. The weakness in domestic governance is not the absence of sanction but the thinness of documentation. Match commissioner reports are filed, yet line-level calls such as a runs award rarely become public entries. A decision with no review holds the most power of all, because nobody ever asks it to account.

Boundary countback attracts a second misunderstanding. Many assume the clause was bad. It was untested. The provision was drafted with ordinary league cricket in mind; nobody imagined it would write the ending of a World Cup final. Pre-tournament conditions are usually stress-tested for weather, reserve days, knockout ties — but the clause destined to produce the tournament's defining image rarely is. In late 2026 the ICC scrapped boundary countback in favour of repeated Super Overs. The correction landed on the rule, not the process.

That is where my objection lives. After Lord's, the headline question was whether Dharmasena erred. He and his family received threats on social media. The document trail deserved that attention instead: what did the match referee's final report record, what note was kept of the runs award, what changed in the protocol for the next event. The referee's eye is trained on angles, not applause — and here the angle belongs to the institution, not the umpire. A single mistaken call is a personal failure. The same category of call sitting beyond verification across thousands of matches is a design failure. Lord's showed us the second, while the coverage spent months on the first.

The fix is uncomfortable rather than complex. First, a runs-award review — not a separate code, but a short channel attached to the boundary check, where the TV umpire inspects the frame at the instant of the throw and fixes the number. Second, a standing public line in the match referee's report for overthrows, penalty runs and disputed run accounting, so the record reads the same whoever is in office. Third, domestic boards publishing a summary of referee reports after each event — whether it is Article 63 of the BFF code or a BPL points deduction, one ledger. Protocol before press.

Playing conditions for the 2026 T20 World Cup are being drafted in this cycle. The tie-break rule has been repaired. The empty cell in the officiating audit remains empty. If a semi-final turns on a final over — a throw, a ball glancing off a bat, two umpires needing to confer — which clause will be ready with the answer? Will the verdict come from the law book, or from a live frame?