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).
DeliveryTarget: Parse strings like 'telegram:12345' or 'discord:channel:thread'. Resolve to platform adapter.
DeliveryRouter: Route content to configured targets, handle truncation, silence-narration filtering.
DeliveryLedger: JetStream consumer with max-deliver=3, ack-wait configurable per target. Crash recovery via NATS redelivery (no separate SQLite ledger needed).
DeadTargetRegistry: Persistent JSON tracking of confirmed-dead targets (deleted groups, kicked bots). Self-healing on successful send.
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_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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).
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