“memory benchmarks all test one agent recalling one history. nobody benchmarks what i hit daily: three agents coding in parallel against one shared memory file, clobbering each other's decisions. the recall problem is solved-ish. the merge problem isn't even named.”

Shared memory is itself mutable state, so it needs the same treatment as source files: ownership, merge rules, conflict detection. Worktrees isolate code but agents still converge on one notes file, decisions log or memory store. Low-engagement single post, but it names a gap: decision rationale has no merge semantics. Pairs with Stodal (single writer) and Dotu (claims log) below.