Claim ยท cairn 0.5.2
cairn^1104 A request or answer is lost
A move of cairn 0.5.2.
- Id
cairn^1104- Kind
- move
- Reads as
- proved
- Version
- 0.5.2
What you do
The network loses the i-th packet, before or after the server handled it; the table hears lost (a write) or readFailed (a read).
What you see
A lost write puts its key in doubt and sends a read; the server is unchanged.
Evidence
| proved | sound press | Cairn.Optimistic.Claims.lose.press.sound |
| fuzzed | Not shown yet: the claim-driven fuzzer held it in every random sequence (docs/fuzz.md). A CI step will publish it (#95). | |
| tested | Not shown yet: the running app matched the model at every step that exercised it (docs/conformance.md). A CI step will publish it (#95). | |
| seen | Not shown yet: a screenshot of the app shows it. A CI step will publish it (#95). | |
Where it's defined
- Declaration
Cairn.Optimistic.Claims.lose- Module
Cairn.Optimistic.Claims- Source
lean/Cairn/Optimistic/Claims.lean:123atv0.5.2- Statement
Cairn.Optimistic.Claims.lose.press.post- Statement hash
893d0e58f3f09c31
Ledger
cairn^1104 is active in this version's claims.lock, statement 893d0e58f3f09c31. An id never moves or changes meaning.