Tournament 2026-08-03 Dispatch · Tier-1

Patch window for Aim format confirmed by publisher

The publisher patch-notes page named 18–20 August as the next format window. The desk is now reading the operator's stage cards against the new patch and will publish the composition rules by the end of this week.

The publisher patch-notes page named 18–20 August as the next format window for the Aim format. The desk has verified the page twice, including a re-read at 10:42 UTC after the publisher added a footnote on utility handling. The footnote is a routine clarification, not a substantive change.

What changes under the patch window: three utility cooldowns are shortened by an average of 12% and one defensive utility cycle is extended by 8%. The desk read is that this nudges the patch toward a faster caller-timing tempo on the first-round win-rate metric the role notebook tracks.

What does not change under the patch window: the map veto pool stays at the post-v6.3.2 list, the role notebook stays at the four-role composition, and the operator's stage cards are not republished. The desk's editorial reading of the patch is conservative — utility timing changes affect caller role first and support role second; carry and specialist roles see less impact until the operator re-publishes stage cards.

What the desk will track

Caller first-round timing on Aim-format stages in the EU+NA confirmed window.
Support utility-supply rounds in the first three matches of the patch window.
Operator stage-card re-publication — the desk will flag any stage-card change as a follow-up dispatch.
Publisher footnotes — the desk read of the publisher page on 10:42 UTC captured the footnote; any further footnotes will trigger a re-read.

What the desk is still reading

The desk is still reading the patch interaction with the map veto pool. The patch window is 18–20 August, and the operator's stage cards for that window were last republished on 02 August. The desk will publish the composition rules once the operator republishes the stage cards — until then, the editor's read of the patch is conservative.

The desk will publish a second dispatch if the publisher footnotes a substantive change before the patch window opens. If no footnote is posted, the desk's patch reading above is the editorial position the desk takes into the window.

Source: Publisher patch-notes page · Verified 2026-08-03 by the desk · Tier-1 source on file

Return to the dispatch stream →

Reader depth

Reading the patch window on the publisher page

Three habits the desk follows when reading a publisher-confirmed patch window.

The first habit is to verify the publisher page twice. The publisher patch-notes page was verified at 09:14 UTC and again at 10:42 UTC after the publisher added a footnote on utility handling. The footnote is a routine clarification, not a substantive change. The desk's editorial practice is to verify any change on a Tier-1 page twice before publishing the dispatch, on the basis that two verifications give the desk enough certainty to publish a confirmed entry.

The second habit is to log the verification timestamps on the dispatch. The dispatch line names the source the desk consulted and the date the desk verified the source. The practice protects the reader from seeing a date-less dispatch line and protects the desk from a corrections cycle that is harder than the original publication. The verification timestamps are also useful internally when the desk re-reads the publisher page on the next weekday morning.

The third habit is to publish a follow-up dispatch when the publisher footnotes a substantive change. The publisher's footnote on utility handling was a routine clarification, so the desk did not publish a follow-up dispatch. Where the publisher footnotes a substantive change before the patch window opens, the desk will publish a follow-up. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier.

Where the desk diverges from coverage that mirrors trade-press reads is on the footnote-discipline policy. Trade press will sometimes publish a footnote as if it were a substantive change. The desk does not. The desk distinguishes routine clarifications from substantive changes and publishes accordingly. The discipline is sometimes slower to operate; it is always more honest to read.

The desk also treats the patch window as a working document. Rows move up the window-ladder as sources confirm; rows that fall off the publisher or operator page get removed, not retained as a footnote. The window is rebuilt from publisher and operator pages only. A row the desk kept for "tracking purposes" is a row the reader cannot verify, so the desk removes rather than retains. This is sometimes the slower choice; it is always the more honest choice.

Editorial cycle: weekday-morning source-scan, weekday-afternoon narrative-edit, weekly patch workshop. Verification timestamps on the dispatch stream.

Editorial working notes

How the desk reads this

A working description of the editorial cadence the desk follows on this route.

The patch window is verified twice. The publisher page was verified at 09:14 UTC and re-verified at 10:42 UTC after a footnote was added. The footnote was a routine clarification on utility handling. The two verifications give the desk enough certainty to publish a confirmed entry on the dispatch stream, and the verification timestamps are logged on the dispatch stream for the reader to audit.

The patch window's interaction with the map veto pool. The patch window is 18-20 August; the operator's stage cards for that window were last republished on 02 August. The desk will publish the composition rules once the operator republishes the stage cards. Until then, the editor's read of the patch is conservative — utility timing changes affect caller role first and support role second; carry and specialist roles see less impact.

Where the publisher page references the publisher footnote. The footnote was added at 10:42 UTC and was a routine clarification on utility handling. The footnote did not change the substance of the patch window; the desk did not publish a follow-up dispatch on the footnote. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier, and to leave routine clarifications on the publisher page.

Where the desk reads the patch window's interaction with the previous patch. The previous patch (v6.3.2) is live since 28 July. The interaction between v6.3.2 and v6.4 is on the desk's reading list. The desk will publish a patch workshop reading once the operator republishes the stage cards. The patch workshop reading is published on the guides route; the news dispatch is the head-line summary.

What the desk will do if the publisher footnotes a substantive change before the patch window opens. The desk will publish a follow-up dispatch on the dispatch stream with the substantive change and the date the change was footnoted. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier.

Worked example

How the cycle reads in practice

A worked trace of the editorial cycle on this page.

A worked example of the footnote verification in practice. The publisher page was verified at 09:14 UTC. The publisher added a footnote on utility handling at 09:32 UTC. The desk re-read the page at 10:42 UTC and confirmed the footnote was a routine clarification. The desk logged both verification timestamps on the dispatch stream.

Where the dispatch covers the patch window's interaction with the operator. The operator stage cards for the patch window were last republished on 02 August. The desk reads the operator stage cards on weekday mornings; the desk will publish the composition rules once the operator republishes the stage cards. Until then, the editor's read of the patch is conservative.

Where the dispatch covers the patch window's interaction with the map veto pool. The patch window is 18-20 August. The map veto pool was last updated for the v6.3.2 patch on 28 July. The desk's read is that the v6.4 patch does not change the map veto pool; the editorial cadence is to verify the map veto pool against the operator stage cards when the operator republishes.

Where the dispatch covers the patch window's interaction with the role notebook. The desk's read is that the v6.4 patch affects the caller role first and the support role second. The carry role and specialist role see less impact until the operator republishes the stage cards. The desk's editorial practice is to publish the role notebook note once the operator republishes.

What the desk will do if the patch window is extended or shortened. The desk will publish a follow-up dispatch on the dispatch stream with the change and the date the change was published. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier. The patch workshop reading is updated with the revised patch window.