The editorial companion: a read-only desk for competitive gaming
The companion is a read-only editorial surface. The desk does not operate an application download or a feature that requires an account.
Editorial independence
Sources cited · Updated 2026-08-04 · No invented fixtures · No fabricated rosters
Editorial companion
The editorial companion: a read-only desk for competitive gaming
The companion is a read-only editorial surface. The desk does not operate an application download or a feature that requires an account. Where the companion references a route, the route is disclosed in line.
What the companion carries
Three surfaces the companion exposes
- Tournament ledger — the calendar ledger filtered by region, format and prize tier.
- Match desk — the match ledger with platform, format and source tier.
- Patch workshop — the studio notes and the meta reading side by side.
Disclosed route
Comparison route disclosure
Where the companion references a comparison route in editorial copy, the route is disclosed in line with a one-line description of the route's purpose. The route is operated on a first-party basis.
Disclosed first-party route
/Login/playnow
Companion shape
What the editorial companion covers
The editorial companion covers three surfaces: the tournament ledger, the match desk, and the patch workshop. The companion is read-only; the desk does not offer a download, a feature that requires an account, or a per-route notification system.
The companion is jurisdiction-neutral. Where a comparison route is referenced in the companion, the route is disclosed in line. Where a self-exclusion signpost is referenced, the signpost is jurisdiction-specific and the desk does not maintain a per-jurisdiction list.
No download
Why the desk does not offer a download
The desk does not offer a download. The desk's case for the read-only companion is that the editorial surface is the desk's product; offering a download would add a feature the desk cannot independently verify without expanding the editorial surface beyond its primary function.
Where a reader wants a portable read of the editorial surface, the desk's RSS feed at /feed.xml and the LLMs manifest at /llms.txt are the desk's answer. The two surfaces carry the editorial content without the feature scope of a download.
Companion shape
What the editorial companion covers
The editorial companion covers three surfaces: the tournament ledger, the match desk, and the patch workshop. The companion is read-only; the desk does not offer a download, a feature that requires an account, or a per-route notification system.
The companion is jurisdiction-neutral. Where a comparison route is referenced in the companion, the route is disclosed in line. Where a self-exclusion signpost is referenced, the signpost is jurisdiction-specific and the desk does not maintain a per-jurisdiction list.
No download
Why the desk does not offer a download
The desk does not offer a download. The desk's case for the read-only companion is that the editorial surface is the desk's product; offering a download would add a feature the desk cannot independently verify without expanding the editorial surface beyond its primary function.
Where a reader wants a portable read of the editorial surface, the desk's RSS feed at /feed.xml and the LLMs manifest at /llms.txt are the desk's answer. The two surfaces carry the editorial content without the feature scope of a download.
RSS
The companion's RSS surface
The companion's RSS surface lives at /feed.xml. The feed carries the news desk's three-frame stories with the title, link, description and publication date. The feed is updated when the news desk publishes a story.
Where a reader wants the companion's content without subscribing to the news desk, the LLMs manifest at /llms.txt carries the editorial surface as a single document. The manifest is plain text and routes a portable read of the editorial surface.
Reader list
What a reader does with the companion
- Subscribe. Open
/feed.xmlin a feed reader. The news desk publishes three-frame stories on every Tier 1 release. - Open the manifest. Read
/llms.txtfor a portable read of the editorial surface as a single document. - Open a route. Read the route map at
/sitemap/for the full surface, then open the route that matches the question.
FAQ · app
Frequently asked questions, in editorial voice
The desk answers the most common reader questions about this surface in editorial voice. The FAQ is editorial — the desk does not invent answers; the answers cite the surface that already carries the answer.
Does the companion require sign-up?
No. The editorial companion is read-only. The desk does not operate an account system or a feature that requires an account. The companion surfaces the tournament ledger, match desk and patch workshop.
Is the companion available offline?
The companion is published as static HTML on the document root. A reader can save the route for offline reading. The desk does not publish a downloadable application.
What about the RSS feed?
The companion's RSS surface lives at /feed.xml. The feed carries the news desk's three-frame stories with the title, link, description and publication date.
Where do I find the source hierarchy?
The desk's source hierarchy lives on the methodology page. Every dossier, ledger row and match note carries one of four tiers: Tier 1 (League/Official), Tier 2 (Verified org), Tier 3 (Established media), Tier 4 (Community).
What does the source badge tell me?
The source badge tells you what the desk trusts about the row. A Tier 1 source is a league announcement; a Tier 2 source is an org confirmation; a Tier 3 source is a named reporter; a Tier 4 source is a community post the desk has not yet verified.
How does the desk promote a row's tier?
The desk does not promote a row's tier by editorial decision. A Tier 4 row carries a rumor badge and stays Tier 4 until a Tier 1 or Tier 2 source confirms it. The desk's case for the no-promotion rule is that an editorial promotion would conflate the desk's confidence with the source's confirmation.
How often does the surface refresh?
The surface refreshes weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of every route.
How do I subscribe to updates?
The desk's RSS feed at /feed.xml carries every news desk story. The LLMs manifest at /llms.txt carries the editorial surface as a single document.
How do I file a correction?
Corrections are routed through the corrections email at corrections at esportswagerin dot com. The desk verifies the correction against a Tier 1 or Tier 2 source and updates the row within 48 hours.
Extended notes
Why the companion is read-only
The companion is read-only because the desk's editorial surface is its product. Adding an interactive feature would expand the editorial surface beyond its primary function: covering competitive gaming with verifiable sources. The companion carries the tournament ledger, the match desk and the patch workshop; the three surfaces are independent, and a reader who knows one surface can move directly to the next without re-reading the surface they have already opened.
Where the companion references a comparison route in editorial copy, the route is disclosed in line. The desk does not embed external destinations in editorial HTML. The disclosure block on this route names the first-party route the desk uses for editorial comparison references; the route is operated on a first-party basis.
The companion's read-only discipline extends to the RSS feed at /feed.xml and the LLMs manifest at /llms.txt. The RSS feed carries the news desk's three-frame stories; the LLMs manifest carries the editorial surface as a single document. Both surfaces are read-only and both are updated on every publication.
Publication
How the companion publishes
The companion publishes as static HTML on the document root. The desk refreshes the companion's surfaces when the calendar ledger refreshes — every Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of every route.
Where the companion's reference is wrong for a specific region, the desk routes the correction through the contact page rather than overwriting the reference silently. The corrections log lives on the methodology page; the previous wording is kept for context.