I don't think "deterministic" is the right word here. The problem you describe can happen in a 100% deterministic scenario (i. e. no randomness or concurrency problems), it's just that the data model evolves in a way that can't be back-traced to an original important state. Maybe you could change the name of this point to "Avoid losing history in critical areas of the data model". Alternatively, since you already cover logging tables in another point, you could just call this point "immutability".