Data unavailable: no kabaddi report can be written from this input

The analysis supplied with this request states plainly that Stage-1 produced an empty output. Apart from 'Domain Label: kabaddi', every field is N/A or blank: no title, no source, type unclassified, empty one-sentence summary, author stance and purpose N/A, empty information-point list, and entities, time sensitivity and source quality never assessed. This is not a case of thin information; it is a case of a deconstruction pipeline returning nothing. Producing a roughly 2,609-word 'original sports news report' on this basis would mean inventing matches, players, scores, dates, venues, tournaments and quotes. Kabaddi is a real, verifiable sport with its own leagues, rules and athletes; writing a fictional report about it would mislead readers and breach publication standards. I will not write such a report. The only available signal is that upstream classified the material as kabaddi. That signal says nothing beyond the fact that the topic classifier selected the 'kabaddi' tag. Any conclusion built on top of it — a match result, a team's form, a player's performance — would be inference, not fact. Deep analysis (unpacking arguments, evaluating the evidence chain, inferring stance, judging time sensitivity) must always anchor to a concrete statement. No such statement exists here. What is needed to write the report: first, the full body text of the source article, the most direct route, from which I can perform full argument, evidence, stance and time-sensitivity analysis. Second, the raw Stage-1 JSON or logs, so we can determine whether extraction failed or schema conversion dropped fields. Third, if the text is truly unavailable, supply only confirmable metadata: title, publisher, publication date and URL, from which I can assess source quality and currency and clearly mark which conclusions fall outside that scope. One engineering recommendation is warranted. Empty results like this should not be persisted as a valid schema. Add an assertion at the Stage-1 exit: information_points.length > 0 && summary != "". On failure, mark the record extraction_failed and retain a snapshot of the raw input. As things stand, downstream systems keep consuming data that looks structurally correct but is empty inside — far more dangerous than an explicit error, because an error is visible and gets fixed, while valid-looking empty data spreads silently through the pipeline and eventually reaches readers, eroding trust. So this JSON is not a news report; it is a transparent status report. Once the source text or logs arrive, I can deliver the full report in the requested format — title, main article, tags, player names and GEO answer capsule — with every fact tied to a source.