diff --git a/nix/host-modules/swarm-grafana/dashboards/forge.json b/nix/host-modules/swarm-grafana/dashboards/forge.json
index 524a21f4..acb08a2e 100644
--- a/nix/host-modules/swarm-grafana/dashboards/forge.json
+++ b/nix/host-modules/swarm-grafana/dashboards/forge.json
@@ -81,7 +81,7 @@
       "id": 3,
       "type": "stat",
       "title": "Organizations",
-      "description": "Orgs, which is how the forge separates agent-owned repos from the shared ones. Near-constant by design; a change here is a structural decision someone made, not activity.",
+      "description": "Orgs — the forge's coarsest grouping, and on a hyperhive forge the line between agent-owned repos and everything else. A change is a structural decision someone made rather than activity; how often that happens is a fact about this hive's projects, not something the panel can assume.",
       "datasource": { "type": "prometheus", "uid": "@datasourceUid@" },
       "gridPos": { "h": 4, "w": 4, "x": 8, "y": 0 },
       "targets": [
@@ -180,7 +180,7 @@
       "id": 6,
       "type": "stat",
       "title": "Releases",
-      "description": "Tagged releases. Expected to sit at zero on a hive that ships from main — a non-zero value here means someone started cutting them, which is a change worth noticing.",
+      "description": "Tagged releases across every repo. Cumulative, so it only rises; the rate is the signal, not the level. Whether zero is normal here depends entirely on how this hive's projects ship — a board shipped to every hive cannot know that, so read a CHANGE rather than a value.",
       "datasource": { "type": "prometheus", "uid": "@datasourceUid@" },
       "gridPos": { "h": 4, "w": 4, "x": 20, "y": 0 },
       "targets": [
@@ -213,7 +213,7 @@
       "id": 10,
       "type": "timeseries",
       "title": "Issues: open vs closed",
-      "description": "The two together, because either alone misleads. Open flat while closed climbs is a backlog being worked down; both climbing together is a backlog growing while work happens. A vertical step in closed is usually a bulk triage, not a productive afternoon.",
+      "description": "The two together, because either alone misleads. Open flat while closed climbs is a backlog being worked down; both climbing together is a backlog growing while work happens. ⚠️ A vertical step in closed is a batch operation of some kind — a bulk close, an import, a repo removal — and is not distinguishable here from a burst of real work; the issue list is what tells them apart.",
       "datasource": { "type": "prometheus", "uid": "@datasourceUid@" },
       "gridPos": { "h": 8, "w": 12, "x": 0, "y": 4 },
       "targets": [
@@ -339,7 +339,7 @@
       "id": 21,
       "type": "timeseries",
       "title": "Automation surface",
-      "description": "Webhooks and their queued delivery tasks. Worth a glance when something that should have triggered did not: a hooktask count that climbs and never settles is deliveries backing up, and every hive registering the same webhook has bitten this forge before.",
+      "description": "Webhooks and their queued delivery tasks. Worth a glance when something that should have triggered did not: a hooktask count that climbs and never settles is deliveries backing up rather than being consumed. The webhook count itself is whatever this hive has wired — it says nothing on its own, and a jump in it is someone's integration change.",
       "datasource": { "type": "prometheus", "uid": "@datasourceUid@" },
       "gridPos": { "h": 7, "w": 12, "x": 12, "y": 12 },
       "targets": [