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 68c24643f6 archetype flows behave like the built-ins: switch off per archetype or per agent, board cards, duplicate
The document's disabled list takes archetype:<archetype>/<flow> (off for every member) and the same with @<agent> (off for one member); a key naming nothing is ignored. GET /api/notify/flows lists the archetype flows with their members, the board draws a card for each with a switch, a checkbox per agent and duplicate, and the dry run counts their hits. The flows keep following the archetype.
2026-11-11 21:40:17 +01:00
..
src archetype flows behave like the built-ins: switch off per archetype or per agent, board cards, duplicate 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.