Requester notices favour at-least-once delivery over strict once-only

Context

Several settlement paths can invoke delivery for the same job outcome.

Decision

Use a job-and-outcome record to suppress new claims after delivered or suppressed results. Reclaim pending and failed records when delivery is invoked again. The outcome writer has no claim ownership check.

Alternatives Considered

Keeping locks across delivery introduces network-dependent locking. Permanent reservation would lose notices when a sender stops.

Consequences

The protocol reduces sequential duplication but establishes neither guaranteed delivery nor a single sender.