This is a great idea and seems like it could be super useful. We've built something sort of like this by firing off events to Amplitude from the server side to cover state transitions by users, including the old state as a property for later inspection. But doing it automatically from the DB txlog makes a ton more sense.