fantasye is an esports competition network, not a wagering service
fantasyein.com is published by the fantasye desk, an editorial team that covers esports tournament schedules, match briefings, team dossiers, player role notebooks, game-format atlases and patch readings with sourced journalism. The site does not accept wagers, host live brackets or sell merchandise.
What the desk does and what it does not do
The desk covers esports by format family rather than by title, and by source tier rather than by community chatter. The desk publishes only what two independent Tier-1 sources can agree on for confirmed facts; announced entries are flagged and may move up when the second source confirms. Speculation is labelled, never used to fill a confirmation row.
The desk does not publish picks, odds, prop estimates, payout estimates or wagering guidance. The desk does not accept wagers, host live brackets, sell merchandise or accept payment in exchange for editorial coverage. The desk's commercial disclosure at /disclosure/ names the operator relationship the desk has, which is limited to the disclosed first-party route on the mobile sticky CTA and the route-checkpoint card.
What the desk reads
The desk reads publisher patch-notes pages, operator roster PDFs, operator help pages and operator stage cards as Tier-1 sources. Trade press is read as Tier-2 (scene context, editorial interpretation, profile quotes). Community reports and co-streams are read as Tier-3 (scene chatter, co-stream context only). The full register is at /evidence/.
What the desk does not read
The desk does not read betting-shop odds, payout calculators or wager-tracking services as sources. The desk treats any source whose primary business is wagering as out-of-scope for fact verification; trade press owned by wagering businesses is read but flagged.
How the desk handles disagreement
When two Tier-1 sources disagree, the desk publishes both sides in the editorial copy and waits for the third source. The desk does not pick a side on the basis of which source is bigger, louder or older — the desk picks the side the third source confirms. Where three sources are slow to arrive, the desk removes the speculative entry from the briefing queue and waits for the question to settle.
What we publish when we get a fact wrong
A correction is a dated entry on the dispatch stream that names the entry being corrected and the source that triggered the correction. The desk does not silent-edit. Where the original entry can be retained in place with a dated correction line, the entry is retained; where the original entry would mislead readers if retained, the desk removes the body copy and replaces it with a correction banner that links to the corrected version.
Reader-filed corrections are accepted at [email protected]. The desk verifies the reader's source against the desk's tier rules within 24 hours, then either posts a correction or replies with the verification trail. The desk does not require readers to identify themselves.
The corrections register is reviewed by the desk at the end of each calendar month. Recurring gaps from a single source trigger a tier re-evaluation. Recurring gaps from a single desk member trigger a section-level editorial-cycle adjustment.
Three editorial cycles
The fantasy desk follows three editorial cycles: a weekday-morning source-scan cycle for the dispatch queue, a weekday-afternoon narrative-edit cycle for the dossier and briefing pages, and a weekly cycle for the patch workshop. Each cycle has a defined input (which Tier-1 sources are read), a defined output (which page receives the edit) and a defined audit trail (which dispatch line the edit traces to).
The source-scan cycle reads every Tier-1 source on the evidence register on weekday mornings, notes any change against the prior day, and emits a dispatch line if the change qualifies as news. News is defined as “a Tier-1 source change visible to readers on the page they would have read yesterday.” Routine confirmation of a previously announced fact does not count as news; a substantive change in status does.
The narrative-edit cycle reads the dispatch queue from the morning scan and edits the dossier, briefing queue, match ledger and patch workshop pages against the dispatch lines. Each edit is dated on the source-ribbon metadata at the top of the page.
The patch workshop cycle reads the publisher patch-notes page on the publication day, walks through the operator stage cards one stage at a time, and translates the changelog into three annotated tactical questions on the workshop right page. The three passes the desk follows are documented at the patch workshop.
The boundaries the desk will not cross
The desk does not accept payment in exchange for editorial coverage. The desk does not accept payment in exchange for editorial silence. The desk does not accept gifts, hospitality or favours from operators, publishers or other sources the desk covers. The desk does not quote or paraphrase operators, publishers or other sources the desk covers without naming the source.
The desk does not publish speculation as fact. The desk does not extend the season by extrapolating unmatched bands. The desk does not invent team names, player names, role assignments, stage names, format families or publisher notes. The desk uses the operator's terminology wherever the operator has published it.
The desk does not name sources the desk cannot verify. Trade-press quotes are attributed to the publication; community reports are attributed to the platform; co-stream reads are attributed to the channel. Where a source cannot be verified to the desk's tier rules, the desk does not cite the source at all.
Compare the product route, with editorial context
Read before you click
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 only.
Reading the editorial position the desk takes
The first habit is to keep the editorial position short. The desk's editorial position is short by design: any reader can audit the desk's editorial hygiene against the public dispatch stream in under five minutes. The position is published on /about/ and reproduced on the footer of every page so readers can find it without searching. The desk does not expand the position into a long-form document unless a reader asks for the expansion.
The second habit is to name the boundaries the desk will not cross. The desk does not accept payment in exchange for editorial coverage. The desk does not accept payment in exchange for editorial silence. The desk does not accept gifts, hospitality or favours from operators, publishers or other sources the desk covers. The boundaries are listed in plain language on /about/ and reinforced by the corrections register the desk maintains.
The third habit is to publish the methods colophon alongside the editorial position. The methods colophon describes the three editorial cycles the desk runs on weekday mornings, weekday afternoons and weekly, with a defined input, output and audit trail for each. The colophon is published on /methods/ and reproduced in summary form on /about/. The desk does not write a long-form methods document unless a reader asks for the expansion.
Where the desk diverges from coverage that mirrors trade-press reads is on the editorial-ethics discipline. Trade press will sometimes accept hospitality from operators or publishers the publication covers. The desk does not. The desk's hospitality policy is on /about/ and the desk will decline hospitality where the policy would otherwise apply. The discipline is sometimes slower to operate; it is always more honest to read.
The desk also treats the editorial position as a working document. Position rows move up the confirmation-ladder as sources confirm; position rows that fall off the publisher or operator page get removed, not retained as a footnote. The position 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.