Delivery system: router, ledger, dead targets, wake #772

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

Outbound message delivery infrastructure built on NATS JetStream (already provides guaranteed delivery, dead-letter queues, ack/nak, dedup — no need for a separate actor engine like Hollywood).

  1. DeliveryTarget: Parse strings like 'telegram:12345' or 'discord:channel:thread'. Resolve to platform adapter.
  2. DeliveryRouter: Route content to configured targets, handle truncation, silence-narration filtering.
  3. DeliveryLedger: JetStream consumer with max-deliver=3, ack-wait configurable per target. Crash recovery via NATS redelivery (no separate SQLite ledger needed).
  4. DeadTargetRegistry: Persistent JSON tracking of confirmed-dead targets (deleted groups, kicked bots). Self-healing on successful send.
  5. Wake delivery: Use NATS request/reply for async delivery to push-capable adapters.

Acceptance Criteria

A cron job can schedule a message for delivery. If the target is unreachable, the ledger retries. If the bot is kicked from a group, the target is registered dead and skipped.

Notes

Delivery goes through a Deliver RPC on a Messaging Service gRPC contract (proto/messaging/v1), registered in servicespec. Not NATS fan-out. The daemon treats an unreachable Messaging Service as unhealthy and retries; it never fails the schedule. mqti.4's chat courier (crondelivery.NewChatCourier) is the first consumer.


Imported from beads archie-core-1786637496264-247-25b84f1a · GitHub #268 · type feature · priority P2 · created 2026-08-08

Outbound message delivery infrastructure built on NATS JetStream (already provides guaranteed delivery, dead-letter queues, ack/nak, dedup — no need for a separate actor engine like Hollywood). 1. **DeliveryTarget**: Parse strings like 'telegram:12345' or 'discord:channel:thread'. Resolve to platform adapter. 2. **DeliveryRouter**: Route content to configured targets, handle truncation, silence-narration filtering. 3. **DeliveryLedger**: JetStream consumer with max-deliver=3, ack-wait configurable per target. Crash recovery via NATS redelivery (no separate SQLite ledger needed). 4. **DeadTargetRegistry**: Persistent JSON tracking of confirmed-dead targets (deleted groups, kicked bots). Self-healing on successful send. 5. **Wake delivery**: Use NATS request/reply for async delivery to push-capable adapters. ### Acceptance Criteria A cron job can schedule a message for delivery. If the target is unreachable, the ledger retries. If the bot is kicked from a group, the target is registered dead and skipped. ### Notes Delivery goes through a Deliver RPC on a Messaging Service gRPC contract (proto/messaging/v1), registered in servicespec. Not NATS fan-out. The daemon treats an unreachable Messaging Service as unhealthy and retries; it never fails the schedule. mqti.4's chat courier (crondelivery.NewChatCourier) is the first consumer. --- _Imported from beads `archie-core-1786637496264-247-25b84f1a` · GitHub #268 · type feature · priority P2 · created 2026-08-08_
sam added the mediumfeature labels 2026-10-27 13:37:41 +00:00
sam self-assigned this 2026-10-27 13:37:41 +00:00
sam added the deferred label 2026-11-15 17:26:23 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#772