Four parts of a useful release reference
- Source/build state.
- Artifact identity and checksum.
- Scope and configuration.
- Review or verification reference.
Why evidence stays version-bound
A result from one build, configuration or environment should not silently become a claim about a later release. The public wording therefore distinguishes product description from release-specific proof.
What this page explicitly does not claim: The public site does not expose raw verification archives, internal test logs, vulnerability details, private source paths or secret-bearing evidence.