The Cricket Asia Story That Arrived With a Tag and an Empty Body

At 11:40 on a Chennai night, a record sat open on a newsroom screen. The system had already labelled it — cricket_asia. Every line beneath that label was empty. The one-sentence summary, blank. Author stance and article purpose, both parked in the "not applicable" column. The entire information-points section, deserted. The instruction to identify entities was present, but there was nothing left to identify.

The colleague at the desk turned to me and asked, "So what is the story?"

I had no answer, and that was the most honest answer available that night. Twenty-one years of this trade have taught me to leave the ground and sit in the stands, because that is where answers live — with the woman in Block J who handed her umbrella to a stranger in the rain. That night the stands were a distant idea. There was no ground either. There was a tag, and behind the tag, nothing.

This is not a match report. It is the story of a report that expired before anyone wrote it.

Cricket coverage in Asia now runs at three different speeds. The first is the board's — press releases, executive committee decisions, selection lists. The second is the agency's, which sends four paragraphs and one photograph from the ground. The third is the speed nobody writes about: the pipeline that collects all of it, labels it, and pushes it toward the reader.

The third speed has become the fastest of the three over the last four years. Franchises run their own channels, boards run their own outlets, and in between sit the aggregators who publish three hundred stories a day. An aggregator's job is not to write the story. It is to recognise it — to decide that this is cricket, that this is Asia, that this belongs in this particular bin. Recognition is cheap. Understanding is expensive.

That asymmetry was visible on the screen that night. Classification succeeded, extraction failed, and the system raised no flag. The desk went quiet, so I followed the noise.

Three separate things are happening here, and they need separating.

First: a tag is not information, a tag is an address. Any system can look at a URL, a domain or a headline and conclude that this concerns cricket in Asia. It is telling you exactly as much as a postman reading the address on an envelope. The envelope is correct; that does not prove there is a letter inside. That night the envelope was correct and the inside was empty.

Second: the failure was silent, and that is the actual story. What was missing from the pipeline was not technology but a condition. No stage insisted that the summary be non-empty, that information points could not be zero, that the entity list must contain at least one name. The moment that condition exists, the record gets flagged as failed and never reaches a desk. Because the condition did not exist, it arrived as "empty" — and the difference between empty and successful is invisible to the reader.

Third, and the most expensive: an empty record still travels. Had I insisted that night and written something, I would have had to invent a stance, invent information points, invent the relationships between institutions. The text would have looked complete from the outside. Its root would simply never have touched a ground, a bus, a corridor. And the reader would have had no way to check.

In all my years of watching this game, the two most reliable things have been a date and a place. Which day, which gate, which block. "This week" is not a date; it is a vagueness that gets read as fact. An empty record is not dangerous because it lies. It is dangerous because, despite being incomplete, it is treated as whole by the next link in the chain.

The effect on Asian cricket is direct. Coverage inequality in this region was already severe — the big series involving India, Pakistan, Sri Lanka and Bangladesh draw ten correspondents each, while matches involving Nepal, Oman, the United Arab Emirates and Hong Kong routinely finish without a single reporter present. Where there is no human, the pipeline fills in. And the pipeline applies a tag even where it has read nothing at all.

The risk is not hypothetical. Anyone who follows associate cricket knows the scorecard arrives, but the story behind the scorecard — which fast bowler came out with tape on his knee, which captain chose to bowl after winning the toss because he had read the dew — never does. The tag travels. The muscle does not.

The reflex is to blame artificial intelligence. I think that reflex is wrong, because it conceals the incentive that created the problem.

The real point is that the tag has become the product and the article the cost. In a market where the advertiser prices the words "cricket" and "Asia," the tag carries value and the text does not. The record on that screen was complete from an advertising standpoint. It was deficient only from a reader's.

The second point is one where I differ from several colleagues at my own desk: an empty record is honest. A record that is seventy per cent filled and thirty per cent guesswork is far more dangerous. Emptiness gets caught. Guesswork does not — it sits exactly the way a real sentence sits, and the next time somebody writes about the same event, they read it as a source.

The same logic applies to the data now walking into dressing rooms. An analyst who draws conclusions from numbers without watching the rhythm of the match makes precisely this error — he mistakes the tag for the information. Strike rate will tell him a batter went slowly. It will not tell him the man had not drunk water in fifteen overs and his back was seizing. The number is the envelope. The letter is written on the field.

The lesson here is editorial, not technical. Adding a condition to the pipeline — summary non-empty, entity list non-empty, every date absolute — is not engineering work. It is the same work an editor used to do when he sent a manuscript back with "where is the source?" scribbled on it.

For the reader the question is simpler. The next time you open a story about Asian cricket, look for one thing: is there a human being in the text? A gate, a block, a date, a name. If there isn't, you have not read the story. You have read the envelope.