FA-30295 / HTTP retries / Member archive

Conditional mutation retry reconciliation: Retry consumed violates retry transition semantics · case 05

Retry consumed violates retry transition semantics

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

begin(version,desired) creates a pending conditional write. sent records that it may have reached the server; lost means response absent. inspect(version,value) after loss reconciles: desired value at version+1 is committed, unchanged original version permits retry, any other state conflicts. retry only from retry state retains original precondition and desired body. ack(value) succeeds only for an active sent request. Return decisions and outgoing retry preconditions.

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
1	`["retryable", ["send", 5, 14], ["send", 5, 14], "ignored"]`	`["retryable", ["send", 5, 14], "denied", ["success", 14]]`	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.