FA-29604 / HTTP retries / Member archive

Retry reconciliation with a server receipt: An in-progress operation is duplicated or rejected as a content conflict · case 04

An in-progress operation is duplicated or rejected as a content conflict

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

submit(key,body) returns new for absent key, pending for matching in-flight key, conflict for a changed body, and cached(value) for a completed matching key. commit(key,value) commits only existing pending entries. forget removes a receipt. Return decisions and receipt table.

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	`[["new", "new"], {"a": [4, "pending", null]}]`	`[["new", "pending"], {"a": [4, "pending", null]}]`	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.