Telegram and the composer deliver notifications and approval requests #1984
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#1984
Reference in new issue
Block a user
Notifications (what happened, what was done, what is needed) and approval requests go out on Telegram and the chat composer, and the answers come back as events. An answer is accepted only from a verified identity.
Done when: the same notification and approval request reach both channels, answering in either continues the run, and an answer from an unverified identity is refused.
Spec: R19, R38.
Telegram now ships as a connector extension rather than in core (archipelago 13f6c42, core
7903a0e22). The connector contract gained Deliver (messages and records, never offered to an agent) and Listen (a stream from a connection the connector holds, resumed from a stored cursor). Deliveries writes one row per channel and retries an unconfirmed one with capped backoff, so a channel that is down delays a message instead of failing the run. A tap becomes an approval.answer event from an allowed user only, and dispatch settles the request. Verified on staging: an investigation's findings reached Telegram through the connector. Still to check: an Approve tap through the new path continuing a run.