Review what your AI proposes
Where your AI's edits wait, how you approve or reject them, and what the record keeps.
Rindo keeps two kinds of change apart. Some land the moment they are made and go on the record; some wait as a draft until a person approves them. This page says which is which, where a draft shows up, and what happens when you approve, reject, or come back later.
What waits and what does not
Edits your AI makes to existing content — a task’s description, a page’s body, a test case’s steps, a translation — wait as pending drafts with a diff against the current version, when:
- they come from a project agent run by a runner — always, by design; or
- they come over MCP from your own assistant, and the project switch Settings → General → Agent writes (“Content writes via MCP require approval”) is on. It is off by default.
A translation sent over MCP always waits as a draft, whatever the switch says.
New tasks, new pages and comments land directly on every channel, and so do status changes, titles and field edits. All of them are on the audit trail. A task a project agent files without a status lands in Triage — a project setting, on by default, when the workflow has a triage status — so new work from an agent is sorted by a person first. Your own assistant files tasks as you, and they land where yours do.
Where a draft shows up
- On the page itself. The task or page shows a one-line Pending revision … awaiting review banner naming its author — the agent, or you, for a draft your own assistant made. The current version stays current until someone approves.
- In History. Open History on the task or page to read the proposed text and its diff against the current revision.
- In the list. A task or test case with a pending draft carries a violet dot in its list row and on its board card.
- In your Inbox. Watch a task — commenting on a page watches it too — and a pending draft on it notifies you; the person who registered a project agent is notified of that agent’s drafts without watching.
Approve or reject
- Approve makes the draft the current revision. It keeps the revision number it was submitted under, and the audit trail records who approved it.
- Reject leaves the current revision as it is. The rejected draft stays in the page’s history, marked rejected, so nothing is lost and nothing is rewritten. A reject sent over MCP can carry a note, which History shows beside the rejected draft.
Approving takes the same permission as editing the content: Member or above, and an Admin for the project’s guidance. A project agent can never approve — it only proposes. Your own assistant, acting as you over MCP with a write grant, can approve what it submitted: the switch above binds the channel, not the actor.
When the page moved underneath
Every edit, by a person or an agent, is made against a known base revision. If the page changed after a draft was submitted, approval is blocked (Blocked — base rN is no longer current) and the author resubmits against the new current version. A newer human edit is never silently discarded. The same rule meets an agent at write time: an edit built on an old version is refused with the latest content, and the agent merges and tries again.
History and revert
Every page keeps its full revision history: open History to see each revision, who made it, through which channel, and the diff between any two. Revert creates a new revision carrying the old content exactly. While the page exists, no revision is ever rewritten or removed — approved, rejected and reverted all stay in the chain.
The audit trail
Every write — by a person in the app, by an assistant over MCP, by a project agent on a runner — lands on the project’s Audit page with who did it, when, and through which channel. Approvals and rejections are entries like any other. Any project member can read it, Viewers included. Entries are never edited; old ones leave only under a retention period the operator sets.
Review passes
Ask your AI to review a page and it comes back as a review pass: its findings as comments, closed with a summary, one severity, a confidence and a category for the pass as a whole. A rewrite it proposes arrives as a draft you can diff and approve like any other. The project’s review passes are listed under Reviews.