Execution and the Change Ledger

Execution lists every change of the workspace, from proposed to verified, as a list or a timeline. A new change is first prepared and checked by policy. Filter it by status, site, path or assignee, and save a view for yourself or for the workspace. At the top, Connections shows each site’s write connection and anything that blocks work.

A change that waits always says why, such as Waiting for the publish window, Paused by the kill switch or Waiting for the connection, never only Scheduled.

Open a change for its Change Detail. Proposed Changes lists each field it will write. Preview and Diff shows the before, read live from the page, beside the after, with the search snippet at desktop and phone widths. Policy Status and Approval Requirements say which rules matched and who must approve.

If you are on its chain, vote to approve, reject it with a reason, or ask a question. Edit saves a new version: every vote on the earlier version is void, and the policy checks the new one. Once it is approved, a member who may execute chooses Start, and the policy is checked again just before it writes.

1. 1It reads each field live and compares it with the before that was approved.
2. 2If the page changed since, it stops and shows a three-way diff, so a person chooses which version to keep.
3. 3It applies the change, then reads the page back to check every field.
4. 4It writes the before and after to the Change Ledger, and the change moves to Verifying.

If a step fails, the run ends with nothing left applied, and the change says what to do next.

WordPress: install and activate the QueryRev plugin on the site, then open Integrations, choose Changes to your sites and Connect WordPress. Enter the site’s WordPress address, copy the connection code, and paste it in WordPress under Settings, then QueryRev. The plugin acts as its own WordPress user that may edit titles, descriptions, canonical and robots tags, content sections and internal links of posts, pages and products, create drafts, unpublish a page and add 301 redirects. It never installs plugins or changes themes, users or settings.

Human task: when no connection can make a change, QueryRev gives a person a task with the exact values to enter. When you have made it, choose Mark done; QueryRev then reads the live page and checks every field, the same as after an automatic run.

Only a Founder or an SEO Manager connects or disconnects a site. Disconnecting stops writes at once; approved changes wait until the site is connected again.

Roll back, on Change Detail, reads the page live, writes back the values from before, and records the rollback in the ledger. A rollback needs a person who may approve; it never runs by itself. Measuring the change stops when it is rolled back. A rollback of a human task is a new task with the before values.

Changes is the Change Ledger: what QueryRev and your team changed on your sites, before and after, in order. Each entry says who wrote it, AI, a person or both, who approved it, what it was expected to add, and its outcome now.

Show it as a timeline or a table, filter it by site, author, period or page path, and export the entries shown as a CSV file. Entries are only ever added: none is edited or removed afterwards.