feat(gateway): durable message deduplication via upstream IDs #612

Closed
opened 2026-10-27 13:37:02 +00:00 by sam · 0 comments
Owner

gateway.Message carries no upstream/channel-native message ID, so a re-delivered Telegram update appends a duplicate turn. Add Message.ID and derive the NellDB document ID from it (time-prefixed to preserve the ScanSince ID tie-break), making redelivery an idempotent LWW upsert.


Imported from beads archie-core-1786637492005-85-03c595e7 · GitHub #106 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08

gateway.Message carries no upstream/channel-native message ID, so a re-delivered Telegram update appends a duplicate turn. Add Message.ID and derive the NellDB document ID from it (time-prefixed to preserve the ScanSince ID tie-break), making redelivery an idempotent LWW upsert. --- _Imported from beads `archie-core-1786637492005-85-03c595e7` · GitHub #106 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumtask labels 2026-10-27 13:37:02 +00:00
sam self-assigned this 2026-10-27 13:37:02 +00:00
sam closed this issue 2026-10-27 13:37:02 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#612