Reproduce Release I

Build: MG-RL-13.0-20260926-RELEASE-I. Hosted reference environment: Ubuntu 24.04, Python 3.13, Node.js 22. Reading the publication requires no installation.

From the GitHub repository

git clone https://github.com/MathGov/ripple-logic.git
cd ripple-logic
python -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements-ci.txt
python -B releases/v13.0-release-i/verify_all.py --output-dir ../mathgov-results

On Windows PowerShell, use these commands after cloning and entering the repository. Direct invocation works even when script activation is restricted:

python -m venv .venv
$env:PYTHONUTF8 = '1'
.\.venv\Scripts\python.exe -m pip install -r requirements-ci.txt
.\.venv\Scripts\python.exe -B releases/v13.0-release-i/verify_all.py --output-dir ../mathgov-results

Set PYTHONUTF8 in each new PowerShell session before verification. Several frozen checks read UTF-8 manifests and HTML with Python's default encoding; on Windows installations using a legacy encoding such as CP1252, they otherwise fail with UnicodeDecodeError. The environment variable also reaches the verifier's child processes. It changes the execution environment without editing the frozen publication.

One supplied loopback HTTP test can encounter a Windows file-deletion race. Ubuntu hosted checks are the reference; a Windows failure must be inspected rather than dismissed as a pass.

From the original publication ZIP

Download MathGov_RippleLogic_v13.0_Final_Publication_I.zip and its .sha256 file from Release I. Verify the ZIP before extraction:

sha256sum -c MathGov_RippleLogic_v13.0_Final_Publication_I.zip.sha256

On Windows use Get-FileHash -Algorithm SHA256 <zip-path> and compare with the checksum file. The expected original ZIP SHA-256 is:

c7ece3a604980fa859e41cd63bbebe6d9adc0953e795737c8a38c16b82ac4d85

Extract to a new directory. Create and activate a virtual environment outside the extracted publication. For the maintained environment, download the current requirements-ci.txt alongside that environment. Install it, then run the verifier from the extracted directory containing verify_all.py:

python -m pip install -r /path/to/downloaded/requirements-ci.txt
python -B verify_all.py --output-dir ../mathgov-results

On Windows, set $env:PYTHONUTF8 = '1' before running these checks too, and use the Python executable from your external virtual environment.

Replace /path/to/downloaded/requirements-ci.txt with your actual path. The maintained environment updates lxml and PyMuPDF separately from the frozen specification, and every update must pass the supplied checks. The original release assets retain the first publication environment. To reproduce that historical dependency set specifically:

python -m pip install -r Reference/requirements.txt
python -m pip install rfc3339-validator==0.1.4 six==1.17.0
python -B verify_all.py --output-dir ../mathgov-results

The original requirements omit the optional RFC 3339 validator. Without it, JSON Schema date-time validation is not enforced and the invalid-timestamp test fails. The two additional pins correct the environment; they do not modify the frozen ZIP or specification. The release's initial requirements-ci.txt companion records that original corrected environment; use the repository version for maintained dependencies.

Keep generated results and virtual environments outside the frozen publication. Scoped test success does not establish empirical validity, certification, native Excel recalculation, or production readiness. Read the verification report.

Maintained reading site

With Python and Node.js available, run:

python -m pip install -r requirements-site.txt
python scripts/build_site.py
python scripts/check_site.py
npm ci
npx playwright install chromium
npm run test:site

The builder copies the frozen publication to a new _site/ directory, preserves its homepage as publication-index.html, and adds maintained readers under read/, the formatted installation guide, and a local text-search index. Original Reading_HTML/ files remain unchanged. It refuses an existing output directory. For a fresh subsequent build, choose a new directory with --output <new-directory> or remove only your disposable _site/ output. Tests use the default _site/ location.

Before creating output, the builder verifies the pinned ledger, exact 288-file inventory and every original checksum. Extra local files cause a failure rather than being copied into the public site. Preserve such files outside the release tree; do not delete them merely to satisfy a check. Build from a clean checkout when provenance is uncertain. See current publication status.