Changelog
What changed, and how it changed.
This page is the working example. It was published, then edited through a staged published-content transaction, then rolled back — and the entries below record what each of those steps actually did to this page.
2026 · Showcase build
A dedicated demo install
A disposable LocalWP site with its own database and its own MySQL instance, with the theme and both plugins symlinked from the working checkout rather than copied.
One token system
A single palette, type scale and shape language, moved with the token tools and shipped as one class-based stylesheet through the theme package importer.
Real pages
Seven pages and two posts, all published through the content tools, all navigable through a menu registered by the navigation tool.
Entries
agentshell_create_page at status publish. The write carried an atomicity block: a real SQL transaction, rolled back on failure.agentshell_edit_published: the new text went into a private shadow row, and the published original kept serving its old content until the publish step committed.agentshell_screenshot in transaction mode, so the screenshot showed the edit that had not yet gone live.agentshell_publish_edit committed the change; agentshell_publish_edit_reconcile finished the tail — shadow deleted, claim released, caches invalidated.agentshell_rollback_transaction. The published page was unchanged afterwards, and the transaction row was released with a guarded delete.Two different rollbacks. Rolling back a configuration transaction discards a buffer — nothing was ever written. Rolling back a content operation has to delete something that was written, which is why it needs a durable journal, verified evidence and an authority check at the moment of deletion.
Verify it yourself
The audit trail remembers.
Every configuration mutation is recorded with its actor, operation and affected tokens; every content journal entry is recorded with its operation id and state. Ask the site what happened, and it will tell you.