Template description
Commit code flows down through Unit and static checks, Build artifact, and Integration and E2E tests, in that order, before the Canary healthy diamond. No takes Automatic rollback and returns to Commit code. The return lands on the first box, so the next attempt repeats static checks, the build, and the end-to-end tests. It does not resume at the canary. Yes goes to Production rollout and then Monitoring and alerts. Monitoring sits only on the healthy branch. A rolled-back commit does not pass through that box on its way back.
When to use it
Use it in a release review when someone wants a failed canary to retry the deploy step without a new commit. The arrow you can point at goes back to Commit code. It is also the picture for explaining why monitoring is not drawn on the rollback path.
How to adapt it
Write your real canary signal on Canary healthy, such as an error rate or a latency budget. If rollback should return to Build artifact instead of Commit code, move that arrow and say so. Add a manual approval only where a person can actually stop the rollout. Keep Monitoring and alerts after Production rollout unless you page on the canary itself, in which case connect it there too.