vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

docs: rewrite the container load and retired limits prose in active voice for the vale error rules

Browse source
This commit is contained in:
iris 2026-10-15 04:47:01 +02:00 • committed by mara
commit 6f2455f84a
3 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/agent-lifecycle/persistence.md
View file

@ -414,7 +414,7 @@ Contents:
for them. for them.
- `resource-limits.json` — retired. Per-agent overrides set on the hive used - `resource-limits.json` — retired. Per-agent overrides set on the hive used
to live here; nothing reads or writes it now. An old copy in the meta repo to live here; nothing reads or writes it now. An old copy in the meta repo
is ignored and can be deleted. is harmless and you can delete it.
The root agent has the meta dir RO-mounted at `/meta/`. The root agent has the meta dir RO-mounted at `/meta/`.

2
docs/scheduler/coordinator.md
View file

@ -460,7 +460,7 @@ The answer per agent and per field is, first match wins:
A swarm cap replaces the hive's answer, so a hive can't raise an agent A swarm cap replaces the hive's answer, so a hive can't raise an agent
above it. Like the rest of the drop-in, a changed swarm cap reaches a above it. Like the rest of the drop-in, a changed swarm cap reaches a
running agent at its next spawn or rebuild. A hive has no way to set a cap running agent at its next spawn or rebuild. A hive has no way to set a cap
for one agent: caps are set per agent in the swarm UI. for one agent: you set caps per agent in the swarm UI.
The container can't read its own cap, so `write_dropins` also writes the The container can't read its own cap, so `write_dropins` also writes the
effective `MemoryMax=` into the agent's runtime dir effective `MemoryMax=` into the agent's runtime dir

6
docs/web-ui/dashboard.md
View file

@ -81,10 +81,10 @@ and `tool_groups_changed` (the latter two re-render the stale-perms
sub-section when permission data changes). (Rebuild queue and meta inputs sub-section when permission data changes). (Rebuild queue and meta inputs
live on the BU1LDS page — see below.) live on the BU1LDS page — see below.)
Per-container CPU, memory and disk load is not shown in the hive UI. The Per-container CPU, memory and disk load isn't shown in the hive UI. The
same figures are exported as OTEL metrics and graphed in Grafana (see same figures go out as OTEL metrics and appear in Grafana (see
[observability](../scheduler/observability.md)). An agent's CPU and memory [observability](../scheduler/observability.md)). An agent's CPU and memory
caps are set per agent in the swarm UI. caps live per agent in the swarm UI.
**K3PT ST4T3** — two sub-sections on one pane: **K3PT ST4T3** — two sub-sections on one pane: