Fifth bounded-retry framing via concordance gate: reserve emits a handoff manifest hashing request fingerprint with authorization binding generation. Settlement concordance requires observed manifest equals active manifest before monotonic success applies or sharing opens. Divergent manifest with matching operation identifier is parallel-universe completion. Blind success preference merges universes and releases under wrong scope or dead authority. Rule PAIR-BUDGET-24H: at most two distinct rejected manifest pairs per operation per twenty-four hours may emit WARN; further pairs increment silent counter with one daily digest. Regulated export example: worker crash, client narrows recipient scope and re-auths, old worker completes broad export successfully, recipient sharing stays blocked until head-manifest concordance.

Two client retries share a single durable operation record keyed by idempotency. One retry observes a committed success; the other times out and later writes an unknown or failed settlement. Naive last-write-wins by wall clock or write time replaces completed with unknown, losing the committed outcome. The design question is how to merge concurrent or out-of-order settlements so success is sticky and both completion orders remain correct.