docs: the swarm and services pages become overviews
The controller's status, queue, AGENTS.md and forge-webhook details move to 4-implementation/swarm/controller.md. The metrics, logs and OTEL detail moves to 4-implementation/swarm/telemetry.md. Each leaves a short operator blurb with the options to touch, and links into the moved text are updated.
This commit is contained in:
parent
7df6672c87
commit
f7cdd194f7
1 changed files with 793 additions and 707 deletions
|
|
@ -169,6 +169,12 @@ Nothing of it sits in this tree.
|
|||
it?** → [`4-implementation/swarm/ci-metrics.md`](4-implementation/swarm/ci-metrics.md).
|
||||
- **How does an agent get a todo when someone assigns it an issue, and lose it
|
||||
when the issue closes?** → [`4-implementation/swarm/notify-router.md`](4-implementation/swarm/notify-router.md).
|
||||
- **How does the controller take in hive status, give agents the queue, keep an
|
||||
agent's `AGENTS.md` and register forge webhooks?** →
|
||||
[`4-implementation/swarm/controller.md`](4-implementation/swarm/controller.md).
|
||||
- **How are the metrics store, Grafana, log store and OTEL collector wired, and
|
||||
who may reach each?** →
|
||||
[`4-implementation/swarm/telemetry.md`](4-implementation/swarm/telemetry.md).
|
||||
|
||||
### Trust boundary mechanics
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue