How does Hantera keep a history of actor changes?
When commands change an actor, Hantera persists a checkpoint with an identifier, timestamp, and optional change metadata. Teams can use those checkpoints to inspect the actor's historical state.
A checkpoint records the state of an actor after commands are applied. Hantera can use the history up to a checkpoint to reconstruct the actor’s state at that time.
This gives operations and support teams a way to investigate what changed on an order, payment, ticket, asset, or SKU before deciding how to respond.
This actor-specific history is separate from the system-level audit log used for platform resource actions.