Nine Dimensions, Zero Facts: Auditing an Extraction Failure in Indian Esports Reporting

That Tuesday in September 2026. 8:40 p.m. On the studio desk lay a piece of paper — the contract of a nineteen-year-old from Rohini, carrying a force-majeure clause written in the language of a different sport. PUBG Mobile had been banned under Section 69A on 2 September. Nine days of calling had produced fourteen organisations and forty-one players. What I read on air that night was not a statement. It was the clause, line by line, with his permission.

That file had names. It had dates. It had stipend figures. It recorded which organisation had stopped paying in which month.

Last week, a different document opened on a screen. Nine dimensions — patch and meta, tournament format, team and player, regional landscape, club finance, rules and governance, risk profile, public narrative, industry transmission. Every row carried its label: Meta Direction, Format Type, Roster Phase, Compliance Risk Level, Transmission Map. Every value carried the same sentence: N/A — insufficient information.

The scoresheet exists. The score does not.

The first call wasn't to the analyst. It was to the archive. Because a nine-dimension document is not the story — it is the last link in a chain that begins with an article, a source, a timestamp and at least one hard fact. This time the first link came back empty.

To understand why that matters, you have to understand how the Indian esports record is actually built. There is no wire service. There is no accredited beat. There is no institutional press corps to certify that a roster move is confirmed. What exists is four things: an agent's message trail, an org's press release, a league registrar's PDF, and — far too often — somebody's Discord screenshot. The first three are source tiers. The fourth is a habit.

In 2026 I walked out of a 9 p.m. sports slot at a Delhi FM station and started The Window with four hundred subscribers and one rule: report the deal, not the mood. That October I watched eight matches of the FIFA U-17 World Cup at Jawaharlal Nehru Stadium and tested the method there. An ISL club had split a loanee's wages 70-30 with the parent club while calling it a straight loan in its own press release. I had the agent's message trail and the club's release, both dated, contradicting each other. The club amended the release in three days.

That episode is the cleanest example of how the work functions, because there was no magic in it. Two documents, one date, one contradiction. And on the day one of those documents fails to load, the story starts looking 'clean' — which is the centre of this entire matter.

Now the pipeline. Esports analysis runs in two stages. Stage-1 reads an article and extracts: title, source, article type, one-sentence summary, author stance, a list of information points, entities involved, time sensitivity, source quality. Stage-2 takes those extracted facts and runs nine analytical dimensions. Crucially, Stage-2 has no direct access to the raw article. It is entirely dependent on Stage-1's notes.

Which produces a hard ceiling: Stage-2's accuracy can never exceed Stage-1's accuracy. It is a ceiling, not a floor. And this time Stage-1 returned an empty 'Information Points' field — no title, no source, no entities, no timestamp.

Only two paths exist from there. Fill the template from general priors, write confidently, and never let the reader learn the foundation was hollow. Or state plainly that no finding is possible and specify exactly what would produce one. The document took the second path. Professionally, that is precisely what an auditor should do — and precisely what Indian esports coverage almost never does.

Start with the distinction the whole argument rests on: 'checked and absent', 'not checked', and 'checked and could not determine' are three different things, and Indian sports journalism collapses all three into one sentence.

Everywhere the document says 'N/A — insufficient information', it is using the third category. Saying 'the meta did not shift because the patch was minor' would be the first — an affirmative finding. Saying 'patch information was never supplied' is the third — a refusal. The distance between them is enormous, and reporting routinely erases it, because 'N/A' reads as weak and 'no change' reads as strong.

There is another line in the same document that carries its entire credibility. The governance section does not rate compliance risk 'Low'. It rates it 'N/A'. That is a small thing and it is everything. 'Low' would mean the check was run and came back clear. 'N/A' means the check was never run. In Indian esports the standing habit is to declare an organisation clean because no match-fixing allegation was printed — the same logic as calling a player clean because he was never tested.

The same document says of unpaid wages that their status is indeterminate, not confirmed absent. That distinction is my entire beat. In the 2026 series we knew one nineteen-year-old was owed three months. We did not know about the other forty, because we had not asked. 'Nobody is owed' and 'we did not run the ledger' are different sentences, and the newspaper makes them one.

Now the question an auditor asks first: what shape is this failure?

Every label is present. Every value sits at default. That pattern does not belong to an article that genuinely contained no facts. It belongs to a parsing or scraping failure, or to an upstream template that was never populated.

The consequence splits into two different repairs. If the failure is content-shaped — the article really had nothing — the repair is editorial: there is nothing to report, close the file. If the failure is template-shaped — the plumbing broke — the repair is engineering: re-run the fetch, check character count and encoding against the source URL, confirm whether the raw text ever arrived.

My own analogue is the 2026 loan. Had the club's press release loaded and the agent's trail not, the story would have read as a straight loan. The error would not have been in the reporting. It would have been in which document got fetched. The reader sees the same clean story either way, and one of them is false.

Which is why the most honest line in the document concerns not the analysis but the diagnosis: the failure looks systematic, template-shaped, rather than content-shaped. One bad fetch is an accident. Every field empty and every label populated is a design problem.

The nine-dimension framework itself is sound. Its failure is not that it produced nothing; its failure is that nobody supplied what it needed. Each dimension in the document carries its own minimum activation input — game title, patch version and one concrete balance change for the meta; organiser, format and series length for the tournament; one name and one event type for the roster; one club and a described deal for finance.

And here is the precondition Indian esports ignores: the game title.

The framework's first question is which title — LoL, Dota 2, CS2, Valorant, Honor of Kings — because tournament systems, metrics and business logic shift fundamentally across them. In India that gap is stark. BGMI is mobile-first, publisher-operated, and lives under a heavy regulatory shadow. Valorant runs on Riot's franchise-lite structure. CS2 belongs to Valve and its ecosystem sits with third-party organisers, ESL and BLAST. The same roster move carries three different economic meanings.

A blank title also disables the framework's own corrective — that a region can be Tier-1 in one title and a wildcard in another. Worse, if the title is unknown, nothing confirms that an item filed under the esports label is esports at all. A mislabelled item enters the corpus undetected.

It has happened before, and the label decided the outcome. In September 2026, Nikhil 'Forsaken' Kumawat was caught cheating at the eXTREMESLAND Asia finals in Shanghai and OpTic India collapsed overnight. Much of the Indian media treated it as a 'gaming' story, a gadget-desk subject. I put it on a mainstream Delhi radio show as an esports integrity question and gave three CS:GO players an unedited segment to describe qualifiers nobody had ever audited. The label changed, the desk changed, the question changed. Had it stayed a 'gaming' story, we would still have no record of a qualifier audit.

The third gap is source hierarchy. The order is fixed: official tournament data, then vertical media, then community rumour. On the day the source field is blank, rumour and official data occupy the same tier — and on this beat, sourcing is the entire job.

My trust ledger carries one rule per entry: role, never name. Agent, club official, league registrar. Never a name, because for the ages and the staff sizes we deal with, a printed name can damage a person's whole income. On the day the source field is blank, that discipline becomes unprovable, because nothing establishes whether a detail came from three sources or one screenshot.

The rule has not changed since 2026: I speak when I have three. Not two — three. Which is why, in 2026, when I reported Indian mobile esports' first buyout figure — a nineteen-year-old fragger moving from Tier-2 to Tier-1 for six lakh rupees on a two-year deal with a nine-lakh release clause, inside the BGIS 2026 circuit with its one-crore prize pool — two rival organisations called to argue about the number. That argument was confirmation, because the number came from their own paperwork. Had it come from a screenshot, the argument would have been about defence, not value.

The fourth gap is the timestamp, and it does the fastest damage. Information decays at different rates. Patch news goes stale in days. Transfer news goes stale in days. Tournament results in weeks. A document with no publication date can be correct and arrive wrong, because the reader assumes today's news while holding last month's. In the regular season that is especially dangerous: movement is continuous and the story does not stop when the window closes.

And the part the document gives least room to, and should have given most: who pays.

Not the org. Not the analyst. The boy in Rohini whose contract became an empty file. If the record is hollow, the stipend document is never built, the force-majeure clause is never questioned, and the next time an organisation tells a nineteen-year-old 'paperwork later, play first', he has no precedent to point at. The real cost of this audit lands on the person with the least leverage in the deal.

This is also where I distrust my own reflex. The structural auditor asks payroll first, sponsor dependency second, buyout third — and the player's actual situation last. Paperwork looks cleaner than people, so it is easier to stop there. But a blank document lies harder than any filled one, because it pretends to exist.

Which opens the counter-intuitive reading.

The danger we fear in esports journalism is fabrication — printing something that never happened. The larger danger is duller: inherited emptiness. A document shaped like a report, with correct terminology, risk flags and a disclaimer, containing not one fact. It passes review because it looks like work. Thirty-five pages of nine-dimension tables read as more professional than three paragraphs of honest uncertainty — and that is the whole deception.

Second, and fewer will agree: a published null result is always worth more than a filled template. We have spent a decade demanding paperwork from organisations — show the contract, show the stipend record, show the buyout clause. The same standard now belongs on our own documents. If we audit 'world championship' against the bracket and 'historic medal' against the event's actual status, we must audit our report against its extraction. Otherwise the asterisk school applies only to other people.

Third, about the crowd. After Germany's group-stage exit in 2026 I scrapped the column and opened a ninety-minute phone-in. Sixty-one callers came, and they were not talking tactics — they were talking inherited club loyalties. The lesson: the crowd already suspects. The job of a crowd-calibrated empath is not to inflate that suspicion but to hand it receipts. An empty extraction hands the crowd nothing — it returns their own priors, which they have already heard.

So the next domino is not a transfer. It is the extraction layer, and the fix is cheap: four fields that can never be null — game title, source with organiser or publisher tier, publication date, and at least one concrete information point. Everything downstream, from patch to transmission, flows beneath those four.

Until that happens, we live with an uncomfortable fact. The Indian esports record is no longer built in reporters' notebooks. It is built in a pipeline. And when a pipeline builds the record, the question stops being whether the story is true — and becomes who audits the pipeline, and whether that audit ever reaches the kid whose name is currently buried in an empty column.