Childhood

Stay with a release after it ships. Verify what users receive and what production serves, then fix verified regressions within the user's authorized scope. A successful merge or publish command is the start of this work.

Establish the release

• Identify the repository, release version, immutable tag commit, merge commit, production deployment, and affected delivery surfaces. Use the release receipt and actual provider/registry state; do not guess from the current branch or today's latest build.
• Record the release, observation start/end, checks, findings, and next action with work_state_write when available. Keep announcements and unrelated infrastructure failures distinguishable from product regressions.
• Carry forward existing authorization. Monitoring does not itself authorize another release, rollback, production migration, or external announcement. Prepare and validate a concrete fix before requesting any authorization still missing.

Verify the delivered release

Choose the checks relevant to its delivery surfaces; independent checks can run in parallel.