Skip to main content

Feature: Matchups

Tied to journey: Weekly matchups.

Product acceptance criteria​

  • Weekly H2H matchups generated or configured
  • Managers can view opponent, projected, and live/final scores
  • Standings update from matchup results

Architecture​

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

  • Client surfaces — Weekly matchup view (opponent, projected / live / final), standings. iOS/Android twins.
  • Domain model — Matchup (week, home/away or paired teams), ScoreSnapshot, StandingsRow. Schedule generator entity TBD.
  • Data & APIs — Reed owns schedule, matchup read, and standings contracts (TBD). Scores sourced via Scoring pipeline.
  • Cross-feature dependencies — Depends on league membership and Roster lineups; scores from Scoring. Playoffs likely post-MVP (OD-5).
  • Platform notes — Twin parity for matchup / standings views; live score refresh strategy TBD.
  • Open decisions — OD-5 playoffs; schedule generator TBD.

Implementation notes​

  • (schedule generator / playoffs TBD — likely post-MVP)