Awaiting stats
Approve match rows to unlock the board.
S3 rankings
Ranked drop built from reviewed leaderboard lines, movement, team context, recent scoring form, and the same season engine that feeds the public tables.
Approve match rows to unlock the board.
OVRWire rankings are built to start arguments without losing the receipts. The power board is where verified results, recent form, player production, team context, and organizer-published editorial judgment become a ranked league story.
The standings tell you who has the record. Rankings tell you who is moving different right now.
Rankings are receipt-backed in three layers:
OVRWire should not publish rankings from fake demo rows, private guesses, or live fan prompts. Rankings need source-backed inputs and a clear date or freshness label.
No. Standings are record order. Rankings are a power-board layer that can account for recent form, production, context, and editorial judgment.
Yes, depending on the league's setup. Some boards are team-first power rankings, while player-driven boards can spotlight the top performers shaping the season.
They should update after reviewed results or organizer-triggered ranking drops. A freshness label should make the timing clear.
Yes, for Pro and Hall of Fame scope. It can publish cached "why" notes grounded in reviewed league data.
That is part of the fun. The page should give them the receipts: recent games, standings, leaderboards, and match results.
No. Public rankings should be grounded in league data approved for publication, not private notes or unreviewed submissions.