perditions-league

byHello Mcdonald

2026 perditions league with invites, match picks, live standings, reminders and leaderboard

LandingLeaguesInviteStandingsMatch PicksLoginSign Up
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Perditions League

1. Introduction

Perditions League is a 2026 sports prediction league for friends and organisers. It lets a League Organizer create a league, invite players, set match picks and reminders, and follow live standings and a leaderboard; invited League Players accept the invite, submit match picks before each deadline, receive reminders, and check live standings and the leaderboard.

The product intent is a sharp, competitive, street-smart league experience — not a soft social app. The audience is small groups of friends and their organiser who want a bold, industrial, high-contrast surface for picks and rivalries, delivered as a first-party web application with application-owned identity, background reminder automation, and outbound invite/reminder delivery to external recipients.

This document is the System Requirements Document for the product; it specifies the product's features and workflows in full.

Page 1 of 20

2. System Overview

Perditions League is delivered as a React frontend, a shared FastAPI backend, and a MariaDB database. The frontend provides the custom pages; the backend owns league, invite, pick, reminder, standings, and leaderboard APIs plus the background reminder automation; MariaDB holds application-owned persistent data (users, leagues, memberships, invites, matches, picks, reminders, and standings/leaderboard state).

Actors:

  • League Organizer (human) — creates the 2026 perditions league, sends invites, sets match picks and reminders, follows live standings and the leaderboard.
  • League Player (human) — accepts the league invite, submits match picks before each deadline, gets reminders, checks live standings and the leaderboard.
  • Reminder automation (system process) — sends reminders before the pick deadline.
  • Invite/reminder recipients (external recipients) — receive outbound invite and reminder messages.

Current delivery covers: league creation, invites, match picks, live standings, reminders, and leaderboard, plus the identity establishment and invite acceptance needed to make those journeys executable.

Removed from scope

  • None.
Page 2 of 20

2a. Product Interpretation and Delivery Boundary

The product is a first-party web application. Identity is application-owned: a new user enrolls through Sign Up, a returning user verifies identity through Login, and both are anonymously reachable. Protected league work (creating leagues, accepting invites, submitting picks, viewing standings) requires an established identity; the Landing, Sign Up, and Login pages are public entry surfaces.

Invites and reminders are delivered to external recipients outside the application; the application owns the invite record, its acceptance state, and the reminder schedule, while delivery to the recipient's channel is outbound. Reminder sending is background automation owned by the backend, triggered before the pick deadline.

All accepted behavior is current. No future-horizon capabilities are defined in this document.

2c. Page Content and Component Coverage

Page 3 of 20

Landing

  • Information/state: Public entry surface explaining the 2026 Perditions League, invites, match picks, live standings, and reminders before sign-in. Hero headline "Picks. Rivals. Live standings."; subline "Create the 2026 Perditions League, invite your players and track every pick."; call to action "Start a league". Quoted section labels in all caps with wide letterspacing; hazard-stripe band across the lower third of the hero; thin ticker tape of live standings scrolling across the page edge.
  • Primary actions: "Start a league" (routes to Sign Up); sign-in path to Login.
  • Supporting actions: Read the feature explanation sections (invites, picks, standings, reminders).
  • Domain entities: League (described), Match (described), Standings (ticker display only).
  • Component responsibilities: Hero block (quoted label, headline, subline, sharp orange CTA block with exposed 1px grid-line offset); hazard-stripe band; feature explanation panels with ruled framing; standings ticker tape.
  • States: Loading — static content, no data dependency beyond the ticker; empty — ticker shows a neutral placeholder when no live standings exist; success — full hero and explanation content; error — ticker failure degrades to a static label without blocking the CTA; recovery — CTA remains usable regardless of ticker state.
Page 4 of 20

Sign Up

  • Information/state: Anonymous enrollment surface for a new user who will create or join a league. Collects the identity details needed to establish an application-owned account.
  • Primary actions: Submit enrollment to create the account and proceed to Leagues (organizer path) or to an invite (player path).
  • Supporting actions: Navigate to Login if already enrolled.
  • Domain entities: User account.
  • Component responsibilities: Enrollment form with labeled fields; validation messaging; submit control as a sharp orange block.
  • States: Loading — submit in progress with control disabled; empty — blank form with field labels; success — account established and routed onward; error — invalid or incomplete input shown inline with the field; recovery — user corrects input and resubmits without losing entered values.

Login

  • Information/state: Anonymous returning-user verification surface granting access to league records.
  • Primary actions: Submit credentials to verify identity and reach Leagues, Match Picks, or Standings.
  • Supporting actions: Navigate to Sign Up if not yet enrolled.
  • Domain entities: User account.
  • Component responsibilities: Credential form; validation and failure messaging; submit control.
  • States: Loading — verification in progress; empty — blank form; success — verified and routed to the intended protected destination; error — rejected credentials shown without revealing which field failed; recovery — retry with corrected credentials.
Page 5 of 20

Leagues

  • Information/state: Protected organizer surface listing the leagues the organizer owns and the state of each 2026 perditions league, including its members and invite status.
  • Primary actions: Create a 2026 perditions league; send invites to players.
  • Supporting actions: View league membership and pending invites; open Match Picks and Standings for a league.
  • Domain entities: League, Membership, Invite, User.
  • Component responsibilities: League list with ruled panels; create-league form; invite composer capturing recipient and producing an invite record; invite status list (pending, accepted).
  • States: Loading — league list skeleton; empty — no leagues yet with the create action foregrounded; success — league created and invite sent confirmation; error — creation or invite failure shown with retry; recovery — retry preserves entered league and invite details.
Page 6 of 20

Invite

  • Information/state: Protected surface for an invited League Player to review the league invite and its details and accept it to join.
  • Primary actions: Accept the invite to join the league.
  • Supporting actions: Review league name and organizer before accepting.
  • Domain entities: Invite, League, Membership, User.
  • Component responsibilities: Invite detail panel with quoted metadata; accept control; membership confirmation.
  • States: Loading — invite lookup in progress; empty — no pending invite for this user; success — membership created and confirmation shown with a path to Match Picks; error — invalid or already-used invite explained; recovery — user can return to Leagues or wait for a new invite.

Match Picks

  • Information/state: Protected surface where a league member submits picks for each match before the deadline. Pick rows render as shipping-label cards with quoted match data and a yellow live-deadline tag.
  • Primary actions: Submit picks for each match before the deadline.
  • Supporting actions: Review previously submitted picks; see the deadline status per match.
  • Domain entities: Match, Pick, Deadline, Membership, League.
  • Component responsibilities: Match list as shipping-label cards; pick selection control per match; deadline tag; submit control; confirmation of recorded picks.
  • States: Loading — match list loading; empty — no matches scheduled for the league; success — picks recorded and confirmed; error — submission rejected (for example past deadline) explained per match; recovery — user can correct open picks and resubmit before the deadline.
Page 7 of 20

Standings

  • Information/state: Protected surface showing live standings and the leaderboard for a league. Hazard-stripe band repeats at the top of the page; live data uses yellow.
  • Primary actions: View live standings and the leaderboard.
  • Supporting actions: Switch between the league's standings and leaderboard views; refresh live data.
  • Domain entities: Standings, Leaderboard, Membership, Pick results.
  • Component responsibilities: Standings table with ruled framing; leaderboard ranking list; live indicator; ticker tape of live standings.
  • States: Loading — standings loading; empty — no results recorded yet with a neutral message; success — live standings and leaderboard rendered; error — data fetch failure shown with retry; recovery — retry reloads live data without losing the selected view.
Page 8 of 20

3. Functional Requirements

FR-1 — Create a 2026 perditions league (explicit) As a League Organizer, I should create a 2026 perditions league so that my players have a league to join.

  • Trigger/input: organizer submits league creation details on Leagues.
  • Observable result: a new league record exists, owned by the organizer, listed on Leagues.
  • Access: authenticated organizer.
  • Failure/recovery: creation failure is shown with retry preserving entered details.
  • Continuation: organizer proceeds to send invites.

FR-2 — Invite other players to the league (explicit) As a League Organizer, I should invite other players to the league so that they can join and compete.

  • Trigger/input: organizer composes an invite for a recipient from Leagues.
  • Observable result: an invite record is created in pending state and delivered outbound to the recipient; invite status is visible on Leagues.
  • Access: authenticated organizer.
  • Failure/recovery: delivery or creation failure is shown with retry.
  • Continuation: organizer tracks invite status until accepted.
Page 9 of 20

FR-3 — Accept the invite to join the league (required_inference) As an invited League Player, I should accept the invite to join the league so that I become a member and can submit picks.

  • Trigger/input: player opens Invite and selects accept.
  • Observable result: membership is created for the player in that league; confirmation is shown.
  • Access: authenticated player with a pending invite.
  • Failure/recovery: invalid or already-used invite is explained; player can return to Leagues.
  • Continuation: player proceeds to Match Picks.

FR-4 — Submit match picks (explicit) As a league member, I should submit match picks for each match before the deadline so that my results count toward standings.

  • Trigger/input: member selects a pick per match on Match Picks and submits.
  • Observable result: picks are recorded against the member and match; confirmation is shown.
  • Access: authenticated league member.
  • Failure/recovery: a pick past the deadline is rejected and explained per match; open picks can be corrected and resubmitted.
  • Continuation: member checks Standings after results.

FR-5 — See live standings (explicit) As a league member, I should see live standings so that I know where I rank as results come in.

  • Trigger/input: member opens Standings for a league.
  • Observable result: current standings are displayed with a live indicator.
  • Access: authenticated league member.
  • Failure/recovery: fetch failure is shown with retry.
  • Continuation: member refreshes or switches to the leaderboard.
Page 10 of 20

FR-6 — See a leaderboard (explicit) As a league member, I should see a leaderboard so that I can compare my ranking against other players.

  • Trigger/input: member opens the leaderboard view on Standings.
  • Observable result: ranked list of members is displayed.
  • Access: authenticated league member.
  • Failure/recovery: fetch failure is shown with retry.
  • Continuation: member returns to standings or picks.

FR-7 — Get reminders (explicit) As a league member, I should get reminders before the pick deadline so that I do not miss submitting picks.

  • Trigger/input: the reminder automation evaluates the pick deadline and sends a reminder to members who have not completed picks.
  • Observable result: a reminder is delivered outbound to the member before the deadline.
  • Access: system process; recipient is an external recipient.
  • Failure/recovery: failed delivery is retried by the automation.
  • Continuation: member opens Match Picks and submits.

FR-8 — Self-service enrollment or login (required_inference) As a new or returning user, I should enroll or log in so that I can reach league records.

  • Trigger/input: user submits Sign Up or Login.
  • Observable result: an application-owned identity is established or verified and the user is routed onward.
  • Access: anonymous entry on Sign Up and Login.
  • Failure/recovery: invalid input or credentials are shown inline; user retries.
  • Continuation: user proceeds to Leagues, Invite, Match Picks, or Standings.
Page 11 of 20

FR-9 — System sends reminders before the pick deadline (required_inference) As the reminder automation, I should send reminders before the pick deadline so that members are prompted in time.

  • Trigger/input: scheduled evaluation of upcoming deadlines.
  • Observable result: reminder messages are dispatched to eligible members.
  • Access: backend background process.
  • Failure/recovery: failed dispatches are retried.
  • Continuation: reminders are reflected in member behavior on Match Picks.

4. User Personas

League Organizer

  • Product context: Runs a 2026 perditions league for friends; owns the league record and its membership.
  • Primary goal: Stand up the league, bring players in, keep picks and reminders on schedule, and watch live standings and the leaderboard.
  • Distinct responsibilities: Creates the league on Leagues; composes and sends invites; sets match picks and reminders; follows live standings and the leaderboard on Standings.
  • Inputs/decisions: League details, invite recipients, match pick configuration, reminder timing relative to the deadline.
  • Interactions: Sends invites to League Players and tracks their acceptance; sees player picks reflected in standings.
  • Observable success: League created, invites accepted, picks recorded, reminders delivered, standings and leaderboard current.
Page 12 of 20

League Player

  • Product context: Invited into a friend's 2026 perditions league; competes on picks.
  • Primary goal: Join the league, submit picks before each deadline, and track rank.
  • Distinct responsibilities: Accepts the invite on Invite; submits match picks on Match Picks before the deadline; receives reminders; checks live standings and the leaderboard on Standings.
  • Inputs/decisions: Which pick to make per match; whether to accept the invite.
  • Interactions: Receives invites and reminders from the organizer's league; appears in standings and leaderboard alongside other players.
  • Observable success: Membership confirmed, picks recorded before deadlines, rank visible on standings and leaderboard.
Page 13 of 20

5. Core User Flows

Flow A — Organizer creates a league and invites players

  1. Organizer opens Landing and selects "Start a league".
  2. Organizer completes Sign Up; the account is established and the organizer is routed to Leagues.
  3. On Leagues, the organizer submits league creation details; the new 2026 perditions league appears in the list.
  4. The organizer composes an invite for a player and sends it; the invite appears in pending state.
  5. The invite is delivered outbound to the player.
  6. The organizer tracks invite status on Leagues until it shows accepted.
  7. If creation or delivery fails, the organizer retries with details preserved.

Flow B — Player accepts an invite and joins

  1. Player receives the invite outbound and opens the application.
  2. If new, the player completes Sign Up; if returning, the player verifies on Login.
  3. The player opens Invite, reviews the league and organizer, and selects accept.
  4. Membership is created and confirmation is shown.
  5. The player proceeds to Match Picks.
  6. If the invite is invalid or already used, the player is told and can return to Leagues.
Page 14 of 20

Flow C — Player submits match picks before the deadline

  1. Player opens Match Picks for the league.
  2. Each match appears as a shipping-label card with quoted match data and a yellow live-deadline tag.
  3. The player selects a pick per match and submits.
  4. Picks are recorded and confirmed.
  5. If a pick is past the deadline, it is rejected and explained; the player corrects open picks and resubmits before the deadline.

Flow D — Reminder before the deadline

  1. The reminder automation evaluates the upcoming pick deadline.
  2. It sends a reminder outbound to members who have not completed picks.
  3. The member receives the reminder and opens Match Picks.
  4. The member submits picks per Flow C.
  5. Failed dispatches are retried by the automation.

Flow E — Member checks live standings and leaderboard

  1. Member opens Standings for the league.
  2. Live standings render with a live indicator and the hazard-stripe band at the top.
  3. The member switches to the leaderboard view to compare rankings.
  4. If data fails to load, the member retries without losing the selected view.
Page 15 of 20

6. Visuals Colors and Theme

Muse: Virgil Abloh. Headline: "Remixed familiarity after Virgil Abloh."

  • Mode: Dark.
  • Colors: background #111111; surface #1C1C1C; text #F4F1EA; primary #FF5A00 (actions, hazard stripes); accent #F2E900 (live data only); muted #8C8C86. Black ground at 70 percent, off-white text.
  • Typography: Headings Archivo Black, all caps, heavy weight, wide tracking, quoted labels in small caps. Body Space Grotesk. Scale 1.333 modular: 56/40/28/18/16; hero 40px mobile to 128px desktop.
  • Shape language: Hard edges, label and tag motifs, hazard-stripe bands, exposed grid lines, industrial framing. No rounded friendly cards.
  • Layout: Asymmetric grid, full-bleed hero, ruled panels; pick rows read like shipping labels with quoted metadata.
  • Imagery: Product on concrete, industrial textures, high-contrast street photography; hazard-stripe decoration only.
  • Avoid: pastel colours, blue accent, white ground, gradient blobs, soft shadows, Inter/Roboto/system fonts.
Page 16 of 20

7. Signature Design Concept

The public entry (Landing) is a full-bleed black hero with a giant safety-orange hazard-stripe band across the lower third. A quoted label sits above the headline; the headline "Picks. Rivals. Live standings." sits left in Archivo Black at 128px desktop and 40px mobile; the subline "Create the 2026 Perditions League, invite your players and track every pick." follows; the CTA "Start a league" is a sharp orange block with an exposed 1px grid-line offset behind it. A thin ticker tape of live standings scrolls across the page edge. The hazard-stripe band repeats at the top of Standings. All readable text and controls stay whole at 375px, 768px, and 1280px, wrapping or scaling with clamp(...); decoration may bleed and crop, text may not.

Page 17 of 20

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject: the hazard-stripe band and the headline block.
  • Thesis: on load, the quoted label and headline snap into place with instant state changes; the ticker tape begins scrolling live standings across the page edge; the CTA block reveals with its grid-line offset.
  • Motion vocabulary: snappy marquees and ticker tapes, tag flips, instant state changes, no soft bounce.
  • Composed first frame: black ground, quoted label above the headline, orange CTA block, hazard-stripe band across the lower third, ticker at the edge.
  • Reduced-motion state: ticker becomes a static wrapped row or horizontally scrollable row so every item can be brought fully into view; no marquee motion.
Page 18 of 20

9. Non-Functional Requirements

  • Persistence: Application-owned durable state for users, leagues, memberships, invites, matches, picks, reminders, and standings/leaderboard, stored in MariaDB. (required_inference, from durable_state_required)
  • Identity: Application-owned identity with anonymous Sign Up and Login entry; protected destinations require an established identity. (required_inference)
  • Background automation: Reminder dispatch runs as backend automation before the pick deadline, with retry on failure. (explicit/required_inference)
  • External delivery: Invites and reminders are delivered outbound to external recipients. (explicit)
  • Responsive readability: Readable text and controls remain whole and uncovered at 375px, 768px, and 1280px; moving content may cross edges by design and must be fully readable as it passes or via scrolling. (explicit, creative direction)
  • Reduced motion: A usable static arrangement is provided under prefers-reduced-motion. (explicit, creative direction)

10. Tech Stack

  • Frontend: React application UI.
  • Backend: Shared FastAPI process hosting application APIs and domain modules, including reminder automation.
  • Database: MariaDB for application-owned persistent data.
  • Infrastructure: docker-compose with backend, database, and frontend services.
Page 19 of 20

11. Assumptions and Constraints

  • The 2026 season is the current league horizon; no other season is in scope.
  • Invites and reminders are delivered outbound; the application owns the records and schedule, not the recipient's channel.
  • Identity is application-owned and self-service; no differentiated permissions beyond organizer ownership of a league and member participation are specified.
  • The creative direction is authoritative for visuals and motion; the entry hero copy is fixed as given.
  • No future-horizon capabilities are defined.

12. Glossary

  • Perditions League: The 2026 sports prediction league created and joined in the product.
  • League Organizer: The user who creates a league and sends invites.
  • League Player: An invited user who joins and submits picks.
  • Match Pick: A member's selection for a match before the deadline.
  • Deadline: The cutoff after which picks for a match are no longer accepted.
  • Standings: Live ranking of members based on pick results.
  • Leaderboard: Ranked comparison of members.
  • Reminder: Outbound message sent before the pick deadline.
  • Invite: Outbound request for a player to join a league, tracked until accepted.
Page 20 of 20
Live
Landing design preview
Landing: Read league features
Landing: Start a league
Sign Up: 1. Submit enrollment
Sign Up: 2. Correct invalid input
Login: Sign in instead
Leagues: 1. Create league
Leagues: 2. Retry league creation
Leagues: 1. Compose player invite
Leagues: 2. Retry invite delivery
Leagues: Track invite status
Match Picks: Set match picks
Standings: 1. View live standings
Standings: 2. Switch to leaderboard
Standings: 3. Retry standings fetch
Live
Landing design preview
Landing: Read league features
Landing: Start a league
Sign Up: 1. Submit enrollment
Sign Up: 2. Correct invalid input
Login: Sign in instead
Leagues: 1. Create league
Leagues: 2. Retry league creation
Leagues: 1. Compose player invite
Leagues: 2. Retry invite delivery
Leagues: Track invite status
Match Picks: Set match picks
Standings: 1. View live standings
Standings: 2. Switch to leaderboard
Standings: 3. Retry standings fetch