I'm assuming - and this could be a bad assumption - but based on the continuing updates architecture, if client a changes model a, client b will see an update on model a. How does client b get notified of the change? Does it have some kind of fallback system ala socket.io? Is this not yet part of the project?
Judging by the chart on the site, it looks like each client polls the original model on the server, and infers changes by diffing it against the client's current copy.