Cairn Docs Claims Blog Packages

Claim ยท cairn 0.5.2

cairn^1105 A retry comes due

A move of cairn 0.5.2.

Id
cairn^1105
Kind
move
Reads as
proved
Version
0.5.2

All of cairn 0.5.2's claims

What you do

Key k's backoff timer fires.

What you see

A key waiting after a failed read sends the next read; the server is unchanged.

Evidence

provedsound pressCairn.Optimistic.Claims.retry.press.sound
fuzzedNot shown yet: the claim-driven fuzzer held it in every random sequence (docs/fuzz.md). A CI step will publish it (#95).
testedNot shown yet: the running app matched the model at every step that exercised it (docs/conformance.md). A CI step will publish it (#95).
seenNot shown yet: a screenshot of the app shows it. A CI step will publish it (#95).

Where it's defined

Declaration
Cairn.Optimistic.Claims.retry
Module
Cairn.Optimistic.Claims
Source
lean/Cairn/Optimistic/Claims.lean:131 at v0.5.2
Statement
Cairn.Optimistic.Claims.retry.press.post
Statement hash
7aa7a95a4e7eb0a0

Ledger

cairn^1105 is active in this version's claims.lock, statement 7aa7a95a4e7eb0a0. An id never moves or changes meaning.