Proof of Play · ApexLogics Showcase

A contested run is usually one person's word against a leaderboard. This tool folds a run's checkpoints into a single digest where each checkpoint absorbs the one before it, so removing a checkpoint or swapping two of them changes the result. Enter the same checkpoints in the same order and you get the same digest every time, which is what makes a run claim checkable by someone who was not there.

Inputs STEP 1

Run identifier Any label you want stamped into the run, for example a speedrun submission id.

Checkpoints you claim to have hit

Checkpoints in order, one per line One checkpoint per line, for example gate-1:0420. Order matters.

Expected final digest (optional) Paste a digest from an earlier run to check that this run reproduces it. Leave blank to skip the check.

Sequence Status

Verified when count matches and the digest does not mismatch

Final Digest

Folded from run id + each checkpoint in order

Reproduces Expected

not_checked, match, or mismatch

Detail

Run identifier--

Step count--

Declared count--

Count match--

First checkpoint--

Last checkpoint--

Final digest--

Reproduces expected--

execution_hash: --

This is tamper evidence, not anti-cheat enforcement and not DRM. It shows that a submitted checkpoint sequence is internally consistent and reproducible. It cannot tell you whether the checkpoints themselves were accurately produced. Changing checkpoint order changes final_digest — try swapping two lines above and re-running.

Policy Mandate Record v2.0 · what is this?

Exhibit: a worked example that computes in your browser. It is not regulatory-grade output. Source card on AINumbers: industry card c2-2.