Replicate the record yourself

Path A — packaged (pip):

pip install yuclaw
yuclaw replay-lab            # fetches the published bundle and verifies it

Path B — standalone (Python ≥ 3.10 standard library only, no installs):

curl -sO https://yuclawlab.github.io/yuclaw-brain/replay/lab_replay_bundle.json
curl -sO https://raw.githubusercontent.com/YuClawLab/yuclaw-brain/main/tools/replay_lab.py
python3 replay_lab.py lab_replay_bundle.json

Both paths rebuild the decile cohorts from bundled scores, recompute every statistic (bootstrap CI with the published seed, Fama-MacBeth IC with Newey-West correction, market-model alpha), and recompute every sha-256 leaf and daily root against the public yuclaw-trust ledger. Verifier vocabulary: a day counts as exact when the recomputed daily root matches the anchored root byte-for-byte; it counts as an anchored-subset day when the anchored block committed a SUBSET of that day's entry hashes (an intraday re-run anchored before the day completed) and every anchored hash recomputes unchanged from today's data — fewer hashes anchored, none mutated. The replay output names both counts separately; a subset day is a disclosed anchoring artifact, not a verification failure.

• Exit code 0. Any statistic or hash mismatch exits non-zero with a diff report.
• Statistics match the bundle's published expected block exactly (same seed, same estimators).
• Ledger roots match — every recomputed daily root equals the root committed to the public yuclaw-trust repository.
• Build metadata matches — the bundle's data-through date, build date, and source commit agree with the page and packet you downloaded them from.

File a Replication report issue using the template (.github/ISSUE_TEMPLATE/replication.md). Required fields: OS · Python version · exact command · bundle build metadata · sha-256 of the output · result (PASS / FAIL with the mismatch report verbatim). Reports are added to the public log below, unedited.