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
iris 6739bb903d docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook,
4-implementation or 5-project; the options reference (section 3) comes from
the website and has no directory here. trust-boundary stays whole under the
handbook for now. web-ui, swarm and tools split between handbook and
implementation, and the command-line references move to
2-handbook/reference. Links, path references in code and nix, and the docs
index follow the moves; no page content changes.
2026-11-06 18:46:57 +01:00
..
src metrics tests: compare labels sorted, the SDK keeps attributes in no fixed order 2026-11-05 01:31:23 +01:00
Cargo.toml swarm-notify-router: export event, todo, review request and consumer metrics 2026-11-05 01:31:23 +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.