From 895a00c5ebe77efce01c0ede49cb5c4646111a07 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Fri, 1 May 2026 15:49:53 +0200 Subject: [PATCH] rm irretrievable term --- standards/application/reliable-channel-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/application/reliable-channel-api.md b/standards/application/reliable-channel-api.md index f138b28..0d5fc04 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -170,7 +170,7 @@ When a segment is received from the network, the implementation MUST process it 1. **Decrypt**: If an `Encryption` implementation is provided, decrypt the segment. 2. **Apply [SDS](https://lip.logos.co/ift-ts/raw/sds.html)**: Deliver the segment to the SDS layer, which emits acknowledgements and detects gaps. - - **Detect missing dependencies and fetch from store**: If SDS detects a message in the causal history which has not yet been received , and considers the message is irretrievably lost, + - **Detect missing dependencies and fetch from store**: If SDS detects a message in the causal history which has not yet been received, and considers the message is lost, the implementation MUST attempt to retrieve the missing segment throughout store protocol (store API is never exposed and hence, store queries are handled internally). 3. **Reassemble**: Once all segments for a message have been received, reassemble and emit a `reliable:message:received` event.