AAS Archive
The archive is in testingEverything you make here, accounts and runs included, will be wiped before launch on 1 October 2026.

Verify a bundle

Choose a bundle zip. Your browser opens it, recalculates the sha256 of every file and compares it with manifest.json, adds up the playbacks in timeline.json and compares them with its totals, and checks the human axis against the log. Nothing leaves your browser: there is no upload.

or drop the zip here <run-id>.zip, written by aas publish

If the bundle contains a signature.json, the signature over manifest.json is verified as well, provided your browser supports Ed25519.

What is checked

  1. Hashes: every file listed in manifest.json has the listed size and sha256; every file in the zip is listed (except manifest.json itself).
  2. Timeline: the segments' seconds add up to the real time; the playbacks' in-game time adds up to the in-game total; their wall time to the playback total; thinking equals real time minus playback time; every section's in-game time is the sum of the playbacks inside it; the summary's own figures match.
  3. Human axis: a run declared human: none has no run.human record in the published run. A run.human record after completed_at that is followed by a game.goal belongs to a goal extension that is not published yet, and does not count (SPEC §8.3).

This is the same verification anyone can run with the tooling's aas check, except for the timeline format checks.