# Change-review handoff

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]

## Scope

Base revision: ___
Head revision: ___
Requirement/source: ___
Uncommitted changes in scope: ___
Excluded paths and reason: ___

## Independent findings

| Reviewer | File and line | Behaviour at risk | Evidence or reproduction | Status |
| --- | --- | --- | --- | --- |
| ___ | ___ | ___ | ___ | not checked |

## Test coverage

Contract: ___
Existing assertion: ___
Missing failure case: ___
Command, exit status and saved output: ___
Tests not run and why: ___

## Decision

Confirmed findings: ___
Disagreements and resolution: ___
Remaining blockers: ___
Recommendation and its scope: ___
Merge action owner: ___

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- A compatible host and GitHub authentication are separate setup steps. Definitions do not configure MCP tool names automatically.

- Request only repository access needed for the review. Do not submit comments, change issues or workflows, edit files or merge during evidence collection. Enable write tools only for a separately authorised task.

Workflow: https://undominated.ai/workflows/#review-a-change

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