EDITION · Sat, 01 Aug 2026 · 13:23 UTC
Source-verified ledger · editorial corrections desk open
NEWS · POST-MATCH

Post-match — verified recap across APAC, EMEA, Americas and the Global Finals

Post-match coverage is the desk's standing recap column. Each recap is built from the publisher's own match-history feed and the broadcaster overlay; the editorial read is filed separately as Tier-C.

POST-MATCH · METHOD

How the desk reads a post-match result

A post-match result is score, anchor, read. The desk reads three artefacts per match: the score (publisher feed), the anchor (broadcaster overlay), the read (editor's interpretation).

01

Score

Reproduce the score from the publisher's match-history feed. Tier-A on the publisher feed.

02

Anchor

Reproduce the broadcaster overlay's per-round positioning. Tier-A on the broadcaster feed.

03

Read

The desk's interpretation of the score and anchor. Tier-C editorial with a corrections log.

04

Cross-stamp

Score and anchor are cross-stamped against the publisher's match-history feed URL.

05

Editor's stamp

Tier-A lock where the publisher feed and the broadcaster overlay agree.

06

Archive

Filed under the post-match archive with the publisher URL, the broadcaster URL and the editorial stamp.

POST-MATCH · SAMPLE

Sample post-match thread · APAC Major · Quarter-final 1

Below is a sample post-match thread from the APAC Major Quarter-final 1. The score and anchor are reproduced verbatim from the publisher and broadcaster feeds; the editorial read is filed separately as Tier-C.

ScoreFinal — Aurora Pacific 2-1 Monsoon DriveTier-A — publisher match-history feed
AnchorMap 1: Aurora 13-9 MonsoonTier-A — broadcaster overlay
AnchorMap 2: Aurora 9-13 MonsoonTier-A — broadcaster overlay
AnchorMap 3: Aurora 13-7 MonsoonTier-A — broadcaster overlay
Editor readTier-C editorial — desk's interpretation across three mapsFiled with corrections log
POST-MATCH · DEEP READ

How a post-match column reads across a season

A post-match season is built from three composite reads: the regional composite, the bracket composite, and the season composite. Below is the desk's working method.

Regional composite

The regional composite is built from the publisher's own match-history feed across the regional cycle. The composite captures the per-match score, the per-match anchor and the per-match editor read.

Bracket composite

The bracket composite is built from the publisher's own match-history feed across the full bracket cycle. The composite captures the per-bracket score, the per-bracket anchor and the per-bracket editor read.

Season composite

The season composite is built from the publisher's own match-history feed across the full season. The composite captures the per-season score, the per-season anchor and the per-season editor read.

What the desk does not publish for a post-match column

The desk does not publish leaked match scores. The publisher's published score is the only source.

The desk does not publish speculative match reconstructions. The publisher's published anchor is the only source.

POST-MATCH · FAQ

Post-match reader FAQ

What is the post-match column?
The desk's standing recap column. The column is built from publisher-verified match-history feeds and broadcaster overlays.
How are scores verified?
Through the publisher match-history feed and the broadcaster overlay. Both must agree for Tier-A.
Where do match scores come from?
From the publisher's own published match-history feed. The desk reproduces the score verbatim.
How is the editor's read filed?
As Tier-C editorial with a corrections log. Mean turnaround 14 hours on score-related corrections.