A staff member who needs yesterday’s paragraph should not automatically restore yesterday’s database. Agree which document and revision are being recovered and what must remain unchanged. A scoped content comparison can preserve newer enquiries, settings and unrelated pages while the approved text is recovered in a test environment.
Who should use this acceptance brief
Content teams commissioning recovery and approval workflows. Use this as a scoped website handover task. Where real system evidence is required, teaching examples are not a substitute.
Source-bound platform fact
WordPress revisions provide stored versions of supported content fields and comparison/restoration features. They are not a full-site backup of every file, setting or plugin table. WordPress: revisions · Checked 16 October 2026.
Filled teaching example
Synthetic example, not a client case. Finite inputs, expected decisions and counterexamples follow; no live integration is claimed.
On narrow screens, scroll to read the complete table.
| Input / case | Check basis | Expected decision |
|---|---|---|
| post42 revision7 → post42 | same document | candidate restore |
| post42 revision7 → post99 | wrong document | reject |
| revision missing | no retained source | unknown |
Run the acceptance exercise
- Identify the exact post/page and retained revision, with owner approval for the proposed change.
- Preview the field-level diff and list excluded media, settings and plugin data.
- In a sandbox, restore only the authorised scope and compare unaffected records.
Interpret the result and retain evidence
The checker verifies document identity for a supplied revision. It cannot prove the revision exists in a real installation or that every required field is versioned. Keep the approval, compared fields and before/after evidence together; a successful generic backup drill cannot substitute for this per-document decision.
Limits before implementation
No legacy page restoration is authorised here. No changes to live content, backups or retention settings.
Replay the finite example
Save both files in one folder and run with Node22.13 or newer. The example sends no network requests and changes no account or site. Filled inputs and expected outputs · Inspectable functions
node decision-check.mjs cms-revision-restore-scope.jsonIf the requirement is recovery of the whole service rather than one document, use the backup and restore drill scenario to define that separate scope. A content revision is not a substitute for restoring files, configuration and the enquiry journey.