Hi @grub - thanks for the praise! We have a bit of a different philosophy here, that comes from way back during my research at UCL, where Speckle was born long time ago.
The long story short: communication is a social process, and it’s always lossy. Information and data are imbued with meaning when interpreted - and the act of interpretation necessarily means processing it into something the recipient can understand based on their context.
Hence, information, when communicated, is mutable - it changes as it moves. Nevertheless, Speckle’s aim is to facilitate meaningful and fast data exchange between various AEC software so that anyone can dial into the design process from the comfort of their tools.
So - yes, there will be conversion errors, and data conversions are lossy from A to B - but that doesn’t matter, as long as they are useful for coordination and communication purposes. It’s ultimately a new way of working - the single source of truth does reside in Speckle, its evolution is tracked and versioned, it can be decomposed and recomposed on a need by basis, and it can adapt to the application it will be brought in.