yes, it would mean having two different event stores too, forking from the abstraction, that branches according to purpose...

i think that for this there needs to be some kind of chain of association or top level id, like, the first version ID should be a tag that all versions share...

i've talked about this idea and it's penciled into my ACL administrative events code that i haven't finished yet, a "blockchain" back-reference "replaces" is the tag i've suggested, i think it has many uses throughout, and especially for all kinds of replaceables - parameterised replaceables would be faster to associate if they had these as well since they are multiple