WolfSuite Workspace · Documentation
Proposals and approval
An agent's change waits as a proposal until a person decides. Approving it saves a new revision; rejecting it changes nothing. An agent cannot approve a proposal, including its own. 1 2 3 4
An agent proposes
An agent calls doc_edit with mode: "propose". The proposal holds the operations for a person, and the document does not change. 1
Proposing the same change again returns the proposal that is already open and opens no second one. 5
An agent can also save directly with mode: "commit". The change is applied at once and the reply names the new revision and the log entry. 6
A person reviews
A person sees Inspect Diff, Approve and Reject on each open proposal. These controls do not appear on closed proposals. 7
In the review panel, Approve is available once every change is approved, and Reject once every change is rejected. 8
The review panel can download the decision as <file name>.review-decision.json. 9
Approve or reject
- Approve saves the proposal's changes as the next revision under the proposal's id. 10
- Reject closes the proposal and saves nothing. 3
- When two people approve at the same moment, one approval saves the change and the other finds the proposal already closed. 11
- An agent that tries to approve or reject any proposal, its own or a person's, is refused with
FORBIDDENand nothing changes. 4 12
After approval the agent reads the saved result and can reply in the comment thread and resolve it. 13 2
The document history names who approved each revision and which proposal it came from. 14 15
On the managed deployment, in a check recorded on November 14, 2026, an agent proposed an edit, a person approved it, and the service saved revision 1 recording the approver. 16
Proposals that fall behind
| State | When | Evidence |
|---|---|---|
superseded | Another change was saved after the proposal was made, and the proposal can still apply. It is out of date, not broken. | 17 |
conflicted | Another saved change makes the proposal impossible to apply. | 18 19 |
An agent that edits from an older revision gets REVISION_MISMATCH with the current revision, so it can read again and propose afresh. 20
Evidence
Each numbered reference above points to the test that exercises the statement or to a recorded observation of the hosted service at workspace.wolfsdk.com. Test paths are relative to the WolfSuite repository.
- Test
sdk/web/packages/mcp/test/tools.test.ts: “propose holds the ops for a person and changes nothing” - Test
sdk/web/packages/mcp/test/workflow.test.ts: “the agent proposes, the person approves, the agent reads the result and settles the thread” - Test
sdk/web/packages/server/test/rooms.test.ts: “reject closes the proposal and commits nothing” - Test
sdk/web/packages/server/test/ws.test.ts: “an agent that sends proposal.decide gets FORBIDDEN, for its own proposal and for a user's; nothing changes for anyone” - Test
sdk/web/packages/mcp/test/tools.test.ts: “a repeated propose answers with the proposal already open, says existed, and opens nothing” - Test
sdk/web/packages/mcp/test/tools.test.ts: “commit applies the ops at once and reports the new head and the log entry” - Test
sdk/web/apps/workspace/test/ui.test.tsx: “a user gets Inspect Diff, Approve and Reject on open proposals only” - Test
sdk/web/apps/workspace/test/review.test.ts: “approves only when every change is approved and rejects only when every change is rejected” - Test
sdk/web/packages/review/test/review/carried-capabilities.test.ts: “review panel store and decision download: hunk approval, navigation, and <stem>.review-decision.json export” - Test
sdk/web/packages/server/test/rooms.test.ts: “approve commits the proposal's batches under its id, by its author, and announces in order” - Test
sdk/web/packages/server/test/rooms.test.ts: “two approvers racing: one commits, the other finds the proposal closed” - Test
sdk/web/packages/server/test/rooms.test.ts: “it cannot approve its own proposal: FORBIDDEN, and the proposal, the head and the session log stay as they were” - Test
sdk/web/packages/mcp/test/tools.test.ts: “a person approving the proposal commits it, and the agent then reads the result” - Test
sdk/web/apps/workspace/test/ui.test.tsx: “history shows the revision, the approver, the proposal and the short receipt” - Test
sdk/web/apps/workspace/test/ui.test.tsx: “an approved proposal names who approved it, across every document” - Production observation, : On the managed deployment, an agent proposed an edit, a person approved it, and the service committed revision 1 naming the approver. Recorded in
evidence/ltg-ws-stage7-wolf-cloud-hostinger-deploy-20261113.json. - Test
sdk/web/packages/server/test/rooms.test.ts: “a commit that leaves a proposal applicable makes it superseded: it is stale, not broken” - Test
sdk/web/packages/server/test/rooms.test.ts: “a commit that makes a proposal impossible makes it conflicted” - Test
sdk/web/packages/server/test/external.test.ts: “approving one proposal conflicts a sibling that an external save came between” - Test
sdk/web/packages/mcp/test/tools.test.ts: “a stale base_revision is REVISION_MISMATCH carrying the head to rebase on”