Most data systems are built to forget.
Not deliberately. It's just the natural consequence of how databases work. When you update a customer's address, the old address is gone. When you change a product price, the previous price is gone. When a process state changes, the prior state is gone.
Each of those deletions also deletes something else: the why.
Here's a question most organisations can't answer: what was Pump 47's vibration reading before it failed?
Not a complex question. A specific measurement, at a specific point in time, for a specific piece of equipment. But in most asset management systems, if that reading was overwritten when the failure was logged, it's gone. The data archaeology required to reconstruct it — if it's possible at all — involves manual investigation across multiple systems, log files, and human memory.
The same pattern applies everywhere.