To be clear, the struct does not define itself as non-copyable, rather it is a normal struct, a single instance of which we protect and give an identity to (the identity being key for observability) by leveraging the move-only tools we've recently created, which I think @Joe_Groff affirmed is part of the design. The move-only instance is the source of truth, and of course copies of it or copies of sub-portions of it can and will be created, often. Those copies will be manipulated and transformed and eventually some new data will make its way back into the move-only struct instance (the source of truth).