We’d like to see something similar too for overall code in quality gates. Racketing makes sense for small organisations but in large enterprises with thousands of projects, agreeing on the amount and frequency to rachet is a ridiculously difficult activity. Leaving it to individual teams is also not practical if you have centralised control of quality gate configuration as we do.