Appendix B — Status, provenance, and attribution
B.1 This documentation build
Source revision: 6e3bd67a5. Full commit identifier: 6e3bd67a5a6bd65c52c9cb5b3a0035d05f04d8bf. Rendered 2026-10-24 16:19 UTC.
This book publishes the source snapshot and supplied measurements, not a new execution of the science suite. A modified working tree is labeled in the revision. Test evidence carries its own source fingerprint and scope; performance separates kernel from full-run timings.
B.2 What is and is not certified
| Claim | Evidence required |
|---|---|
| Documentation integrity | Successful render, source provenance checks, local link/fragment check |
| Current extraction CPU tests | Current scripts/validate.jl --backend=cpu record and log |
| Metal/CUDA hardware correctness | Separate successful record on that device, with documented coverage |
| A physical recombination or PMF conclusion | Matched temporal/spatial/spectral/start-redshift/chemistry convergence artifacts |
| Full Boltzmann or nonlinear Lyman-alpha accuracy | Not established by the current P1/smoothing/response-table model |
| Reproduction of all Schiff 3D results | Not claimed by shipping linear reference tools or example configurations |
Historical upstream Metal gates and performance figures are not current extraction certification. Source support for CUDA is not CUDA hardware validation. A NOT_RUN device stays unmeasured even if another backend passes.
B.3 Source lineage
- MHD and Poisson sources were extracted from Vespa’s
lib/MHDKernelsandlib/PoissonKernels; the full runner descends fromMHDKernels/test/pmf_dm_lattice_bench.jl. - Chemistry and emission are bundled from
ChemistryKernels.jlandEmissionKernels.jl, preserving their source and license notices. - Portable Schiff/LMHD, photon, and Lyman-alpha reference/analysis algorithms descend from
vespa-runs/tools/sv25_reference. Their own provenance lists copied source hashes and adaptations, including dirty-working-tree content. - This book adapts the actual Quadrant template: its Quarto book structure, brand palette, theme-aware tokens, source/test provenance conventions, numbered math, notation/status appendices, and footer. Rustdoc resolution was replaced by checked local Julia source snapshots; there is no WebAssembly simulator or fabricated laboratory.
The machine-readable extraction record is provenance/extraction.json; the independent science tools use tools/reference/provenance.json. Subsequent standalone fixes can intentionally differ from the initially recorded imported hashes. Use the run’s source_fingerprint_sha256 for its actual implementation.
B.4 Licensing and credit
The integration, extracted project-owned numerical/reference code, and documentation are distributed under the root BSD-3-Clause license, with CITATION.cff providing the software citation. Retain per-component notices. Chemistry/Emission retain their University of Illinois/NCSA-style Enzo license text. Do not infer that those licenses automatically cover external manuscripts, datasets, or software. The extraction provenance records the source state; the root license supplies this distribution’s terms for the project-owned reference implementation.
Credit the original scientific algorithms, source projects, reference models, and the specific numerical/physics modifications used for a result. Cite Schiff/Venumadhav or Jedamzik/Abel work only for the model actually compared; the package’s examples are not a replacement for reading the original papers. No paper acceptance, DOI, or historical campaign certification is asserted here.
B.5 How to cite and share
The repository’s CITATION.cff supplies citation metadata without inventing a software DOI. Cite PMFGLM.jl, Tom Abel and contributors, the repository, the exact commit or source fingerprint, and the numerical model/settings used. Include reference-tool provenance for oracle-based comparisons. Do not cite an uncommitted working tree as if it were an immutable release.
Share configurations, resolved environments, raw tables, test records, logs, and scripts with figures. Hypothesis annotations are available for discussion; GitHub issues and edit/source links support corrections. Avoid publishing machine-local paths, private data, or huge checkpoints without review.