A record of what happened.
And a way back.

A change set moves through draft, captured, pending approval, approved and applied, with separate rollback statuses after that. At each stage you can see what it contains rather than inferring from a log line.

Rollback is not a single irreversible button. You can preview the reverse order and any conflicts without touching the site, and verify current resources against the checksums recorded at capture time.

If a resource changed after its post-image was recorded, rolling back would destroy that newer work. Talos refuses those resources instead of overwriting them, and tells you which ones drifted.

A changes shelf in the chat panel lists restore points from the current session, so reversing something is a two-click operation in the same place you made it.