What happens to every change
QuinR changes real pages on real sites. This page says exactly what it does to them, and shows what it has actually done so far.
The sequence, every time
- 1
A snapshot first
Before QuinR changes anything, it records exactly what was there. Every applied change has one — not by policy, but because the code cannot apply a change without writing it.
- 2
You approve it
Nothing reaches your site until somebody on your side says yes. QuinR writes the change and shows you the before and after.
- 3
It applies the change
Through your CMS, with an idempotency key, so a retry cannot apply the same change twice.
- 4
It fetches the page again
Not its own record of what it sent — the live page, as a visitor would get it.
- 5
It verifies what it finds
The re-fetched page has to match what was approved.
- 6
If it does not match, it rolls back
Automatically, to the snapshot, without waiting to be asked — and the same happens if the apply is interrupted before it can be checked. That is what the rolled-back number below counts.
The numbers
- Waiting for someone to approve — right now
- 0
- Approved by a person
- 0
- Applied to a live site
- 0
- Verified against the live page
- 0
- Rolled back automatically — the live page did not match
- 0
- Rejected by a person
- 0
- Could not be applied — the CMS refused the write
- 0
- Went live and needs undoing by hand — a merged pull request can only be reverted by a new one
- 0
Counted across every account, for the week beginning 2026-10-26. 0 of the applied changes were applied without asking each time, by accounts that switched that on.
Every applied change carried a before-snapshot. That is 100%, and it is true by construction rather than by good luck: the code cannot apply a change without recording what was there first.
Two things worth being clear about
Unattended changes are offered, never assumed.
After a kind of change has been approved enough times, QuinR offers to stop asking every time. Nothing switches that on but a person clicking it. Anyone with admin access can switch it off again for the whole account: from then on QuinR asks before every change. A change already being applied at that moment finishes, and is still verified and rolled back if it does not match.
Automatic rollback covers the verify window, not the distant past.
If a change fails verification, QuinR reverts it to the snapshot straight away. Once a change has verified cleanly — a minute ago or a year ago — it is not un-applied by a button. It is changed back by a new change, which is itself snapshotted, approved and verified. We would rather say that than imply an undo button exists.