Write acceptance before implementation
Describe the intended change in observable terms. Which ownership, binding, permission, document state or business result must be true? Identify who can accept it and which evidence they need.
Keep intended and effective state separate
A pipeline can report that it sent an update successfully while the business operation still fails. Read back the relevant state and test the actual journey under the right identity.
Retain exceptions as evidence
Missing permissions, unavailable systems and incomplete source evidence are conditions to report and resolve. Do not turn them into a green indicator by omitting them from the denominator.
Make recovery part of acceptance
A controlled release needs a defined recovery route, tested at an appropriate level. Document what the backup covers, what it does not cover and who is responsible for recovery decisions.