No Ledger, No Ruling: Where the Chain of Evidence Breaks in Cricket Reporting
**मुख्य उत्तर**: Stage-1 ऑडिट में सभी फील्ड खाली होने का अर्थ है कि स्रोत से कोई सत्यापित तथ्य नहीं निकला, इसलिए उस पर गहन विश्लेषण संभव नहीं। सही कदम है कच्चा पाठ दोबारा निकालना या मूल लेख सीधे उपलब्ध कराना, क्योंकि खाली रिकॉर्ड पर लिखा हर निष्कर्ष मनगढ़ंत होगा। **मुख्य तथ्य**: - 2017 चैंपियंस ट्रॉफी के 15 मैचों के 18 DRS रिव्यू दर्ज हुए: 9 बरकरार, 6 पलटे, 3 अंपायर कॉल। - ICC प्रावधान के अनुसार गेंद-ट्रैकिंग अनुमान 50 प्रतिशत से अधिक होने पर मैदानी फैसला बरकरार रहता है। - 2020 इंडियन प्रीमियर लीग की 60-मैच ऑडियो लॉग परियोजना में 27 सुनाई देने वाली अपीलें दर्ज हुईं। - मैच रेफरी का Level 1 और Level 2 अपराध अलग श्रेणियां हैं, जिनके सुनवाई मंच और अपील मार्ग भी अलग हैं। - विफलता की तीन वजहें: खाली मूल पाठ, सूची पेज को लेख समझना, कटे हुए JSON का चुपचाप खाली ढांचे में बदलना। **स्रोत उद्धरण**: आंतरिक Stage-1 एक्सट्रैक्शन ऑडिट रिपोर्ट; ICC प्लेइंग कंडीशंस (DRS प्रावधान), 2023 संस्करण; 18 जून 2017 को लंदन के ओवल में खेला गया ICC चैंपियंस ट्रॉफी फाइनल; 28 सितंबर 2020 का इंडियन प्रीमियर लीग मुकाबला। **संबंधित प्रश्नोत्तर**: प्रश्न: क्या Domain Label अकेले विश्लेषण के लिए पर्याप्त है? उत्तर: नहीं, यह केवल शब्दावली और पृष्ठभूमि देता है, कोई सत्यापित दावा नहीं। प्रश्न: खाली शीट से ज़्यादा खतरनाक क्या है? उत्तर: आधी भरी शीट, क्योंकि वह अनुमान को न्योता देती है और 'सूत्रों के मुताबिक' जैसे दावों को जन्म देती है। प्रश्न: दोबारा प्रयास से पहले कौन सी तीन जांचें ज़रूरी हैं? उत्तर: कच्चे पाठ की लंबाई, पेज का प्रकार (लेख या सूची), और मॉडल की वापसी का पूरा और पार्स-योग्य होना।
Eleven-forty at night on a Delhi digital sports desk. An audit sheet sat open on the screen with eight columns — title, source, type, one-line summary, author's stance and purpose, information points, entities involved, time sensitivity, source quality. Against all eight stood the same answer: not applicable. One box was filled — Domain Label: cricket_world. That was all. No fact, no number, no quote, no event. Only the name of a world, not a single story from it.
A deadline stood in front of me. Instinct offered the usual route: work with what you have. Two or three general observations, a couple of old examples, a confident tone, seven hundred words ready to file. I shut the laptop and pulled out the spiral notebook in which, at nineteen, I had logged every DRS review from the fifteen matches of the 2026 Champions Trophy. Eighteen reviews: nine upheld, six overturned, three umpire's call. Every line carried the over, the ball, the batter and the third umpire's name. That notebook had come back to remind me that in a trade whose currency is evidence, a story begun on a blank page never gets filed.
The strength of any cricket ruling comes not from its plausibility but from its paper trail. ICC playing conditions carry a written provision for every dispute, and every provision carries a source — the on-field umpire's report, the third umpire's protocol, the match referee's sanction, the broadcast feed as exhibit. The noise around umpire's call in DRS is answered not by sentiment but by a number: if the ball-tracking projection shows more than fifty per cent of the ball hitting the stumps, the on-field decision stands. That is not a loophole; it is a defined margin. Anyone who calls it a loophole has formed a verdict before reading the clause.
Match referee proceedings are even stricter about categories. Level 1 and Level 2 offences are different charges, heard by different bodies, with different appeal routes, and any mention of a sanction must name the body speaking. There is no such thing as 'the authorities said' in cricket's language; there is a match referee's report, a disciplinary committee's order, a tribunal's finding. Watching from the stands across several seasons taught me the same lesson the stump mic teaches: what you hear is evidence, what you are shown is an edit.
So when that sheet came back empty, the question was not what to write. It was that every decision has three parts — what happened, what entered the record, and what was decided on the record's strength. All three were missing. Only a label survived, and a label can supply vocabulary and background: tournament, team, format, ranking system. A domain label can give you a lexicon, not a single claim.
There are three failure modes, and each maps onto cricket's own evidence system. The first is an empty body text — anti-scraping defences, JavaScript-rendered pages, paywalls, or a stub with only a headline. This is exactly a DRS review with no UltraEdge spike and no ball-tracking generated at all. Without an exhibit the third umpire says nothing; the on-field call stands. The second is mistaking a list page for an article page. Navigation, headlines, timestamps, teasers are not the article. This is the broadcast director cutting to a different angle and the viewer taking that angle for the whole truth. The replay shows the angle; the ledger shows what it cost. The third is the most dangerous: a model response truncated mid-output, a JSON parse failure, and a system that silently returns an empty structure. No error, no alert, just N/A. A match referee's report filed without a clause number exists on paper and vanishes in effect.
What stings most here is not technical but professional. A half-filled sheet is dangerous because it invites inference. Drawing a conclusion from partial facts is the same offence in journalism that bias is in umpiring. An empty sheet is at least honest — it states plainly that there is no record, therefore no ruling. No decision is stronger than the paper trail behind it. My first VAR byline began with a roar and ended with a ruling; at twenty, that piece taught me that the gap between 'clear and obvious error' and 'umpire's call' is written in a protocol, not in an atmosphere.
I did not file that night. I logged three things instead, and they belong in every such situation. First, the length of the raw text: if it is zero or a few hundred characters, extraction has failed and analysis is not even a question. Second, the page type: article or listing, because a listing page contains no claim. Third, the model's return: a truncated answer parses into an empty structure that looks like a complete one. After those three checks the fault is located in the pipeline, not in the news.
There is a human cost attached, and it belongs before the paperwork. The reader who opened that link did not want a batter's score. They wanted to know where an over-rate penalty moved a points table, or how a Level 1 sanction on a bowler altered his team's playoff arithmetic. Any article written over an empty record misleads that reader, and a misled reader does not come back for a second helping of trust.
There is an inverted reading of the whole episode, and it is the more useful one. A completely empty sheet is the safest state. The most dangerous sheet is the one with the summary filled, half the information points populated, and the source-quality box left blank. There the writer believes he holds material when he holds only a shape. That is the condition in which 'according to sources' is born, and that phrase generates more corrections in cricket coverage than any other. Appeals arrive late; that is why I keep the notebook open after the whistle.
I reopen the old DRS ledger to see which decision still survives contact with its own rulebook two seasons later. Apply the same standard to reporting. If a claim does not survive a second audit of its own source record, it should never have been written.

The question ahead is whether we can adopt a minimum viable record — at least three verified facts, one named source, one date, and one detail the reader did not already know. The day that standard takes hold, an empty sheet will not quietly return N/A. It will raise an alarm. Which is as it should be: a file with no evidence belongs in an alarm, not a courtroom.
