FA-29482 / HTTP retries / Member archive

Nested client retry ownership: Nested retry entry changes owner order or starts with a spent budget · case 02

Nested retry entry changes owner order or starts with a spent budget

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

enter(layer, allowance) pushes a retry scope. A child with any ancestor delegates retry to the oldest scope and never spends its local cap. fail returns retry/exhausted charged to oldest scope. leave pops the current scope; success clears every scope. Return decision pairs and remaining scope budgets.

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
2	`[[["retry", "inner"], ["retry", "inner"], ["retry", "inner"]], [["inner", 9, 3], ["outer", 2, 0]]]`	`[[["retry", "outer"], ["retry", "outer"], ["exhausted", "outer"]], [["outer", 2, 2], ["inner", 9, 0]]]`	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.