What can be independently verified
Release v2.1 publishes a machine-readable identity and SHA-256 manifest so downloaded data, citation, discovery and workflow files can be checked against this build. A checksum establishes byte identity—not correctness, professional review, certification or external recognition.
Release identity
- Public release
- v2.1 · 2026-07-25
- Evidence content
- v1.7 · Article claims, source relationships and evidence datasets are not relabelled as new evidence by a workflow release.
- Independent-review workflow
- v2.0 · zero independent external reviews are publicly recorded.
- Correction workflow
- v1.9 · zero material correction records are publicly logged.
Machine-verification entry points
How to verify
- Download SHA256SUMS and the public machine files to be checked.
- Calculate each file digest with a local SHA-256 tool.
- Confirm byte identity only when both the file path and digest match.
Coverage and limits
The manifest covers public data, citation, feed, discovery, robots, sitemap and release-identity files. It does not cover HTML pages, images, styles, scripts or server configuration. Server transfer, browser caches and later releases can change files, so verify the version in release.json at the same time.
The site does not invent a DOI, source-code repository, open-data licence, third-party certification or institutional seal; metadata does not conceal those absent conditions.