Checkpoint commit with some unfinished code, specifically in how to properly determine if there was a change worthy of pushing out to external data store. Trying to make it so that when calling ISavable.Save we pass along a copy of the new item, original item and a list of changed fields allowing for some discovery within the custom Save methods to determine if a save is truly warranted. Also included in this is an unwired saveUI processor, an option I was evaluating but didn't get as far as I'd like. There is a new IEntity data template added to TDS with some helper code to determine if an item is of IEntity, used by the custom save logic to find items warranting possible saving.