Reproduce the Paper

This page is the published-docs counterpart to the repo-level REPRODUCIBILITY.md guide. Use it when you want the shortest supported path for replaying the paper-facing artifact bundle without digging through legacy scripts or CI config.

The canonical rerun surface is the committed artifacts/paper_2026/ bundle plus the top-level make reproduce-* shortcuts that mirror its frozen commands.

Quickest supported path

From a clean checkout:

python -m pip install -r requirements-paper.txt
python -m pip install -e .
make reproduce-paper

To rerun one frozen domain instead of the full suite:

make reproduce-dose
make reproduce-rf
make reproduce-ik
make reproduce-reference-robotics

Override REPRO_ROOT if you want outputs outside the default results/paper_2026/ tree, for example make reproduce-dose REPRO_ROOT=results/tmp_repro.

What the paper bundle freezes

artifacts/paper_2026/ records the current paper-facing replay contract:

  • manifest.json: artifact metadata, package version, git commit, and pinned CPU/GPU container recipes.
  • commands.json: exact replay commands mirrored by make reproduce-*.
  • configs/: captured argument snapshots for each replay command.
  • expected_outputs.json: required files under each output root.
  • metric_tolerances.json: allowed drift bands for rerun comparisons.
  • checksums.sha256: SHA256 digests for the committed inputs that define the bundle.
  • archive_record.json: DOI archive status and published Zenodo DOI for the paper artifact snapshot.

Paper Version And Bundle Schema

The canonical package pin for reproducing the paper artifact bundle is zeroproofml==0.4.3; use the matching release tag v0.4.3 when replaying from a release checkout. artifacts/paper_2026/manifest.json records "package_version": "0.4.3"; keep that manifest and each bundle's recorded schema metadata with the artifact, and do not reinterpret paper-era bundles under newer strict-inference bundle schemas.

Native and containerized reruns

  • Native CPU: Python 3.10 with pip install -r requirements-paper.txt, then pip install -e .. requirements-paper.txt delegates to the shared requirements-bench.txt lock used by native benchmark reruns.
  • Containerized: build one of the recipes listed in artifacts/paper_2026/manifest.json and mount the repo at /workspace.
  • DOI archive: artifacts/paper_2026/archive_record.json records the published Zenodo DOI 10.5281/zenodo.18944465 and record URL https://doi.org/10.5281/zenodo.18944465.

What to keep for an auditable rerun

For a paper-grade replay, retain:

  • the repo commit you ran,
  • the relevant files from artifacts/paper_2026/,
  • the produced run directory under REPRO_ROOT,
  • the generated run-local manifest.json / provenance.json files.

Where to go next

  • Start at 21_experiments.md for the broader benchmark, deployment, and archived-workflow map.
  • Keep REPRODUCIBILITY.md as the compact repo-root version of this same guidance when you need a top-level file outside the published docs site.