I’m trying to understand how people handle changes to real system state. In many projects, once something writes to a DB or config, the previous state is effectively gone unless you planned for it upfront.

I haven’t personally dealt with large-scale failures here, but with more automation and AI writing state directly, it feels like reversibility matters more. Curious whether teams actively design for rollback, or mostly rely on backups and manual fixes.