Team dossiers with roster source dates and role snapshots, never likenesses
The teams route is the desk's source-dated dossier set. Each dossier carries a roster source date, a role snapshot, an operator roster PDF reference and a confidence tier. We do not publish player likenesses or sponsor marks; identity comes from the publisher roster PDF and the operator's match page, with the desk's editorial copy describing role responsibilities instead.
Why the desk waits for the roster PDF, not the trade press
Trade press rosters are useful context but they are not source. The desk reads trade-press reporting for scene context — what is the mood in the qualifier, who is talking to the operator, which role specialists are mentioned — but the desk does not use trade-press reporting to fill the roster row. A roster row stays at “announced” until the publisher roster PDF and the operator page agree.
This is sometimes the slowest part of the editorial cycle. The desk would rather be slow and right than fast and wrong. A wrong roster row on the corridor page is one of the hardest things to retract on a competition network — readers see the row in their browser tabs for weeks after a correction. Holding the row at announced is the editorial call the desk makes to protect the corridor from retractions.
When a roster composition changes mid-window
Mid-window roster changes are the most error-prone part of the corridor. The desk treats a mid-window change as a correction: the dossier page notes the change, the date the operator confirmed it, and the date the desk updated the row. The desk does not treat mid-window roster changes as routine — each one is logged.
The desk's practice is to wait until the operator roster page is updated before the change appears on the corridor. The roster PDF is checked after. Both must agree before the change is treated as confirmed. Trade press can be cited as the source of the change but the desk uses operator-roster language throughout the dossier — never paraphrases the operator's terminology.
The four-role composition in plain language
A typical 5v5 composition has four named roles plus one specialist. The desk describes each in the player role notebook and uses the same vocabulary across the corridor, the role notebook and the post-match review bench. The vocabulary is short by design — it stays consistent across every dossier so readers do not have to relearn role language between teams.
The desk treats role composition as published information, not as confidential intelligence. The publisher notes which role compositions are in scope per format patch, the operator list of named roles per match, the publisher roster PDF is the editorial source for role names. The corridor carries role-bar pills for each role a team fields on the current stage card.
When a team fields an off-meta composition
Off-meta compositions are documented in the editorial copy and on the post-match review bench, never on the corridor page. The corridor shows what the team fields on the current stage card; the editorial reading of what the composition reads against the patch is on the review bench. This separation prevents the corridor from becoming a speculative page.
If the desk does not have a roster PDF and an operator page that agree, the row stays at announced. The composition vocabulary on the role-bar pills stays at the four-role default. A fifth-role pill is added only when both sources confirm the fifth role.
Read before you click
Where this link goes
The disclosed first-party route is a third-party product page operated by gogotofly.com. The desk does not edit or approve the operator's product page; readers should review the operator's terms before following the link.
Editorial disclosure
fantasye does not accept wagers. The disclosed first-party route is a product comparison entry.
Reading a team dossier against the source dates that matter
The first habit is to read the publisher roster PDF before the trade press. The publisher roster PDF names the roster, the role labels and the role assignments the publisher covers. Trade press interprets those facts but does not publish them, so reading the publisher PDF first means the desk is anchored on the source. Where the publisher PDF and the operator match page agree, the desk treats the row as confirmed.
The second habit is to read the dossier's role-bar pills against the operator match page. The role-bar pills on the corridor are short by design: a role-bar is two to four pills that name the role composition the team fields on the current stage card. The desk does not put more pills on the bar than the operator page lists, even if the trade press thinks the team fields five or six. The corridor is rebuilt from operator pages only.
The third habit is to date every roster file. A roster file without a date is a roster file the desk cannot audit. The corridor lists the source date on every dossier card so the reader can see when the desk last verified the role assignment. Where the source date is older than 14 days, the desk flags the row with a source note that the reader will see on the dossier page. The flag is a courtesy to the reader, not an editorial contradiction with the operator.
Where the desk diverges from coverage that mirrors trade-press reads is on the role-label discipline. Trade press will sometimes promote a Tier-2 role read into the dossier on the basis of one named reporter. The desk does not. The desk waits for the publisher PDF and the operator match page to agree on the same role label, even if the trade press is widely read and broadly credible. The discipline is sometimes slower; it is always more honest.
The desk also treats the dossier as a working document. Rows move up the role-label ladder as sources confirm; rows that fall off the operator page get removed, not retained as a footnote. The corridor is rebuilt from 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.