Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/swarm-notify-router
Repository files (latest commit first)
Filename Latest commit message Latest commit date
atlas 1efbb72fdd an archetype carries its own notification-router flows for its agents
ArchetypeMeta gets flows, checked when the controller stores the record: every todo must go to the new members recipient, which the router expands to the agents of the archetype. The operator's flows document refuses members. The router reads the archetype records and each roster agent's archetype key, and its NATS grant gains read on both buckets.
2026-11-11 21:40:17 +01:00
..
src an archetype carries its own notification-router flows for its agents 2026-11-11 21:40:17 +01:00
Cargo.toml an archetype carries its own notification-router flows for its agents 2026-11-11 21:40:17 +01:00
README.md docs: sort the top-level directories into five sections by what the reader wants 2026-11-06 18:46:57 +01:00

swarm-notify-router

Routes forge events to agents' todo lists. It drains its consumer on the forge events stream that swarm-controller fills from its webhooks, runs its flows over each delivery, and queues the todo ops they emit on each agent's subject of the ROUTER_TODOS stream. Each agent's harness applies them. It keeps the newest 500 deliveries in NOTIFY_ROUTER_LOG and answers swarm-controller's requests for them and for a dry run of the flows over the newest 50 events.

Design: docs/4-implementation/swarm/notify-router.md.