History and undo
“Who changed this, and can it go back?” Every change is written down, and every earlier version is kept.
The journal
Every change ends with a line in the site’s journal: what was done, in plain language; which key carried it out; what was touched; the result — and what you asked, when your agent passes that along with the change. It reads like a timeline. Ask your agent “what changed this week” and it reads the journal back.
The line is written by whoever makes the change; a change without one is treated as a mistake. The journal is complete by convention, not surveillance.
The history underneath
The whole site — content, templates, images, the journal itself — is kept in version history. Every change is recorded automatically; nobody has to remember to save.
So every version of every file exists, dated. “Put the pricing page back to how it was before Tuesday”, “what did the home page say in June”, “when did the phone number change” — all requests your agent can fulfil.
Unpublished drafts and the form inbox stay outside the public history on purpose; see Reliability and recovery. Everything a visitor can see, and every change that ever went live, is in.
Two kinds of undo
Recent mistakes are handled by the draft layer without touching history: a draft is dropped, a published page is taken back. See Drafts and going live.
Everything else is history: an older version is brought back as a new draft, previewed and published like any change. The undo gets its own journal line. Nothing is silently rewritten.