Only verified changes land
On this base, a change that has not passed verification does not enter the main line.
What this means for the operating side
- Every change that lands has been verified in its merged state. There is no room for an unverified combination to slip in
- A change that fails stays in the results, with its reason. What stopped, and why, can be checked afterwards
- Promotion to qa (a release) passes through a separate gate. Development momentum does not flow straight into the main line
What you can decide
- You can explain, as a property of the system, how far the changes in a release have been verified
- When something goes wrong, the discussion narrows to “was the scope of verification enough”, not “did it pass at all”