docs: name the swarm display name by its new path
Two sites spelled it as a brace group, services.hyperhive.{hiveName,
swarmName}, which no anchored rewrite can handle correctly now that only
one of the two moves; both are written out separately. One of them is an
MCP tool description, so it is rendered into every agent's system prompt.
This commit is contained in:
parent
30a94d35e9
commit
1a0cb0fb44
8 changed files with 17 additions and 12 deletions
|
|
@ -297,7 +297,7 @@ status_text, status_set_at, hive_name, swarm_name }`:
|
|||
or when `running = false` (see above).
|
||||
- `hive_name` / `swarm_name`: display names read from
|
||||
`HYPERHIVE_HIVE_NAME` / `HYPERHIVE_SWARM_NAME` env (sourced from
|
||||
`services.hyperhive.hiveName` / `services.hyperhive.swarmName`).
|
||||
`services.hyperhive.hiveName` / `services.hyperhive.swarm.name`).
|
||||
Both `None` when the options aren't configured.
|
||||
|
||||
### Timestamps on the wire
|
||||
|
|
|
|||
|
|
@ -121,7 +121,7 @@ Every agent's export includes these resource attributes automatically:
|
|||
| `service.name` | `hyperhive-agent` (constant) |
|
||||
| `agent` | agent logical name (e.g. `iris`) |
|
||||
| `hive` | hive display name (`services.hyperhive.hiveName`) |
|
||||
| `swarm` | swarm display name (`services.hyperhive.swarmName`, if set) |
|
||||
| `swarm` | swarm display name (`services.hyperhive.swarm.name`, if set) |
|
||||
|
||||
Additional labels can be appended via `extraResourceAttributes` (see option
|
||||
reference above); custom per-data-point labels can be passed with
|
||||
|
|
|
|||
|
|
@ -20,17 +20,19 @@ the additional config needed when the swarm spans multiple hosts.
|
|||
```nix
|
||||
services.hyperhive = {
|
||||
domain = "pr1ma.example.com"; # machine-addressable DNS domain
|
||||
hiveName = "pr1ma"; # human display name (optional)
|
||||
swarmName = "constellat1on"; # shared swarm display name (optional)
|
||||
hiveName = "pr1ma"; # human display name (optional)
|
||||
swarm.name = "constellat1on"; # shared swarm display name (optional)
|
||||
};
|
||||
```
|
||||
|
||||
`domain` is required when matrix federation is on (`matrix.enable`);
|
||||
it drives `HYPERHIVE_HIVE_DOMAIN` in every container so agents can
|
||||
form qualified labels (`iris@pr1ma.example.com`). `hiveName` and
|
||||
`swarmName` are purely display — they surface in the dashboard chrome
|
||||
`swarm.name` are purely display — they surface in the dashboard chrome
|
||||
header and per-agent system prompts. Federated hives at different
|
||||
domains can share a `swarmName`.
|
||||
domains can share a `swarm.name`; that it sits under `swarm` and
|
||||
`hiveName` does not is the whole distinction — one names this hive, the
|
||||
other names the group it belongs to.
|
||||
|
||||
See `docs/conventions.md` § Hive identity for the env-var chain
|
||||
and `qualify()` / `qualified_label()` semantics.
|
||||
|
|
|
|||
Loading…
Reference in a new issue