Who changed what, when, and what it was before — recorded for every single write, and never edited or deleted after the fact.
Every mutation — a direct write, a sealed change request merging, a rollback, a connector-sourced update — logs an event: who did it, what action, what the value was before, and what it became. That applies uniformly across scalar keys and whole config documents; there's no write path that skips the ledger.
Ledger rows are never updated or deleted. A rollback isn't a destructive revert that erases what happened — it's a new event that sets the old value again, fully visible in the history right next to the change it's undoing. The ledger only ever grows; it never rewrites its own past.
Because every write is a fully-specified event in order, the effective state of the entire org — every key, at every scope, as it actually was — can be reconstructed for any point in its history. Not an approximation stitched together from backups; the same resolution engine, replayed against the ledger up to that moment.