Format Is the First Gate: An Empty Source, a Full Table, and the Discipline of N/A

At 11:40 pm, a wire item opens on a desk in Kolkata. The title field is blank, the source field reads N/A, the one-line summary is empty, and the information-points list holds zero items. On screen the template stands fully built — eight dimensions, ready tables, ready headings. The only thing missing is the cricket to fill it.

This is a moment I have been trained for since 2026. That year's IPL final saw Rohit Sharma's Mumbai Indians beat Steve Smith's Rising Pune Supergiant by one run, defending 129/8 against 128/8. During a wide-and-DRS check in the 19th over I live-posted a 14-tweet thread from a room of twelve friends — pausing frames, citing Law 21, stamping every post. The lesson that night was simple: the decision arrives before the replay. Tonight is the inverse. The decision — the template — has arrived. The replay, meaning the facts, never did.

On a stringer shift that gap shows up daily. At the closed-doors Bengal T20 Challenge at Eden Gardens in 2026, match seven between Mohun Bagan and East Bengal produced a square-leg run-out given not out and then reversed after a four-minute consultation. I captured the umpire's on-mic call and six post-match quotes, filed 900 words, and got a one-paragraph clarification out of the CAB. That night I added a rule to my own desk: every controversial call carries a follow-up box stating plainly what is confirmed, what is awaiting a statement, and what is unverified.

That box is the first thing needed tonight.

The null signature on this item points at a broken pipeline, not an empty story. Any cricket story with a real title and a real source normally yields three to five extractable points — which format, which team, which venue, which decision, which date. When the title is present-but-null, the points list is empty and every field reads 'not assessed', the likeliest cause is a paywall, a JavaScript-rendered page, an image-only graphic, or a source whose encoding the extractor dropped. This is not a failure of the news; it is a failure of the supply chain.

The second thing logged in this payload is taxonomic. The returned domain label is cricket_asia, while the contract specified Cricket. cricket_asia is not a standard taxonomy node; it is a geography-scoped tag. It is not evidence of content, it is a routing artefact. Treating it as a fact is the same error the cricket desk commits every day — mistaking a headline for a story.

And here the first gate closes: format. Format is cricket's first and non-negotiable gate, because every metric's benchmark is built from it. A batter's strike rate of 145 is elite in ODI, ordinary in T20 and meaningless in Test, where strike rate is not the comparison at all — average and balls faced are. A bowler's economy under seven is excellent in T20 and irrelevant in a first Test spell. And the oldest error of all: strike rate means runs per 100 balls for a batter and balls per wicket for a bowler. Printing the term without saying which is plain carelessness.

Behind that gate stands a second condition: the nature of the match. A dead-rubber bilateral and an ICC knockout are not the same thing. In one, defeat costs nothing; in the other, a tournament ends. And separating result from process requires stripping toss and DLS luck, which requires knowing the match conditions. The empty payload offers no nature, no venue, no weather, no DLS reference.

The 2026 final illustrates the gate. In a T20 where 129 and 128 were the totals, bowlers' economy rates look Test-like, but that is not evidence of Test cricket — it is the story of that pitch on that day. Without fixing format I cannot draw a single conclusion from that match, which is exactly why writing any player metric on an empty payload would be a category error.

Pause on the entity line. The payload's entities field explicitly instructs that names be drawn from the information points above, and those points are empty. That does not mean players were not extracted; it means the entity set is provably empty. In journalism that distinction is life and death. 'No name found' and 'no name extracted' are two different statuses, and writing them as one is a lie to the reader.

Protocol memory hurts more. In 2026 the ICC abolished the soft signal on catches — the on-field umpire no longer offers a preliminary out or not out, and the third umpire now needs clear evidence. The effect on the archive was immediate. A 2026 clip and a 2026 clip of a similar catch cannot be read the same way, because the law changed in between. The rulebook is a living document, and a reporter who does not read it with dates attached ends up delivering a new verdict on an old clip.

This is where the VAR question arrives, and I will hold it to one sentence: football's review is not a finite resource held by the team, while cricket's two reviews are finite and survive on umpire's call — so the two systems mean different things by 'correcting an error'. I took the VAR question to a cricket ground and waited; the answer was that in cricket's economy a review is an expenditure, and in football it is a right.

The language of risk has a trap in it. Every field here reads N/A, and the easiest mistake is to read N/A as low risk. An unassessed risk is not a low risk. Silence on the anti-corruption unit, on fixing, on odds, on government interference is not a clean chit. Silence in an empty payload is not exoneration; it is just silence.

Then there is the status line. Every cricket story on my desk runs on one of three statuses — confirmed, awaiting statement, unverified. Nothing moves up a tier without a second source or an official document. Tonight's item sits at the third tier, and a fully populated template does not move it to the second. Complete formatting and actual evidence are two different things, and conflating them is the most expensive habit in this trade.

Now the uncomfortable angle. Readers do not actually want an empty table. The market buys confidence, and N/A does not sell. A paragraph stuffed with an invented scoreline, an invented auction figure and an invented player name will be read more widely than an honest table — that is the demand-side failure. I accept it and still write N/A, because fabricated cricket analysis is more dangerous than empty analysis: it can be quoted and it cannot be checked. Slow-mo does not settle arguments; it gives them better frames — but a frame only helps if something happened in front of the camera.

The second uncomfortable part: a real story may be buried in this mess. A story with not one player named is often not a performance story at all, but a board, event or commercial one — Asia Cup hosting, an ACC schedule, a member board's contract. That is a weak signal, not a finding. But if it holds, the story belongs to cricket's money and calendar, and it will travel through the same status line.

The way forward is clear and dull. Re-fetch the raw URL, check for paywall and JavaScript rendering, reconcile cricket_asia against Cricket in the taxonomy, then re-run Stage-1 — with at least three points and one name. The day those three points land, all eight dimensions fill, because the scaffold already stands and will not need rebuilding.

The question is not how to write a report on an empty source. The question is whether, on the day the source is full, we will have the nerve to print the evidence under every line of our own table.