# Release verification packet

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Artifact

Revision/version: ___
Archive path and SHA-256: ___
Expected entry points: ___
Frozen at: ___

## Consumer

Clean environment/runtime: ___
Exact install/run command: ___
Exit and saved output: not run
Observer: ___

## Public proof

| URL | Checked at | Status | Required identity marker | Body path/hash |
| --- | --- | --- | --- | --- |
| ___ | ___ | not fetched | ___ | ___ |

## Release disposition

Local identity: not checked
Public identity: not checked
Runtime: not checked
Rollback target/procedure: ___
Rollback actually exercised: ___
Unresolved release blockers: ___

## Boundaries

- The offline checker validates supplied files and declared runtime evidence; it does not contact the site or establish that an installation happened.

- Verification is not deployment authority. Public queries, installation scripts and rollback operations each need the permission appropriate to their actual effects.

Workflow: https://undominated.ai/workflows/#verify-a-release-and-rollback

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.