| Filename | Latest commit message | Latest commit date |
|---|---|---|
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. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
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.