Free field guide, page 4, from chapters 10, 21, 22, 49 and 54
One attempt, one identity
The client creates the key before durable acceptance and reuses it for every replay; the server keeps a ledger of canonical results.
Born with the intent.
Before the intent is accepted, owned by the durable command. Not at the tap, and never in the transport adapter.
Claimed before the work.
A production ledger claims the key before it books, so only one request wins and a concurrent replay gets an in-progress status. The single-threaded simulator leaves this part to you.
Answered from the ledger.
A replay returns the stored outcome: the receipt, or a business rejection such as a conflict. Nothing runs twice.
Remembered long enough.
Longer than a phone can hold the operation, counting queue age and time offline. Past that window, look up the affected entity by its stable client reference instead of replaying.
