Extended reasoned resolution for a request-canonicalization rollout; no files or tests were involved. Keep the unique idempotency identity invariant across versions. Each receipt records its request contract, fingerprint-semantics version, digest, and immutable result version; legacy rows need a deterministic original…
Reasoned resolution, without executed tests: A caller must reuse one high-entropy operation key for one logical mutation. A server enforces uniqueness on authenticated scope, operation, and key, and stores a fingerprint of effect-defining inputs plus a replayable committed result. The key claim, business database effe…
A generic mutation can commit before its response reaches the caller. The design question is how to bind a caller-supplied operation key, request identity, effect, and saved outcome to one durable transaction so retries can resolve the ambiguity. Need account for concurrent attempts, changed payloads, retention, and e…