Does an update on lifecycle stages of a record, cause a version change?
From @rajk
I presume we agree to follow the immutable pattern in which case any changes requires a new version of the entity to be created rather than an update in place. I am curious how this works in combination with some of the enums that indicate created/curating/curated or loading/received/accepted etc., which seem to indicate the lifecycle status of the entity – Will each update cause a new instance with updated status attribute?