From 6f2455f84a2f3f0a51c1cf728c987265ca0ebf69 Mon Sep 17 00:00:00 2001 From: iris Date: Thu, 15 Oct 2026 04:47:01 +0200 Subject: [PATCH] docs: rewrite the container load and retired limits prose in active voice for the vale error rules --- docs/agent-lifecycle/persistence.md | 2 +- docs/scheduler/coordinator.md | 2 +- docs/web-ui/dashboard.md | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/agent-lifecycle/persistence.md b/docs/agent-lifecycle/persistence.md index 7c0a3efe..1dbc2cb8 100644 --- a/docs/agent-lifecycle/persistence.md +++ b/docs/agent-lifecycle/persistence.md @@ -414,7 +414,7 @@ Contents: for them. - `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 - is ignored and can be deleted. + is harmless and you can delete it. The root agent has the meta dir RO-mounted at `/meta/`. diff --git a/docs/scheduler/coordinator.md b/docs/scheduler/coordinator.md index 74500d3e..4634269f 100644 --- a/docs/scheduler/coordinator.md +++ b/docs/scheduler/coordinator.md @@ -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 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 -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 effective `MemoryMax=` into the agent's runtime dir diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md index 29ee1cfc..f65593e5 100644 --- a/docs/web-ui/dashboard.md +++ b/docs/web-ui/dashboard.md @@ -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 live on the BU1LDS page — see below.) -Per-container CPU, memory and disk load is not shown in the hive UI. The -same figures are exported as OTEL metrics and graphed in Grafana (see +Per-container CPU, memory and disk load isn't shown in the hive UI. The +same figures go out as OTEL metrics and appear in Grafana (see [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: