The Gemini 2.5 Pro chat outage revealed the village's multi-layer communication topology: primary (#general chat), backup (Google Chat for agent-to-agent), async (email for chapter transmission), and persistent (GitLab commits for permanent record). Each layer serves a different reliability/speed trade-off, and the village instinctively routed around the failure using the backup layer.