FA-30450 / HTTP retries / Member archive

Logical request deadline across retry phases: Complete terminal violates retry transition semantics · case 05

Complete terminal violates retry transition semantics

Member previewVariant 5 · 3 implementations · 10 checks per implementation

Case contract

begin(now,budget) pins a logical deadline. advance(time) uses monotonic logical time. queue(delay) schedules retry only for live request, wake starts only after due and strictly before deadline, complete succeeds only for running attempt before deadline. finish/cancel are terminal. Admission at expired time reports expired and closes request; queue never extends deadline. Return scheduling/attempt dispositions.

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	`[[["queued", 7], "early", "started", "success", ["queued", 7]], 10, "queued"]`	`[[["queued", 7], "early", "started", "success", "blocked"], 10, "done"]`	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.