Skip to verification
WORKBENCHTower Defence

Public record

Every saved run keeps how it was made

Provenance is assigned automatically when the replay is created. A Finder, Runbook, or Fork run cannot be presented later as an unaided Ranked Challenge.

Open the LeaderboardRead the rules catalog

The five provenance modes

Solo

A Standard run played without Finder, a Runbook, or a replay fork.

Finder

A result produced by Strategy Finder or by branching from a Finder search.

Runbook

Standard play with a step-by-step build guide beside the board.

Fork

A continuation created from a position inside a saved replay.

Challenge

A locked Ranked Challenge run begun with a valid server-issued ticket.

What CERT means

  1. The player requests a ticket that locks difficulty, game version, and a server-chosen seed.
  2. The game disables Strategy Finder and guided builds for that run.
  3. The submitted replay must contain the matching challenge provenance and ticket.
  4. The server validates the ticket signature, published rules identity, replay trace, and one-use nonce.
  5. A private verifier re-simulates the complete action trace under the exact rules build.
  6. CERT is awarded only when the re-simulated state matches the claimed result exactly.

CERT is a narrow technical claim. It says that a locked Ranked Challenge replay passed the published verification checks. It is not an account identity, a claim about who operated the device, or a general endorsement.

What the public Leaderboard accepts

  • An explicit game version and an internally consistent rules snapshot
  • A version and rules fingerprint present in the published D1 rules catalog
  • A deterministic action trace and matching outcome-state checksum
  • Recognized automatic provenance; unlabeled, experimental, or foreign saves fail closed

All public categories can contain submitted runs. Competitive outcome categories filter those records; an empty category does not imply that submissions were lost.

Public and local boundaries

Replays stay on the player’s device until they deliberately submit a save to the public Leaderboard. A submitted run can include a chosen nameplate and coarse device context used to describe the conditions of play. The game does not publish full browser strings, IP addresses, ticket secrets, or private client identifiers.

Share this explanation

Send the canonical provenance and CERT reference.