From dfa582c8350ae5e36c6c8488b52c3e67b426d1b8 Mon Sep 17 00:00:00 2001
From: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com>
Date: Wed, 28 May 2025 10:50:41 +0100
Subject: [PATCH] docs: added S

---
 draft-roadmap/introduce_e2e_reliability_in_status.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/draft-roadmap/introduce_e2e_reliability_in_status.md b/draft-roadmap/introduce_e2e_reliability_in_status.md
index 01d7cef..f30722b 100644
--- a/draft-roadmap/introduce_e2e_reliability_in_status.md
+++ b/draft-roadmap/introduce_e2e_reliability_in_status.md
@@ -34,6 +34,8 @@ as well as in the browser for PoC Web Apps such as Qaku and Logos Forum.
 - P1. When sending a message in a group, the publisher can ensure the message was received by at least one recipient within `S` seconds **(Vac-DST)**
 - P2. When receiving messages in a group, the receiver can detect 90% of missed messages within `3*S` seconds
 
+For S1. Applied to Communities channels on Status Desktop
+
 **Checklist**:
 - [ ] Specs: link to specs
 - [ ] Code: link to GitHub issues/PRs/Epic
@@ -52,6 +54,8 @@ as well as in the browser for PoC Web Apps such as Qaku and Logos Forum.
 - U3. When being part of a large group, the application is able to retrieve missed messages
 - P3. When receiving messages in group, the receiver can reach eventual consistency within `6*S` seconds **(Vac-DST)**
 
+For S1. Applied to Communities channels on Status Desktop
+
 **Checklist**:
 - [ ] Specs: link to specs
 - [ ] Code: link to GitHub issues/PRs/Epic