Tri-Agent Coordination Protocol — AAO Wave 5

**Status:** LIVE as of 2026-02-26 **Authority:** Graph Kernel (GK) at `:8001` **Replaces:** `[home-path]` (file-based, one-sided, deprecated) | Agent | Model | Strengths | Spawner | |-------|-------|-----------|---------| | **Claude Code** | Opus 4.6 | Agentic dev, architecture, multi-file refactors | `clawdbot agent` | | **Gemini CLI** | Gemini 3 Pro Preview | Research, creative, long-context (>50K tokens) | `gemini` CLI | | **Codex CLI** | GPT-5.3 Codex | Structured output, data analysis, low hallucination | `codex` binary | **Problem:** The file-based `cross_agent_handshake.json` was one-sided — Gemini wrote 3 messages, Codex acknowledged once, Claude Code never participated. The event bus (`event_bus.sock`) died after 1 test message. Two agents could grab the same task simultaneously with no conflict detection. **Solution:** All coordination now flows through the **Graph Kernel HTTP API**. The GK is already the authority layer for task tickets, dedup, attestations, and reputation. Adding agent presence + claims makes it the **single source of truth** for the entire multi-agent system. No file watching, no Unix sockets, no race conditions. | Context | URL | When to use | |---------|-----|-------------| | Local (Mac2, where GK runs) | `http://localhost:8001` | Agent running on Mac2 | | Tailscale mesh (any Mac) | `http://[ip]:8001` | Agent running on Mac1/Mac3/Mac4 | | Cloud Run (remote) | `https://graph-kernel-274020562532.us-central1.run.app` | Cloud VM or external |