memtrace-fleet-first

# Fleet First The coordination layer for **fleets of coding agents** working the same repo at the same time. It stops agents from silently clobbering each other's edits, and turns unsafe overlaps into a clear decision instead of a merge-time surprise. ## The Iron Law ``` IN A FLEET → FLEET TOOLS BEFORE EDITS. NO EXCEPTIONS. 1. fleet_publish_intent (declare what you'll touch; get blast radius + conflicts) 2. edit (your normal edit loop) 3. fleet_record_episode (classify A/B/C; if C, the loop resolves it) ``` A typed intent serializes to ~20 tokens; a prose "I'm going to change X" averages 200+. A 10-agent fleet × 100 edits = tens of thousands of tokens saved per fleet-turn — and zero silent overwrites — when the protocol is followed. ## A fleet = agents on ONE branch (always pass it) **Coordination is branch-scoped.** Two agents only coordinate when they're on the **same `(repo, branch)`**. The branch name is the fleet identifier: a *session branch* is how a group of agents opts into one coordinating fleet. - Working a session branch (`session/auth-revamp`)? Pass `branch` on **every** fleet call. Your fleet coordinates together and stays isolated from agents on other branches. - Omit `branch` only for the shared default pool (single, unnamed fleet). - Agents on **different** branches never conflict — git already isolates them, and whether branches merge isn't guaranteed, so the fleet never reasons across them. ```jsonc { "repo_id": "my...