Skip to main content

Feature: Leagues

Tied to journey: Create / join league.

Product acceptance criteria​

  • Commissioner can create a league
  • League can be discoverable (browse) or unlisted (default TBD — see open decisions)
  • Guests and signed-in users can browse discoverable league metadata
  • Gated join: request-to-join (commissioner approve/decline) or invite code
  • No one-tap open public join
  • League settings editable by commissioner within defined bounds
  • Clear membership list and role display

Architecture​

Scaffold — fill as contracts firm up. Do not treat TBDs as product locks.

  • Client surfaces — League create, discover/browse list, league home / settings, membership list, join request + invite-code redeem flows. iOS/Android twins; shared soft-gate before membership writes.
  • Domain model — League (settings, discoverability flag), Membership (role: commissioner / manager; pending vs active), JoinRequest, InviteCode. Exact field set TBD.
  • Data & APIs — Reed owns backend contracts for league CRUD, discover listing, join request, invite redeem, and membership. Endpoint shapes TBD. Auth-verified JWT required for create / request-join / redeem (Auth).
  • Cross-feature dependencies — Auth soft-gate gates writes; leagues own membership and commissioner role for downstream draft, roster, matchups, scoring, and waivers. Discover browse may be signed-out.
  • Platform notes — Twin parity expected for create/browse/join; invite deep-link host details may follow OD-9 once invite tokens are specified.
  • Open decisions — OD-7 discover list visibility default; OD-10 what makes a league discoverable; OD-11 commissioner approval UX; invite token / deep link TBD.

Implementation notes​

  • (invite token / deep link TBD)
  • (Discover listing policy / feed TBD)