A Blank Template That Told the Whole Cricket Story

There is an old habit in the Delhi press box — flipping a page, the finger pauses at the edge where the ink never reached. Last week a page like that crossed my desk, only it wasn't paper: it was a Stage-1 analysis sheet. Domain: cricket_world. Everything else blank — summary empty, stance N/A, purpose N/A, zero information points, and under 'entities' the instruction 'identify from the information points above', which is a note to itself, not an answer. In twenty years I have filed thousands of cricket reports, but this was the first time a report arrived with no news in it, only a reserved space where the news should have been.

My first thought was that the system had glitched. Then I understood: this is not an article, it is an artifact. The subject of the analysis is not a cricket match but the process that was supposed to fill this sheet and didn't. For any cricket writer, that distinction is everything. If a scorecard reads 0/0 with the innings score also blank, you are not reading a match — you are reading the first page of the scorebook.

Look at the one surviving signal: cricket_world. Every other field was empty, yet Article Type came back 'unclassified' while the domain label came back confident. That is the real story. In cricket, deciding the domain is a bigger task than deciding the type — match report, preview, opinion column, board governance, profile, rankings listicle all sit inside cricket. So when the type stays unresolved but the domain is nailed down, the meaning is plain: whoever said 'cricket' never read the body text. The label came from metadata, a URL slug, or a single keyword.

I remember the 2026 IPL mega auction in Bengaluru, 578 players on the list, numbered paddles going up. In that room one thing always came first — the name. The name told you who the bid was for, even before the batting order was set. This sheet is the same: the name came through (cricket), the batting order did not (article type). And the press box's oldest disease is exactly this — mistaking a headline for a story.

The empty field that costs the most

One field in this sheet is the most expensive to leave blank — time sensitivity. It read 'not assessed in Stage 1'. In cricket that is no minor column. A match report is measured in hours — a preview is worthless after the toss, a report is stale the moment the game ends. A board decision lives for weeks; a profile is read for years. If you don't know whether you are holding an hours-old story or a years-old one, how do you choose the next step?

Without the article type, reading 'stance' is dangerous — a match report's flat tone and an opinion column's flat tone look identical but mean opposite things. Neutrality is a duty in one and cowardice in the other. And source quality? The sheet carried no publisher, byline, date, or URL, though the field asked to 'judge from the source fields'. There were no source fields. Cricket is a domain thick with aggregation and betting-adjacent SEO content — provenance is the only real discriminator between fact and fabrication, and it was entirely absent.

The biggest risk: a well-filled lie

Send this blank sheet to the next stage and what happens? The system will try to fill the gaps — teams, players, a whole narrative. With no evidence. This is the risk I felt during the 2026 Delhi Test, when players wore masks through the smog and Sri Lanka's Suranga Lakmal left the field vomiting. Reports ran that day describing things that never happened on that ground. I filed no 800-word match report that evening — I recorded 47 voice notes, because the microphone told a truth the desk's hurry could not. The rule holds here too: what was not read cannot be written.

The remedy: re-supply the raw input — full body text or the canonical URL. The usual cause is a paywall, a JS-rendered page, a truncated fetch, or headline-only input. Retry the classifier at a lower threshold with six to eight mutually exclusive cricket genres and a confidence score on each. Most importantly, force minimum extraction from headline and lede alone — a title still yields entities and a date. Zero output from non-empty input is a bug, not a result. Capture provenance — publisher, byline, date, link — as first-class fields. And replace instruction strings in the template with computed values or an explicit null, so blank output can be told apart from an unfilled template.

The last word

In the past decade I have learned to hear cricket through a microphone. When a voice note carries only wind, that too is information — it says the stadium is empty. This sheet taught me the same lesson from the other side. Zero information points is still information, provided you have the nerve to accept that nothing here was read. The danger begins when the next system, in its hurry to fill the silence, invents one more story. Which leaves the question — are we reading the news, or the empty box left where the news should have been?