Recognize Partner Obligations by Their Identifiers

Context

Retryable partner work can be delivered again after a lost response. Each operation needs a durable way to recognize the same obligation.

Decision

Fulfilment, cancellation, enforcement and decision handling use the partner’s stable identifier to recognize repeated work.

Alternatives Considered

Exactly-once delivery: Exactly-once invocation is not part of these partner delivery contracts.

Membership's own deduplication keys: An unrelated local key would not reliably match the identifier that the partner repeats.

Consequences

Unique stored identifiers support repeated delivery without a distributed lock. Components can request retry while waiting for package fulfilment. Membership-generated order requests use stable decision, action or request keys where applicable.