
Newsroom floor
Method docs, source ladders, and correction logs beat speed-only culture.

Roster moves, stage openers, and patch explainers written for competitive impact — not empty churn.
Evergreen frameworks with dated hooks. Each piece links back to hubs you can reuse next week.
Schedule density, veto pressure, and Bo5 stamina questions before a championship block.
How to grade confirmed moves versus rumor weather during circuit breaks.
A lab process for balance changes without inventing numbers.

Method docs, source ladders, and correction logs beat speed-only culture.

Atmosphere is color. Bracket math still needs official graphics.

We do not paste wires. We ask what changes competitive reads.
Standards live in editorial policy.
When there is a clear method story — roster windows, stage openers, patch processes — not empty daily filler.
No. Each piece needs an original angle: veto impact, schedule density, or evidence standards.
Visible update notes when facts change. See editorial policy.
Use the contact page with sources. Anonymous screenshots need corroboration.
They model the formats we reuse: finals preflight, roster window, patch method.
No. That language is out of scope on nexus.
Articles live as static routes under /news/ and appear in the sitemap when published.
We label speculation. Confirmed facts lead when we have them.
Keep the editorial read primary. Optional board access stays contextual and age-gated.
Contextual board access only. 18+. Local law applies. Never stake money you cannot afford to lose.