The first collaboration model in CodeVerse was convincing in exactly the way a local demo needs to be convincing.
Open two tabs. Join the same room. Type in one editor. Watch the other editor update.
Then ask one unpleasant question: what happens when those two sockets land on different server instances?
The answer was that the room stopped being a room. Each process had its own memory, its own presence list, and its own idea of the current files. A restart erased state. A reconnect could create a second identity. A load balancer could turn a working demo into two isolated conversations.
This article is about the work that followed: moving CodeVerse from synchronized tabs to a collaboration path I could test across processes, recover after disconnects, and describe without pretending a local benchmark was a production capacity claim.
