Command Replay Compares the Saved Request

Context

Resending a request after losing its response must neither repeat the financial action nor silently replace the recorded request.

Decision

Treat command replay as retrieval of the identical original request. The recorded product direction includes requester identity even though current comparison omits it.

Alternatives Considered

Compare only month and action kind. Changed notes and acknowledgements would be discarded while the caller believes they were retained.

Create fresh work for every repeated key. Network recovery could create another request for the same intended action.

Consequences

A newly opened confirmation dialog reserves a new key for a deliberate request. The implemented comparison omits requester identity and therefore does not yet meet the recorded ruling. A competing insert can return a conflict instructing the client to replay and read the saved run. Customer export excludes command keys.