Event policy
Registration windows, capacity, roster lock, attempts, start windows, close time, course reveal, and evidence release become explicit policy.
PRODUCT / 02 / EXPANSIONRun the
Run the
arena.
LedgerLayer Compete expands the same evidence substrate into registration, event policy, participant sessions, authoritative admission, ranked results, and leaderboards — without moving gameplay rules into platform core.
SERVER AUTHORITY WITHOUT GAME COUPLING
The platform knows
competition.
Actions remain adapter-owned data. The competition runtime checks session identity, seat, sequencing, coordinate windows, terminal state, and policy before asking the adapter whether the game action itself is legal.
REGISTER→LOCK ROSTER→OPEN SESSION→ADMIT ACTIONS→DERIVE RESULT→RANK
Short-lived sessions
Browsers and clients receive narrow participant capabilities rather than organizer credentials or signing keys.
Realtime gateway
Sessions, seats, sequence fencing, reconnect, start commit, and terminal boundaries stay universal.
Policy plugins
Best-of-three, survival, head-to-head, highest score, lowest moves, brackets, and round robin rank results without entering engine code.
Verified leaderboards
The leaderboard consumes verified result projections. It never needs to understand Runner distance or Snake food itself.
History that survives
Competition manifests, engine versions, receipts, and publication states remain inspectable after future releases.
VERIFY FIRST / COMPETE NEXTMove authority into
Move authority into
the competition layer.
Compete is the natural second product after the Verify trust loop is stable with external customers.