Run the whole event from one panel
Per-league admin at /[slug]/admin: quick score entry, add / edit / remove players, a +/- gold toggle for on-the-spot corrections, and tournament settings (title, location, end time, prize, QR). Each store has its own password — it can never see or touch another store's data. This is the one panel a shop needs to run an event start to finish.
The person running a High Noon tournament is standing at a table with players waiting, not sitting at a desk. If scoring is slow or clumsy, the event stalls and the organizer stops wanting to run them — which kills the whole retention loop.
Corrections are constant in live play: a mis-tallied gold, a player who shows up late, a name typo on the board. The organizer needs to fix any of that in seconds, in public, without breaking the standings or touching a database.
And every one of those controls has to be tenant-safe. A store's admin should be able to run its event freely while being structurally incapable of seeing or altering a neighboring store's league.
Everything to run an event, nothing that reaches another store.
Quick score entry plus add / edit / remove players inline. Get gold onto the board and players into the event without leaving the panel or losing the room's momentum.
A +/- gold toggle makes live corrections a single tap — fix a mis-tally or reward a bonus on the spot without hand-editing totals or risking the standings.
Title, location, end time, prize text, and the join QR are all editable per event, so the public board and TV view always reflect what this store is actually running today.
Live in production; here's what's shipped and what would harden operations.
Origin: An organizer runs an event standing at a table; scoring and fixes must be seconds-fast and tenant-safe. Built as the operator surface of the platform.
Prereqs: None outstanding — rides the multi-tenant engine and Redis data layer already in production.
Status: Live in production with per-store auth proven at real events. A3 (audit log, staff roles, bulk actions) is operational depth for later.
Internal strategy page. Keep this honest as the build changes.