Can reviewers see exactly what an agent changed in Busabase?

Great question. A Change Request is a proposed change to Busabase data, not an edit that has already been applied. An agent can submit one or several operations in a request. The current record stays as it is while the request waits for review. Approve records the review decision; merge is the step that applies the change.

There are a few ways to find the request:

1. On the Space Home page, open an item under Waiting for your review. The Recent activity section on the same page also links to recent requests.
2. Open Inbox → For review for pending requests. Use Changes requested, Merged, or Closed to find requests in those later states.
3. Open Activity for the Space-wide timeline, then select the request. If an event is older, use Load more. After a change is merged, the record's Lineage can also take you back to its request.

Inside a request, What will change lists its operations and shows each changed field's previous and proposed values. The header identifies the submitting account and, when available, the credential and channel used. The review timeline records who approved or requested changes, their note, and later revisions or merges. If multiple agents propose edits to the same record, open each request separately and compare it with the current record before merging; a newer edit can create a conflict.

A proposal sent back with Request changes does not disappear or modify the record. It remains under Changes requested, with the reviewer's reason in its timeline, until it is revised and reviewed again. This separate local example shows the saved reason:

One attribution detail: if several agents use the same credential, the request may identify that credential's owner and channel rather than uniquely naming each agent. Use distinct credentials or clear request descriptions when you need to tell their proposals apart.