06Section

On-device

Security, reproducibility and the hardware we compute on. The match data never left our laptop, and every result can be rebuilt byte for byte.

Everything happened on one laptop. The competition data was processed in a sealed, offline container, never committed and never uploaded. The pipeline is pinned from base image to last dependency, so anyone can rebuild our exact output. And the chip that ran it has room to spare for what comes next.

  • offline container
  • byte-identical runs
  • Windows on Arm
  • CPU · GPU · NPU
01 02 03 04
  1. Security & Data Protection

    The match data never left our laptop. It was processed in a sealed, offline container, never committed and never uploaded, and only aggregate numbers were ever published.

  2. Reproducibility

    Same inputs, same bytes. A digest-pinned image, pinned dependencies, frozen parameters and a deterministic decoder: anyone can rebuild our exact output file in three commands.

  3. Machine & Hardware

    The match data could not leave our hands, so the compute came to the data. One Snapdragon X Elite laptop: its CPU decodes a full match in under 10 seconds, and its GPU and NPU are the headroom for local models.