Datasets:
Reproduce and inspect ELYRION III
Use Python 3.10 or later. First verify the downloaded payload before creating environments or generated files inside it:
python tools/verify_integrity.py
python tools/export_data.py --check
The integrity verifier rejects unexpected files and symlinks and verifies every manifest-listed file's byte count and SHA-256 digest. The manifest does not hash itself; matching it does not authenticate authorship or certify scientific correctness. An extracted payload should match exactly before local editing.
Preserve original outputs
The original scientific scripts write to results/, figures/, and generated table sources. Run them in a disposable copy outside the verified payload if you want to retain the original bytes and manifest validity. Copy the repository to a separate directory, then work in that copy. Create your virtual environment outside the untouched original payload as well.
From the disposable copy:
python -m venv .venv
# Windows: .venv\Scripts\activate
# Linux/macOS: source .venv/bin/activate
python -m pip install -r requirements.txt
python code/verify.py
python code/audit_independent.py
python code/make_figures.py
Expected check totals are 1,305/1,305 main checks and 108/108 independent-code-path audit checks. Five figures are written. The audit uses exact rational matrices and 70-digit mpmath calculations without importing model.py; both implementations originate in the same research session. Timings and floating last digits can vary across Python/numerical-library versions. Dependency lower bounds are supplied, rather than a cross-platform locked environment.
RUN_WINDOWS.bat is the original local verification launcher; dependencies must already be installed. It does not upload or request account credentials.
Optional table and manuscript rebuild:
python code/rebuild_tables.py
pdflatex -interaction=nonstopmode -halt-on-error ELYRION_III_Manuscript.tex
pdflatex -interaction=nonstopmode -halt-on-error ELYRION_III_Manuscript.tex
Rebuilding requires a suitable LaTeX installation. It is not required to read the supplied PDF or rerun the mathematical checks.
Data exports
python tools/export_data.py --check reads the original verification ledger and checks all five exported data files byte for byte. Without --check, the command deterministically writes those files. It does not rerun scientific calculations. Editorial claims are embedded in that script so they are reproducible along with the numerical tables. The check catches export drift; scientific correctness still depends on the source derivations and implementation.
The original release checksum file is retained under docs/source_release/. Its relative paths refer to the original release root. To replay it in its original layout, extract releases/original_v3.zip into a fresh directory and verify from that release root. For the prepared payload, use the new complete manifest verifier instead.
Verification boundary
Finite checks, exact rational instances, high-precision floating calculations, and spatial grid refinement have different roles. None substitutes for general analytic proofs, an interval enclosure of every floating value, a certified PDE discretization error, formal proof-assistant verification, physical fabrication measurements, external peer review, or a systematic novelty/patent search.
The preparation replay is recorded in docs/source_replay_audit.json; original ledgers remain under results/ unchanged.