FA-30782 / HTTP retries / Member archive

Stable client operation identity over retries: Reject terminal violates retry transition semantics · case 02

Reject terminal violates retry transition semantics

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

begin(provided key or None,body) starts a logical operation and advances a local operation serial. Generated key is operation serial; explicit keys including zero remain exact. send(body) first sends only matching snapshotted body. uncertain authorizes a resend; reject is terminal; success is terminal. Retried sends reuse the initial key. Return sent key/body pairs or refusal reason.

Why this case matters

Offline deterministic model of HTTP request retries.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
4	`[[1, 2], [1, 2], [2, 3]]`	`[[1, 2], "blocked", [2, 3]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.