What problem does it solve? Teams often ship artifacts that were rebuilt after testing, rely on evidence bound to a different build, or overstate readiness in release notes. This Skill enforces a release-governance boundary so only the exact accepted artifact, with provenance, rollback, and truthful claims, is promoted to a defined distribution scope. ## Core Features & Use Cases - Artifact Identity & Evidence Binding: Freezes candidate identity with SHA-256 digests, version metadata, and source commit, and blocks release when bytes change after acceptance. - Release Gate Matrix: Evaluates distinct gates (build, tests, verify, review, security, recovery, signing, owner acceptance, distribution authority) and returns a structured decision such as RELEASE READY, REVERIFY CANDIDATE, BLOCKED, or STOP. - Provenance, Rollback & Truthful Notes: Records supply-chain provenance, verifies the rollback target before promotion, and checks that release notes never claim more than the evidence supports. - Use Case: Before publishing a signed installer to beta users, run this Skill to confirm the signed bytes match the tested digest, the previous stable build remains recoverable, and the release notes accurately state scoped security results. ## Quick Start Ask the AI to evaluate whether the current build artifact is release-ready for a beta distribution using the signalproof-release gate matrix.
