Cool stuff!<p>What do you suggest is the sweet spot for document size and "hotness"? Your cookbook [0] says "We suspect that an Automerge document is best suited to being a unit of collaboration between two people or a small group." Does that mean tens of kilobytes? Hundreds? More? And how much concurrent contention is viable? And is the "atom of contention" the document as a whole, or do you have any plans for merging of sub-parts?<p>Also, do you have support for juggling multiple transports, either concurrently or back-to-back? In particular, I'm thinking about synchronizing via the cloud when connected, and falling back to peer-to-peer when offline. In that peer-to-peer case, how many peers can I have, and can my peer network behave as a mesh, or must it stick together to some degree?<p>And finally, it looks like your tutorial [1] doesn't actually exist! You refer to it in a blog post [2], but it's a dead link.<p>[0] <a href="https://automerge.org/docs/cookbook/modeling-data/" rel="nofollow noreferrer">https://automerge.org/docs/cookbook/modeling-data/</a><p>[1] <a href="https://automerge.org/docs/tutorial/introduction/" rel="nofollow noreferrer">https://automerge.org/docs/tutorial/introduction/</a><p>[2] <a href="https://automerge.org/blog/automerge-2/" rel="nofollow noreferrer">https://automerge.org/blog/automerge-2/</a>