Skip to main content

Feature: Scoring

Tied to journey: Scoring.

Product acceptance criteria​

  • League scoring settings applied consistently
  • Points visible per player and team for a period
  • Finalization rules clear (when a week is “official”)

Architecture​

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

  • Client surfaces — Player and team points for a period; league scoring settings (commissioner-visible). iOS/Android twins.
  • Domain model — ScoringSettings (per league), PlayerPoints, TeamPoints, PeriodFinalization state. Stat ingestion model TBD.
  • Data & APIs — Reed owns scoring settings and points read/finalize contracts (TBD). Stat provider / recalculation TBD (OD-8).
  • Cross-feature dependencies — Consumes Roster starters for a period; drives Matchups scores and standings. Commissioner override bounds TBD (OD-3).
  • Platform notes — Twin parity for points display; no known platform divergence yet.
  • Open decisions — OD-8 scoring data source; finalization rules TBD; OD-3 commissioner overrides.

Implementation notes​

  • (stat provider / recalculation TBD)