From 723e5f8cce7dbac42442f919d6a68642a3c07c38 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 9 Oct 2026 12:30:45 +0200 Subject: [PATCH] telegram: say the desktop client's gap is a known one the router does not enforce (hq issue 344) --- modules/telegram/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/modules/telegram/README.md b/modules/telegram/README.md index 2df1db71..20846196 100644 --- a/modules/telegram/README.md +++ b/modules/telegram/README.md @@ -46,7 +46,10 @@ watcher's. shows; a tap on one whose words differ — changed by another holder of the token — or on one it never showed is refused on the phone and never said to the router. -## Where an approval from Telegram means something (the operator's direction of 2026-10-09) +## Where an approval from Telegram means something (a known gap, accepted by the operator on 2026-10-09) + +The router does not measure or enforce what follows, and does not hold approvals back for it: the operator +accepted the gap for now, and novox/hq issue 344 records it with what closes it. An approval from Telegram proves only that the linked account tapped. It is meaningful where nothing working for the operator can tap in their name, which on a machine where agents run needs all three of: