A reversible operation has a tested recovery path that restores the state that existed before the action. Examples can include versioned edits, staged deployments and changes backed by complete snapshots or compensating transactions.
Reversibility reduces risk but should not be assumed from an available undo button. Teams need evidence that restoration covers dependencies, side effects and external systems, and that recovery remains practical at the operation's expected scale.
