My point was that at Google, a single person should not be able to break things to this degree. The automation should roll it back automatically. This is, techn

My point was that at Google, a single person should not be able to break things to this degree. The automation should roll it back automatically. This is, technically due to the drop in recall, a bug, unless it is overridden as a special case so it is not recognized as a bug. To break things this bad you not only should have to make the change to the code but you should also have to "sign off" on the dynamics flagged by the X% rollout test as being acceptable somehow. So no matter what this paints Google extremely poorly -- either Google Shopping is one git commit away from going down completely, or they're placing shipping a hacky, poorly executed political statement higher on their priorities than potentially damaging the livelihood of those who are collateral damage.