# Make a release decision with evidence

Taiga Learning · Worksheet
https://taiga.training/en/lessons/release-decisions/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Identify what a release decision must refer to.
- Distinguish merge, deployment, and feature exposure.
- Define conditions for stopping or reversing a release.

## Exercise
Prepare a fictional release note for the customer export. Include the commit, artifact digest, environment, authorization check, migration effect, monitoring owner, and recovery trigger. List one condition that would stop the release even if unit tests pass.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Accept a specific artifact for a specific environment under explicit conditions. Recheck the decision when the artifact, target, or material assumptions change.

## Sources
- [NIST: Secure Software Development Framework](https://csrc.nist.gov/pubs/sp/800/218/final)
- [SLSA: provenance](https://slsa.dev/spec/v1.2/provenance)

This worksheet supports learning. Completing it does not itself authorize a production change.