# Review a Taiga delivery with evidence

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

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

## Learning objectives
- Trace a delivered behavior back to its requirement and plan.
- Identify incomplete checks and assumptions that need review.
- Distinguish run completion, merge, deployment, and user availability.

## Exercise
A fictional employee-access change has a passing build and a run note saying an integration test could not execute. Write the evidence needed before accepting it. Include one denied-access case and the exact artifact or commit under review.

## 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
Review the current artifact and its evidence. A confident summary or completed run does not establish that every acceptance condition is met.

## Sources
- [Taiga docs: Runs](https://docs.tai.ga/deliver/runs/)
- [Taiga docs: Autonomous merge](https://docs.tai.ga/deliver/auto-merge/)
- [Taiga docs: Deployments](https://docs.tai.ga/deliver/deployments/)

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