League Rules

Purpose

This page defines system-enforced league governance rules that are currently codified in the application.

Policy

1. Account player-slot limit is one player per user by default (CONFIG_USER["MAX_PLAYERS"] = 1).
2. Team-management actions require a valid single-team manager context; requests from users without a valid managed team are rejected.
3. Standard contract offers are restricted to the FREE_AGENCY phase.
4. Contract extensions are treated separately from standard free-agent offers and can follow extension-specific flow controls.
5. Team and rookie option decisions are restricted to MORATORIUM or FREE_AGENCY.
6. Player option decisions are owner-scoped and only shown for pending options during MORATORIUM.
7. Declining a final pending player option during MORATORIUM can move the player to free agency and set extension_rights_team.
8. Staff-gated operations require explicit permissions, including:
9. pay_players
10. mark_upgrades
11. manage_fa_offers
12. manage_game_entries
13. log_streams

Operational Notes

• Phase enforcement for offers/options is implemented in view-level guards and decorators.
• Staff authorization is implemented through model/admin permissions and protected views.

Known Gaps (TBD)

• Onboarding, verification, and alt-account policy.
• Sportsmanship and conduct standards.
• Collusion, tanking, and loophole abuse definitions.
• Inactivity thresholds and enforcement ladder.
• Appeal process and commissioner override policy text.

Change Log

• 2026-03-15: Initial scaffold created.
• 2026-03-18: Replaced scaffold with repository-backed governance policy baseline.