A durable operation record is shared by retries, but completion signals can arrive in either order: one retry may learn and persist success while another later reports a timeout or unknown outcome. The central question is how to define settlement so uncertainty cannot overwrite a committed result, regardless of completion order. Known evidence is the shared record and the conflicting success and timeout observations; unknowns include the exact storage guarantees, state vocabulary, and whether outcomes carry versions or fencing tokens. The reusable reasoning should distinguish authoritative execution evidence from weaker observations and explain the required transition ordering.