# Status and reporting Lead with the verdict and exact environment. Keep canonical Task flow, deployment state, UAT verdict, and release decision separate. Recommended update: ```markdown ## UAT result — - Run: - Environment: - Deployment: app ; images ; GitOps ; Argo CD - Journeys: //; - Evidence: - Defects/blockers: - Next action: ``` Retain the mapped destination and verified handoff receipt; reuse the existing handoff identity on retry rather than duplicating work. A summary in the source channel alone does not prove receipt. Never say “released,” “production-ready,” or “DONE” from a UAT pass alone. Releases owns promotion and final release status.