An Editorial Framework for Asian Cricket Coverage: From Empty Extraction to Verified Reporting

This document is not a news report. It is the editorial framework for the report that can be written once Stage-1 extraction returns real data. The reason is straightforward: the supplied Stage-1 output is entirely empty. The one-sentence summary is blank, Author Stance and Article Purpose are both N/A, the Information Points section contains no entries at all, Entities are supplied only as an instruction to 'identify from the information points above', Time Sensitivity was never assessed, and Source Quality cannot be judged because there is no source field to judge. The only valid signal is Domain Label: cricket_asia, which defines the topic space of 'cricket plus Asia' and supports no claim about any specific article. The purpose of this text is therefore different. It sets out what structural elements must be collected when analysing any Asian cricket article, which article types recur in this domain, which entity slots each type requires, how source quality should be graded, and what minimum input must exist before writing begins. It is a description of a working system, not of an event. Three technical causes typically sit behind an empty output. First, body-text fetch failed: a 403 response, a paywall, a JavaScript-rendered page whose empty body reached the extractor, or a redirect that lost the original content. Second, the extractor produced output that failed schema validation, and the system silently downgraded it to an empty structure. This is the most dangerous case because the log records a success. Third, the domain classifier works independently from URL, domain, or headline, so it assigns the cricket_asia label normally even when the body is empty. In all three cases the defect is upstream in the pipeline, not in the article's content. That is why this report contains no match score, no player name, no date, no board statement, and no selection controversy. Every Stage-2 input, from author stance through argument chain, information-point weighting, entity relations, and time sensitivity, depends on those empty fields. Filling them by inference would produce something that looks like analysis but is in fact fabrication. Such output is more harmful than an explicit error, because the reader will treat it as verified fact. Now the structure of the cricket_asia domain. Material published here falls broadly into five categories, each with different verification requirements. The first is match reporting: bilateral series, multi-nation tournaments, qualifiers, and age-group competitions. Mandatory slots are teams, venue, date, toss, a verified scorecard source, decisive moments, and post-match reactions. The time anchor is the sharpest here; such a report's value is measured in hours, and without an independently verified scorecard it is not publishable. The second is federation governance and politics: council meetings, member association elections, sponsorship disputes, relations with the ICC, and membership decisions. The most reliable sources are official releases and post-meeting documents; wire reports come second; social media rumour comes third and cannot be treated as fact without independent confirmation. The third category is business and broadcast rights: television and digital rights auctions, title sponsorship, ticketing revenue, and league economics. Numbers are central here, and the most common error is presenting estimated figures as actual contract values. The rule must be explicit: any number whose source is not stated is written as 'reported' or 'estimated', never as definitive. The fourth category is players and selection: squad announcements, injury status, form assessment, retirement, and coach statements. Time sensitivity is high and the risk of emotional tone is highest; 'according to sources' stories about selection are frequently published without confirmation. The fifth category is format and infrastructure: pitch conditions, weather, day-night arrangements, new venues, and changes to schedule structure. Geographical and seasonal context is mandatory because the same data means different things under different conditions. Entity slots should be fixed in advance for each category. Match reports need two teams, venue, date, format, result, decisive player, and umpire or match referee where there is a dispute. Governance needs the institution, the office-holder, the nature of the decision, affected members, and a reference to the official document. Business needs the type of right, territory, term, value or its ratio, and the contracting parties. Selection needs the player, the team, the format, the stated reason for inclusion or exclusion, and a reference to the selection committee. Format needs venue, weather, the source of the pitch report, and the reason for the schedule change. Without these slots a text may look complete technically but remains editorially incomplete, because the reader cannot check where the information came from. Source quality should be graded in three tiers. Tier one: primary sources — official releases from the relevant board or council, published scorecards, formal appointment or exclusion letters, and direct interviews for which a record exists. Tier two: reports from recognised news agencies, with the correspondent's name and location recorded. Tier three: aggregators, reposts, and social media posts without an original source. The editorial rule should be that tier-three material is written as fact only after confirmation from a primary source; otherwise it is clearly marked as a 'claim' or 'rumour'. This distinction matters especially in South Asian cricket journalism, where a great deal of informal information circulates about selection and federation politics and much of it never receives official confirmation. The minimum input to proceed comes in three options. First and best: the full text of the original article as plain text, from which Stage-1 can be rebuilt and the analysis grounded in reality. Second: rerun Stage-1 with a hard gate — information_points must be a non-empty array, every point must carry a source field, the one-sentence summary must not be blank, and entities must be non-empty; if any condition fails, mark the record as 'extraction failed' rather than 'success'. Adding this gate is necessary because the current state makes failure look like success, and that is the most expensive kind of failure. Third: if the original text is unavailable, supply at least the URL and the fetch time so the cause — robots directives, paywall, or dynamic rendering — can be identified. The editorial checklist is as follows and should be applied before every report. Can the central fact be stated in one sentence. Is its source primary or secondary. Are both date and location verified. Is the status of every number — official, reported, or estimated — explicit. Is any claim about a player's or official's position based on a direct reference. Is the opposing side's statement present, or is the piece one-sided. Is time sensitivity such that delay will make the facts stale. If any answer is no, the article is not ready, whatever its length. The conclusion is that reporting quality is determined not by volume of material but by which fact came from which source and how it was verified. In the current Stage-1 output that chain is entirely broken, so the best product available at this stage is this framework. As soon as the original text or a valid rerun of Stage-1 is available, real reports on matches, federations, business, or selection can be written on this same framework, and at that point every sentence can carry its source.