Reference
996102e0
Documentation provenance
The public GazeAudit site follows the repository’s default branch and therefore can document post-release development as well as the stable v0.2.0 package. Scientific validation records that are explicitly frozen remain governed by their protocol/source fingerprints and are not rewritten by documentation updates.
Stable software release
- Stable package release: v0.2.0
- GitHub release: v0.2.0
- PyPI: gazeaudit 0.2.0
- External publication verification: release/0.2.0-external-publication-verification.json
- Archived v0.1.0 Zenodo DOI: 10.5281/zenodo.22757340
The v0.2.0 publication record verifies the GitHub Release and PyPI Trusted Publishing payload. It explicitly records that Zenodo was not published in the v0.2.0 release tranche, so the v0.1.0 DOI must not be presented as a version-specific DOI for v0.2.0.
When reproducing an analysis, cite and install the release/version actually used rather than assuming that current main is equivalent to v0.2.0.
Current documentation build
This page was built from repository revision 996102e038eaf74a5665d719cd9e0c4a9da504ca.
Inspect this exact revision on GitHub.
The documentation site can therefore move ahead of the stable package release while preserving an inspectable source revision for every GitHub Pages deployment.
What remains immutable
The protocol-bound validation outcomes incomplete, robust_negative, and materially_fragile remain tied to their authoritative frozen protocols, source identities, decision rules, and evidence artifacts. Documentation, navigation, examples, or later package releases do not retroactively change those scientific records.
The archived v0.1.0 Zenodo deposit also remains a version-specific software archive for that release.
Recommended citation practice
For manuscripts or archived analyses, record all three when applicable:
- the installed GazeAudit package version;
- the Git commit used for development functionality not represented by the installed release;
- the DOI or frozen validation artifact when relying on a protocol-bound archived record.
This separates software identity, documentation identity, and scientific-evidence identity rather than collapsing them into one version label.