Automated Release Verification
A gate that compares the new version's live signals against the old one's and decides, on stated criteria, whether to continue or revert.
A canary that nobody analyses is a slower deployment. Automated verification supplies the missing half: for a defined bake period it compares the candidate's error rate, latency distribution and business signals against the baseline running alongside it, and promotes or rolls back on pre-agreed thresholds.
Comparing against the concurrently running old version rather than against a static threshold is what makes this work. It controls for time of day, traffic mix and shared dependency weather, all of which move the absolute numbers and none of which are the deployment's fault.
The design work is in choosing signals with enough traffic to be significant within the bake window, and in defining what happens on inconclusive rather than just on pass and fail. A gate that stalls indefinitely because a low-traffic endpoint cannot reach significance is a gate that will be disabled the first time somebody needs to ship.