Watch
0
0
Fork
You've already forked hyperhive
0

docs: the swarm decides who is on the roster, so that text moves to the swarm page

The agent roster page opened with how an agent comes to exist (the identity
store, swarmctl, the swarm UI, the ruth archetype), which is the swarm's
doing. That text now sits in a "Who is on the roster" section of the swarm
page, and the roster page keeps what is a hive's and an agent's: the hive's
own list, who may reach whose state, and that the manager is a normal agent.
This commit is contained in:
iris 2026-11-11 22:50:32 +01:00 • committed by mara
commit 757e6fc1a7

View file

@ -100,6 +100,22 @@ socket-directory constraint that governs where `socketPath` may point:
The options, wire formats and failure modes of each:
[`controller.md`](../../4-implementation/swarm/controller.md).
### Who is on the roster
The swarm decides. An agent exists in the swarm if and only if it has an
identity in the swarm's authelia identity store, which `swarmctl agent create`
or the swarm UI writes once. `GET /api/agents` on the swarm controller lists
them. A hive creates nothing at boot, so every agent, the manager `ruth`
included, comes from the swarm UI or `swarmctl agent create`, and destroying
one is as final for her as for any other.
The swarm UI's setup assistant creates `ruth` from the
[`ruth` archetype](archetypes.md#the-built-in-archetypes), which grants her
`manage_root_agent` and sets her model to `sonnet`. A ruth created before the
archetype keeps her model; set `sonnet` in her inference settings in the swarm UI
if you want it. What that grant lets an agent reach on a hive is on the
[agent roster page](../agents/agent-roster.md).
## Hives: the substrate
- **hive** — one host running `hive-c0re` and its agent containers