# Governed Release Evidence Pack Template

## Purpose
Use this template to document why a governed adapter release should be trusted, what changed, what was validated, and how it can be rolled back.

## Audience
- Security and assurance reviewers
- Release managers
- Operators and enterprise evaluators

## 1) Release Identification
- Product or integration name:
- Release version:
- Artifact identifiers:
- Release date:
- Release owner:

## 2) Release Thesis
- Why this release exists:
- Risk reduction objective:
- Governance claim strengthened:

## 3) Change Summary
- Functional changes:
- Policy behavior changes:
- Reason code changes:
- Evidence or schema changes:
- Known limitations:

## 4) Artifact Inventory
- Package or image names and versions:
- Checksum or digest references:
- Signed artifact references:
- Distribution scope:

## 5) Compatibility Declaration
- Reviewed combinations:
- Lockdown-only combinations:
- Unsupported combinations:
- Caveats:

## 6) Validation Results
- Health and smoke checks:
- Allow, deny, and constrain results:
- Adversarial or bypass checks:
- Performance or overhead summary:
- Evidence validation summary:

## 7) Rollout and Rollback
- Rollout sequence:
- Monitoring plan:
- Rollback triggers:
- Rollback steps:
- Post-rollback verification:

## 8) Signoff
- Engineering approval:
- Security or assurance approval:
- Release approval: