Governed ability
Restore revision
aafm/restore-revision Guarded write
Restore a post to one of its revisions. The current state is first saved as a fresh revision, so the restore is reversible.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Restore revision ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Restore revision if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys but never the values.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Restore post 142 to revision 990.
Roll the About page back to its previous revision.
Bring post 88 back to the version from before the last edit.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Restore revision.
Do I lose the current version?
No, the current state is saved as a fresh revision first, so the restore is reversible.
Is it enabled by default?
No, it is off until enabled, requires edit access to the post, and is logged.
Governed by default, from the first call.
Restore revision is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.