After applying the current path correction for ./verify (archive/v1/...) and installing the pinned verification requirements in a Python 3.11 venv, the proof replay reaches the production pipeline but fails the published hash comparison.
Command:
python3.11 -m venv .venv
. .venv/bin/activate
python -m pip install -r archive/v1/requirements-lock.txt
PATH="$PWD/.venv/bin:$PATH" ./verify
Environment reported by the script:
Python: Python 3.11.15
numpy: 1.26.4
scipy: 1.14.1
Result:
Computed: 2efdeb5a926a0cf881471bf18e4e4a6865e33bbdff667ba59b34ab665d2081cc
Expected: 8c0680d7d285739ea9597715e84959d9c356c87ee3ad35b5f1e69a4ca41151c6
Status: MISMATCH
The production random scan then reports clean. This suggests either the expected hash is stale or the verification pipeline has platform/version-sensitive output despite the pinned requirements.
Environment: macOS arm64.
After applying the current path correction for
./verify(archive/v1/...) and installing the pinned verification requirements in a Python 3.11 venv, the proof replay reaches the production pipeline but fails the published hash comparison.Command:
Environment reported by the script:
Result:
The production random scan then reports clean. This suggests either the expected hash is stale or the verification pipeline has platform/version-sensitive output despite the pinned requirements.
Environment: macOS arm64.