5c91d405a08e9e232d9da46535f5664287ba35b1
Notification is a contract in internal/domain/messaging, not a channel type. A channel implementation satisfies it by importing its own parent, which it already does, so channels.Channel gains no notification method and no import and the dependency stays channels -> messaging. A notification has no lifecycle, no inbound direction and no config schema, so modelling it as a channel would force Start/Stop/ConfigSchema onto something with no meaning for them. Destinations are configured, never named by a playbook: [notify] grows from one webhook URL into named destinations, each binding a name to a channel already registered in the Messaging composition plus that channel's address. An action names a destination. Playbook triggers are reachable from a public intake surface, so an action that could address an arbitrary chat would be a new exfiltration surface. Host access needs no new process surface. archie-messaging dials out only and deliberately has no NATS connection, so nothing can push to it today. Delivery travels the Gateway connection every process already holds, as a new server-streaming RPC on ChatService; the per-turn Stream RPC is not reused. The 2026-09-03 section presenting two options is superseded. Its claim that no send capability exists anywhere was too strong: telegram.SendPendingReport already sends unsolicited to a stored chat id, with no interface for it. Closes archie-core-t2db.19
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%