Feature: Waivers
Tied to journey: Waivers.
Product acceptance criteria
- Managers can submit waiver claims
- Priority / FAAB rules apply as configured (TBD default)
- Processed claims update rosters atomically
Architecture
Scaffold — honest TBDs; do not invent locked product decisions.
- Client surfaces — Waiver claim submit / pending claims; free-agent browse if distinct from waivers (TBD). iOS/Android twins.
- Domain model — WaiverClaim, WaiverPriority or FAABBudget (model TBD — OD-2), ProcessRun. Atomic claim → roster update.
- Data & APIs — Reed owns claim submit and process contracts (TBD). Auth + membership required. Process schedule TBD.
- Cross-feature dependencies — Updates Roster; requires league membership (Leagues); Auth gates writes. May interact with lock timing (OD-4).
- Platform notes — Twin parity for claim UX; process job is server-side.
- Open decisions — OD-2 priority vs FAAB; process schedule TBD.
Implementation notes
- (priority vs FAAB, process schedule TBD)