A service review now needs errors that remain recognizable, validation that preserves legitimate zeroes and state changes that either complete or leave the input alone. The fresh examples include a wrapped missing-record error, an exact stock balance and two independent validation failures. You have used every operation already. Keep the failure result separate from the state it leaves behind. A function that reports refusal after changing half a record is still incorrect. These are local in-memory contracts; they do not claim database isolation or distributed coordination. Explain the identity a caller can inspect, the boundary each field must satisfy and the first point where an update is allowed to mutate state.