Zero Information Points: A Cricket Analysis Pipeline's Failure and the Journalist's Ethics of Not Inventing

Eleven at night in Manchester. Rain drawing its fingernails across the glass, and on the laptop a JSON file left open. Inside, row after row of fields — Article Title: N/A. Article Source: N/A. Information Points: zero. Entities Involved: empty. Time Sensitivity: not assessed. Source Quality: cannot be graded. Eight analytical pillars, more than twenty tables beneath them, and in nearly every cell the same sentence returning like a tide: N/A — insufficient information. My hands stopped on the keyboard. Because there is an easy way to fill those blank cells — memory. In 2026 in Rostov I watched Belgium come back from 2-0 down to beat Japan 3-2, Chadli finishing that 94th-minute counterattack, the twenty-five seconds between Vertonghen's header and the winner. My head holds hundreds of scores, spells, economy rates, all of them capable of filling any empty cell. Nobody outside would know. Only I would know that those cells were filled with inference, not with truth. On 22 June 2026, Manchester City beat Burnley 5-0 at an empty Etihad. I wrote about the sound of studs that day, about a lone ball boy's footsteps. There were numbers in that piece, but the numbers were not the story. Fifty-five thousand absent seats were the character. Tonight's empty file is a character too, of a different kind. Here absence is not an accident; it is a failure. And before you can turn a failure into a character, you have to admit it is one. Cricket coverage is no longer a single-layer craft. Scoreboard and database sit in one room, editorial judgement in another, and on top of both now sits a model-driven analytical layer. In plain terms there are three steps: extract claims from a source, verify them, then reason from them. The document in front of me is the output of step two. Step one was supposed to separate information points from an article — and an information point is a verifiable claim. A named player did this in this series; a side scored this many in the powerplay; a board decided this on this date. Those claims are the only foundation analysis has. Tonight the foundation is empty. No headline, no source, the type reads 'Unclassified', no team, no player, no timeliness assessment, no source grade. The analyst did not make a single claim. Instead they wrote, in every cell, that there is no information here and therefore no analysis. Whoever made that call did the hardest thing available: they left the table blank when a full-looking table was within reach. Why it happened is a matter of inference, but not blind inference. Three causes are plausible. The source page may have sat behind a paywall, the extraction model hitting a wall and returning an empty schema. The page may have been JavaScript-rendered, so a static fetch collected only the shell and not the text. Or the source may have been image-only or scorecard-only — no readable sentence, therefore no claim to decompose. In all three cases the result is identical: analysis received nothing. One small signal speaks loudly. The domain label reads 'cricket_world' where the contract says 'Cricket'. That single mismatch proves the step-one output never passed schema validation before hand-off. The problem is not one article. The problem is the doorway. The risk of this emptiness is sharper in cricket than almost anywhere else, because format contamination is a live hazard. A Test batting average, a one-day strike rate, a T20 economy rate — three numbers in one language, three different grammars. The word 'average' carries three meanings across three formats; the word 'experience' is an asset in one and a burden in another. An analyst reaching into memory to fill a blank cell will almost certainly mix formats, because memory stores the number and discards the label. That is why a zero count should stop the line — and why tonight's unwritten piece is, in fact, a piece. There is an older human trap here, one that lived in cricket journalism long before any model arrived. Call it helpful reconstruction. When a person sees a blank cell, instinct says: I know this, I have watched this player for a decade, let me fill it in. The impulse is generous. The outcome is toxic. A record pulled from memory has no source, and a number printed without a source has no way back. I learned the game from the stands, not from the scoreboard. In 2026, after a second ACL tear ended my semi-pro career at Stalybridge Celtic, I talked my way into a junior writing job at Northern Pitch. My first big assignment was Salford City's 3-2 National League North win over York City, two goals after the 90th minute, twelve hundred away fans. I ignored the scoreline and wrote about a father and son hugging in row 14. The piece was shared eight thousand times. That taught me something that is clearer tonight than ever: the absence of data and the absence of truth are not the same thing. The embrace in row 14 exists in no database and no expected-goals metric, yet it is observation — seen, noted, written. An average pulled from memory is not observation; it is construction. Between the two runs a single line: source. The embrace has my eyes as its source. The remembered average has nothing. A notebook-less trip to the ground means seeing half a match. That habit taught me that absence can itself be evidence — but only when you have seen the absence yourself. I could write about empty stands because I stood in them. I can write tonight about an empty schema because I opened it. A blank cell I never saw is not mine to fill. So the pipeline needs a hard gate, not a polite suggestion. If the information-point count is zero, step two stops automatically, the event is logged as a data-quality incident, and the log reaches the pipeline owner. Batch-level suspicion matters just as much: if one article carries this empty-schema signature, other articles fetched the same way are probably infected. A one-off error and a systemic error need different medicine. Cricket journalism's own old disease rhymes with this almost exactly. Filing from the press box off a television screen. Assembling quotes without opening the dressing-room door. Writing 'he said' when what you mean is 'I assume'. None of that was invented by a machine. The machine only made it faster and larger. What was a human disease is now spreading at scale. This is where the limits of data and the limits of journalism meet. Transfer-market models overrate youthful potential and underrate dressing-room chemistry. Yet chemistry decides who stands beside whom under pressure, who wants the ball and who does not. A model cannot hold that, and what a model cannot hold it treats as zero. The five-substitute rule shows the same thing from another angle: deep squads can turn the last twenty minutes into a slow war of attrition, and no simple depth index captures that advantage. Analysis that names its blind spots is useful. Analysis that covers them with inference does damage. I don't chase narratives; I follow the people who leave footprints in the noise. That following has one condition — the footprint has to be real. You can draw a footprint from imagination, but then it is not following. It is false witness. Which raises the uncomfortable counter-question. Everyone says the machine will invent and ruin cricket. But sitting with this document, the real risk looks different. A machine can be gated; at zero, it stops. The danger sits with the human who sees a blank cell and says, I know this. There is no gate in front of him, because he is the gate. And a person cannot be his own gate unless he keeps asking: where did I get this number? The second uncomfortable point: silence is not neutrality. Empty space does not stay empty. Rumour, guesswork and 'I heard' rush in. Readers want information; if we say there is none, they go where confidence is louder than evidence. So the answer is not silence but disclosure — a recognised form, the no-data note, stating plainly what was not found, why, and what would change if it were. Cricket has written this form for years whenever rain washed out a day. This time the paper stayed dry; the fetch got rained on. The third point is professional. Publishing a pipeline failure means publishing your own weakness. Institutions dislike it. Brands dislike it. Editors dislike the phone call. But what is the alternative — a table that looks complete, every cell confident, not one of them sourced? Cricket readers can count. One day one of them will ask where the number came from. If there is no answer that day, the failure was never in the pipeline. It was in trust. The next tournament cycle will bring more volume: more matches, more series, more franchises, faster files. Moving at that speed without a gate means sending an invitation to inference into every blank cell. The question is not technological. It is habitual. Before the next World Cup cycle, will we actually build the gate — or will we fill a few more empty cells with beautiful sentences and convince ourselves nobody noticed?