Skip to main content

Feature: Roster

Tied to journey: Roster / bench.

Product acceptance criteria​

  • Managers can set starters vs bench within roster rules
  • Invalid lineups are blocked or clearly warned (TBD)
  • Changes lock relative to scoring period (TBD)

Architecture​

Scaffold — honest TBDs; do not invent locked product decisions.

  • Client surfaces — Roster / lineup editor (starters vs bench), validation messaging. iOS/Android twins.
  • Domain model — Roster, RosterSlot (starter / bench; IR TBD), Lineup for a scoring period. Slot rules TBD.
  • Data & APIs — Reed owns roster mutation and validation contracts (TBD). Auth + membership required for writes.
  • Cross-feature dependencies — Seeded by Draft; mutated by Waivers; feeds Matchups and Scoring. Lock timing TBD (OD-4).
  • Platform notes — Twin parity expected; no known iOS/Android divergence yet.
  • Open decisions — OD-4 lineup lock timing; OD-3 commissioner override bounds; roster slots / IR TBD.

Implementation notes​

  • (roster slots / IR / lock times TBD)