League Operations
Concept ready- Open interactive page system →
- Draft Room
- League selection and creation
- Commissioner Center
- Data Operations
- League History
The review home for every V2 page, interaction surface, and supporting concept. Open any completed concept, confirm its status, and return here to track the remaining modernization work without mixing V1 or production changes.
Each concept is authored for mobile, foldable, and desktop unless its card says otherwise.
Navigation, responsive background behavior, collapsed header, Page Actions, and viewport-safe overlays.
Live matchup header, persistent composer, reactions, event drops, animated football effects, and responsive chat.
Weekly command center, featured matchup, league scoreboard, quick actions, and cohesive full-page atmosphere.
Lineup, reserves, matchup lab, league scout, compact player rows, and reserve ordering.
Search, team and position pickers, readable game state, matchup difficulty, profiles, and roster actions.
League-scored production, consolidated filtering, evidence context, data views, and player profile access.
Playoff race, weekly matchups, responsive standings, cutoff treatment, and dynamic postseason bracket.
Challenge arena, live stakes, leaderboards, proposal builder, settlement states, and protected commissioner actions.
Decision command center, actionable cards, highlights, team intelligence, market context, and bulk selection.
Dedicated workspaces, nested rules, scoring presets, compact steppers, and reviewable unsaved changes.
Direct and three-team deals, team portrait switching, player evidence, routed FAAB, capacity plans, and deferred execution.
These surfaces keep their existing capability while receiving V2 concepts before application changes.
One reusable overlay contract will control viewport edges, translucency, motion, focus, scrolling, and dismissal.
Earlier audits and interaction studies that remain useful while Section 12 is designed.
The V1 contract has now been mapped to the accepted V2 experience system without changing V1, production, or provider authority.
C:\Users\Bizzy\Documents\Codex\2026-09-14\how\2-and-11\BDL_V2_DATA_CONTRACT.md. V2 consumes the V1 Worker's normalized contract and never calls BDL directly, exposes credentials, substitutes provider fantasy totals for league scoring, or creates a second merge layer.