Thanks for looking it over. Imagine you are looking at a thrift spec or a protobuf file where all the data is laid out, and then ask how would you add transfor

Thanks for looking it over. Imagine you are looking at a thrift spec or a protobuf file where all the data is laid out, and then ask how would you add transformation to that spec. So, the Adama starts with laying out state and then goes hog wild on how to transform that state. As to what is persisted, the document you are outline is. At core, Adama is a key to document store except you don't have the typical operations. Instead of put or get, you can "send a message to a document" or subscribe to "your personal view of the document". The language bridges the gap in how sending messages transform the document and how privacy dictates your personal view.