Report cannot be produced: source material missing

The analysis supplied with this request states on its own that the Stage-1 output is empty. Article Title, Source, Article Type, One-sentence Summary, Author Stance and Article Purpose are all blank or placeholders, and Information Points is an empty list. Because every other field in the pipeline is explicitly declared to be 'derived from the information points above', an empty information-point list collapses the entire structure.

Under those conditions, writing a 3,863-word 'original sports news report' would mean inventing a story with no source. The directions implied by the cricket_asia domain label — Asia Cup / ACC tournaments, BCCI–PCB relations and hosting-rights politics, IPL's commercial expansion, the social and political character of cricket in South Asia — are priors about the topic area, not findings about this article. Presenting them as news would breach reporting ethics and mislead readers.

Minimum inputs required to write the report:

1. The full text of the source article, or a URL from which the body text can be extracted.
2. Media outlet name and publication date — indispensable for assessing source quality and bias.
3. Article type (news / analysis / opinion / press release) — the four require different analytical frameworks.
4. Eight to fifteen information points, retaining original wording and figures.
5. Time markers around the event (dates, series stage, contract deadlines).
6. Key entities: players, teams, boards, sponsors, officials.

With source material, the work proceeds in two stages. First, rebuild Stage-1: title, source, date, article type, information points, entities, time markers. Then Stage-2: argument-structure map, evidence chain with source grading, missing perspectives, time-sensitivity assessment, and framing/word-choice analysis. Only then can a genuine 3,863-word report be written in which every claim traces back to a sourced point.

If the Stage-1 failure is technical — a JavaScript-rendered page, a paywall, anti-scraping blocking, a mismatched CSS selector, or an input that is actually a listing page, tag page or 404 — checking extraction logs and raw HTML length is the fastest diagnostic and often resolves the cause within minutes.