Strategies for representing persisted and un-persisted remote data

So there is a lot to think about in this thread, but I thought I would respond to this at least:

My client-side UUID’s are only used for routing messages to the correct UI element. For example, if I have a list of elements, I generate a UUID for each one on page load simply by incrementing an Int, and any time a new item gets added, it gets a UUID that never changes.

The list itself is probably sorted either by some kind of implicit order, or a database column, but this is getting very off-topic from representing database records. My UUID’s are a UI implementation detail.