Community competition direction
Competition needs context.
Not just a bracket.
Tournaments are planned as a later surface that connects players, stacks, eligibility, schedules, match evidence, and safety boundaries.
OffAngle surfaceFixture preview
StackLFT verified
MatchBo3
NoticePolicy gate
Product promise
A bracket is only useful if teams can trust the context around it.
This route does not publish events, rankings, eligibility claims, or safety records. It exists to frame the future surface after lookup, claiming, and notice-board governance mature.
Register
Support player and stack identity only after account claiming and visibility choices exist.
Schedule
Coordinate event times, check-in, map vetoes, and match reporting with clear dispute states.
Resolve
Handle results, evidence, forfeits, and safety flags through operational workflows instead of public pile-ons.
Claimed profiles first
Tournament identity depends on private-by-default claiming and consent.
Dispute-aware reporting
Results need review state, source evidence, and appeal paths.
Notice-board boundary
Safety information must remain policy governed and never become a dodge score.
Companion workspace
Give a bracket the trust layer it normally lacks.
A future event view should show check-in, eligibility, match proof, and dispute state without turning safety into public pile-on content.
ABStackClaim required
MatchBo3
DisputeEvidence gated
Tournament catalog
Frame matches before records exist.
Static catalog context can help future brackets explain map, role, and loadout expectations without claiming eligibility, ranking, or hidden player history.
Static VALORANT catalogNo live provider dataReview-ready links
Interactive Tournament Ops preview