Signing and Provenance¶
Release integrity depends on declared signing and provenance inputs rather than after-the-fact manual notes.
Purpose¶
Use this page to verify the release trust chain before any distribution or installation claim is made.
Source of Truth¶
ops/release/signing/checksums.jsonops/release/signing/release-sign.jsonops/release/signing/release-verify.jsonops/release/provenance.jsonops/release/signing/policy.yaml
Trust Chain¶
The release trust chain currently ties together:
- the checksum inventory for governed release artifacts
- the signing output generated for the release
- the verification output, which records contract checks and overall status
- provenance that binds the release to Git identity, policy path, and toolchain
Operator Verification Path¶
Before distribution, confirm:
checksums.jsoncovers the required release artifactsrelease-verify.jsonreportsstatus: ok- provenance points to the expected release identity and signing policy
- the evidence manifest and checksums still agree on the artifact set
Related Contracts and Assets¶
ops/release/signing/ops/release/evidence/ops/release/provenance.json