Today and the past five days on the desk, dated and sourced

When the desk publishes a fact that turns out to be wrong, the correction is posted on the dispatch stream with the date it was published, the date it was corrected, the source that triggered the correction and a one-line summary of what changed. The corrected entry remains in place; the dispatch stream shows the before and after in chronological order so readers can audit the desk's editorial hygiene.

The desk tracks each correction as a signal. If the same source triggers three corrections in a row, the desk re-evaluates the source's tier on the evidence register. If the same desk member publishes three corrections in a row on similar topics, the desk adjusts the editorial cycle for that section. The corrections policy is an audit loop, not a public-relations tool.

What the desk will not do

The desk does not publish a correction in body copy on a different page, since that hides the correction from readers who consumed the original. The desk does not delete the original entry and replace it with the corrected copy, since that erases the audit trail. The desk does not bury corrections at the bottom of a page, since that makes the correction functionally invisible.

Reader-filed corrections

Readers can file a correction by emailing [email protected] with the dispatch ID and the source the reader consulted. The desk verifies the reader's source against the desk's tier rules, then either posts a correction or replies with the verification trail. The desk does not require readers to identify themselves.

The first habit is to date every dispatch line. Every entry on the dispatch stream carries the date it was published and the desk ticket. The desk does not publish a dispatch line without a date and a ticket, even when the news is urgent. The discipline protects the reader from seeing a date-less dispatch line that the desk later has to retract, and it protects the desk from a corrections cycle that is harder than the original publication.

The second habit is to log every correction as a dated entry on the dispatch stream. Where the desk publishes a fact that turns out to be wrong, the correction is posted on the dispatch stream with the date it was published, the date it was corrected, the source that triggered the correction and a one-line summary of what changed. The corrected entry remains in place; the dispatch stream shows the before and after in chronological order.

The third habit is to track each correction as a signal. If the same source triggers three corrections in a row, the desk re-evaluates the source's tier on the evidence register. If the same desk member publishes three corrections in a row on similar topics, the desk adjusts the editorial cycle for that section. The corrections policy is an audit loop, not a public-relations tool. The corrections register on /about/ lists the corrections the desk has published and the date of each.

Where the desk diverges from coverage that mirrors trade-press reads is on the corrections discipline. Trade press will sometimes publish a correction without naming the source that triggered it, or without dating the original entry. The desk does not. The desk publishes the source and date on every correction. The discipline is sometimes slower; it is always more honest to read.

The desk also treats the dispatch stream as a working document. Rows move up the dispatch-ladder as sources confirm; rows that fall off the publisher or operator page get removed, not retained as a footnote. The stream 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.

A worked example of a desk editor's weekday-morning source scan. The desk editor reads the publisher patch-notes page at 09:14 UTC. The publisher added a footnote on utility handling; the desk editor re-reads the page at 10:42 UTC and confirms the footnote is a routine clarification. The desk editor publishes a dispatch line on the dispatch stream with the verification timestamps logged.

Where the news route covers a worked corrections-cycle example. The desk published a fact that turned out to be wrong. The correction is posted on the dispatch stream with the date it was published, the date it was corrected, the source that triggered the correction and a one-line summary of what changed. The corrected entry remains in place.

Where the news route covers a worked reader-filed-tip example. A reader emails the desk with a tip about a roster swap. The desk reads the tip, cites the reader's email by date, and waits for a Tier-1 source to confirm the tip. The reader's email is stored on the desk's internal spreadsheet for 30 days and then deleted; the reader can ask for the email to be deleted earlier.

Where the news route covers a worked dispatch-cadence example. The desk editor publishes a dispatch line whenever a Tier-1 source changes, not on a fixed daily time. The cadence is documented on /methods/ and reproduced in summary form on /about/. The cadence is a working description, not a strict schedule.

Where the news route covers what the news route is not. The news route is not a wagering-guidance document, not a performance-rating document, not a streaming directory, not a coaching document. The news route is a working description of the desk's editorial cycle on esports tournaments, matches, teams, players, games and patch context.