If you need to change history you can just create new events that accomplish your mutation -- and even mark them as a type 'change history' or some such obvious identifier so when you inspect the event stream you know exactly what you are looking at.

I agree, this is 100% normal in accounting, as the earlier thread pointed out. If there is an error you add journal entries to the end to make the adjustment. It is funny that this sort of thing was invented in accounting in 1494.

> If you need to change history you can just create new events that accomplish your mutation -- and even mark them as a type 'change history' or some such obvious identifier so when you inspect the event stream you know exactly what you are looking at.

"Right to be forgotten" isn't the same as "right to be redacted".

To avoid having to implement the whole logic for any event you'd want to revert, you can have a "cancel" event that points to another event.

You'd read the cancel events first and simply skip the events they point to.

In many cases they are legal proof that something happened. If you can mess with history, proof can't be used in court.