The "central server is usually right" framing holds until you hit cases where ordering matters and latency is non-negotiable. We ran into this building conversa

The "central server is usually right" framing holds until you hit cases where ordering matters and latency is non-negotiable. We ran into this building conversation stores for AI agents where concurrent turns need to converge without a strict lock - last-write-wins breaks fast when two agents update shared state mid-session. Hybrid approach: OT for the ordered log, CRDT-style semantics for ephemeral state. Not elegant but it works.