agent-synclisted

# agent-sync — one project, many agents, no collisions Two planes, and one rule between them: > **Git is the record plane. The cloud is the coordination plane.** > A fact that must survive is written to git first and referenced from the cloud. > A fact about *who is doing what right now* lives in the cloud and expires. No cloud object is ever the only home of a durable fact. Everything below exists to keep that true while several agents write at once. ## Four traps — read these before anything else **1. The knowledge base never decides a lease.** It cannot: twelve concurrent appends to one Outline document returned twelve successes and left **three** lines. Exclusion comes from something with real compare-and-swap. The plane carries the record and nothing else. Full measurements in `references/lease-protocol.md`. **2. Know which lease you have, and say so.** `leaseBackend: "local"` is an atomic file create — exclusive between processes on one filesystem, **advisory across machines**. `leaseBackend: "git"` pushes a ref, and the remote's non-fast-forward rejection **is** a compare-and-swap — exclusive across machines. `acquire` prints which. A pretended lease is worse than no lease: the other agent stops checking. **`acquire` also writes the claim through to the roadmap**, and `release` restores exactly what was there — one row, one cell, refused on ambiguity, `git diff` empty after a round-trip. **Read `references/roadmap.md`** before configuring `claimTags` or closing