Four pools. One weekly pick. Administrators at the controls.

1Exactly four pools

• Final Clock runs exactly four separate tiers: $10, $25, $50, and $100.
• Each enrollment belongs to one tier for the season.
• Standings, survival state, team history, and winners remain separated by tier.

2Named enrollment

• An administrator enrolls each participant with a public display name and one tier.
• The display name appears on the public standings and may appear in winner history.
• Players do not create accounts or operate an enrollment surface.

3Weekly picks

1. An administrator chooses one team for every active participant from the current scheduled games.
2. A team used in a settled earlier week cannot be used again for the same player.
3. Each save carries the current revision so a stale request cannot overwrite a newer choice.
4. Picks remain private before their reveal boundary; the public board does not expose current choices.

4Deadline and kickoff locks

• Trusted server time decides whether a save is timely.
• A new choice must arrive before the weekly deadline and the selected game's kickoff.
• An existing choice can change only before the kickoff of its originally selected game.
• A save at the exact deadline or kickoff timestamp is rejected.

5Results and missed picks

• A final win advances the player; a final loss or tie eliminates the player.
• The default missed-pick policy eliminates an active player without a timely choice.
• Settlement is replay-safe: the same week cannot advance a player or append the same audit event twice.

The displayed schedule must be reviewed by an administrator. The application does not itself guarantee an official live sports-data feed.

6Public board

The home page is view-only and publishes pool counts, public display names, standings, previous winners, and upcoming games. It contains no player controls or mutation form.

7Administration

• Only active administrators may access the private Admin workspace.
• Administrators may enroll participants, create or change weekly picks, and read the administrative audit.
• Only an owner may add, change, or disable another administrator; the last active owner cannot be disabled or demoted.
• The Admin page is protected on the server and is never part of public navigation.
• Production writes use durable transactional storage and append an administrative audit record.