Bracket slots fill ahead of group-stage draw

The first habit is to verify the operator page on the same day as the bracket fills. The desk verified the operator page at 17:14 UTC and again at 17:18 UTC; the bracket composition matches the desk's expected list. The editorial practice is to verify any source change on a Tier-1 page on the same day the change is filed, on the basis that immediate verification gives 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 operator page on the next weekday morning.

The third habit is to decline bracket fill as a performance signal. The desk does not interpret bracket fill as performance signal; the bracket slots are awarded on stated operator criteria, and the desk's editorial role is to verify the operator's stated criteria, not to grade them. A reader who follows the desk for two weeks sees the desk declines to grade bracket fill in the editorial copy.

Where the desk diverges from coverage that mirrors trade-press reads is on the signal-discipline policy. Trade press will sometimes publish a bracket fill as a performance signal. The desk does not. The desk publishes the bracket composition and verifies the operator's stated criteria; the desk does not extrapolate performance signal.

The desk also treats the bracket fill as a working document. Rows move up the fill-ladder as sources confirm; rows that fall off the publisher or operator page get removed, not retained as a footnote. The fill 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 the bracket-fill verification in practice. The desk verified the operator page at 17:14 UTC and again at 17:18 UTC. The bracket composition matches the desk's expected list; the desk published a confirmed entry on the dispatch stream with the verification timestamps logged.

Where the dispatch covers what the bracket fill does. The bracket fill confirms the bracket composition the desk was tracking on the horizon ledger. The fill does not introduce a new bracket composition. The desk's editorial practice is to track the operator's bracket composition on the horizon ledger and update the ledger when the operator fills a slot.

Where the dispatch covers what the bracket fill does not do. The bracket fill does not introduce a performance signal. The desk does not interpret bracket fill as performance signal; the bracket slots are awarded on stated operator criteria, and the desk's editorial role is to verify the operator's stated criteria, not to grade them.

Where the dispatch covers what the reader sees next. The desk will publish a follow-up dispatch when the operator closes the bracket window and opens the group-stage draw. The draw date is named on the operator page; the desk reads the operator's published date without paraphrasing. The desk does not publish a preview of the draw.

What the desk will do if the operator's bracket fill deviates from the desk's expected list. The desk will publish a follow-up dispatch on the dispatch stream with the deviation and the date the deviation was published. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier. The deviation is logged on the corrections register.