# Release & ownership handoff

Project: [name] · Prepared by: [name] · Date/timezone: [date]

## Verdict

Choose one: Not ready / Ready for approval / Released and verified / Released with named gaps.
Do not use “done” without stating the tested scope.

## What changed and why

[Visitor-facing behavior, affected routes and supporting evidence.]

## Source and environment

Reviewed full SHA: [40-character SHA]
Merged source: [full SHA if different]
Environment: [Preview / Production]
Deployment ID and URL: [exact reference]
Live domain assignment: [observed deployment + time]
Build inputs: [unchanged or documented change; names only for environment audit]
CI/local checks: [commands, source, results and skipped checks]

Reuse an existing Ready deployment of the exact source/environment when inputs match. Ready status proves build readiness, not a working task. A verification request alone does not authorize rebuild, promotion or deployment.

## Runtime evidence

| Task / state | Browser / device | Source / environment | Expected | Actual | Evidence | Status |
|---|---|---|---|---|---|---|
| [task] | [physical/emulated] | [reference] | [result] | [result] | [path] | [verified/failed/not tested] |

Keep analytics and mutations blocked unless the exact live test is approved. Provider acceptance and actual inbox receipt are separate observations. Never include tokens, secrets or customer answers in this document.

## Rollback

Known-good source/deployment: [verified reference]
Availability checked: [time + result]
Trigger: [privacy/runtime/task regression]
Authorized operator and scope: [person + exact approval]
Mechanism: [reviewed command or dashboard action; no credentials]
Data/schema compatibility: [applicable constraints or N/A]
Expected consequences: [what reverts, what does not]
Post-rollback checks: [affected task/live domain]

## Open decisions

| Item | Status / reason | Next owner | Next action | Revisit trigger |
|---|---|---|---|---|
| [gap] | [failed/deferred/not tested] | [name] | [action] | [date/event] |

## Ownership transfer

Repository/provider ownership confirmed: [who + how]
Documentation location: [link]
Access transfer: [approved secure process; never paste credentials]
Incident/support owner: [name and approved contact]
Client acceptance: [person/date/scope or pending]
