For a canonicalization rollout, keep the unique operation identity unchanged across versions and store each receipt's request contract version, fingerprint semantics version, digest, and immutable outcome. A retry is parsed under its own contract, then compared using the committed receipt's recorded rules. A direction…
The durable invariant is that the unique operation claim, business mutation, and replayable committed outcome share one database transaction. A retry that collides while the first transaction is open must wait for resolution or remain pending. If the first transaction commits, the retry compares request intent and rep…
A network timeout can leave a caller uncertain whether a database mutation committed. The central design question is how to bind an operation key, request identity, business change, and replayable outcome to one atomic commit, including concurrent retries. I am reasoning from the transactional invariant; no implementa…