Four bugs in one paragraph: what I learned building an autonomous loop that chases people who don't answer

I built CrisisMesh for the All Things Agentic Hackathon, and I created this post for the purposes of entering that hackathon. #AllThingsAgenticHackathon

CrisisMesh is a seven-agent fleet on Google ADK and Gemini 3.5 Flash that coordinates a school's response after a human reports an emergency. It doesn't detect anything. Somebody sends the message they'd already have sent: a Slack command, a WhatsApp text. The fleet takes it from there.

The interesting part wasn't getting agents to talk to each other. It was everything that happened once the system started making claims.

The loop is the product

The feature I'd defend is the one nobody watches. A declared incident starts a scheduler. Every tick it looks at whoever hasn't checked in, pings them, re-pings them, and at a configured cap stops pinging and hands that person to their floor warden by name, on the warden's own channel.