WolfSuite Workspace · Documentation

# Rooms: shared Office files and their revisions

A room holds a team's documents. Each saved change to a document becomes the next numbered revision, and a person can restore an earlier revision as a new one. [1](#evidence-1) [2](#evidence-2)

## Create a room and add files

A new room is empty. The first version of a document you add is revision 0. [3](#evidence-3)

The web app uploads a file as a form upload. A name that is already used in the room is refused with `NAME_TAKEN`. [4](#evidence-4) [5](#evidence-5)

In the check of the managed deployment recorded on November 14, 2026, creating a room and uploading a Word file both succeeded. [6](#evidence-6)

## Revisions

A saved change applies to the current revision of a document and makes the next revision, one number higher. [1](#evidence-1)

A change made against an older revision is refused with `REVISION_MISMATCH`, changes nothing, and names the current revision to start again from. [7](#evidence-7) [8](#evidence-8)

The history of a document shows each revision, the person who approved it, the proposal it came from and a short receipt. [9](#evidence-9) [10](#evidence-10)

## Restore an earlier revision

Restoring an earlier revision saves its contents as a new revision, so the history keeps every step. [2](#evidence-2)

Only a person can restore. A restore is refused for an agent, from an out-of-date view of the document, and to a revision that is not older than the current one. [11](#evidence-11)

An agent can read the contents of an earlier revision without changing the document. [12](#evidence-12)

## When a workspace is read-only

A read-only workspace refuses every change with `LICENSE_LIMIT`, and the message gives the reason and the way to upgrade. [13](#evidence-13)

## 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.

1. Test `sdk/web/packages/server/test/rooms.test.ts`: “applies the batch to the head: revision + 1, the new hash, one session entry, one doc.committed”
2. Test `sdk/web/packages/server/test/revert.test.ts`: “makes the old bytes the head as a new revision, written by the user, and announces it as a commit”
3. Test `sdk/web/packages/server/test/rooms.test.ts`: “a room starts empty at seq 0; a document is revision 0 and its head is the hash of its bytes”
4. Test `sdk/web/apps/workspace/test/api.test.ts`: “uploads a file as multipart form data”
5. Test `sdk/web/apps/workspace/test/api.test.ts`: “a taken name throws NAME_TAKEN and a refused role FORBIDDEN, with the server's code”
6. Production observation, November 14, 2026: On the managed deployment, a smoke run created a room and uploaded memo.docx. Recorded in `evidence/ltg-ws-stage7-wolf-cloud-hostinger-deploy-20261113.json`.
7. Test `sdk/web/packages/server/test/rooms.test.ts`: “a stale base_revision is refused with the head to rebase on, and nothing changes”
8. Test `sdk/web/packages/mcp/test/tools.test.ts`: “a stale base_revision is REVISION_MISMATCH carrying the head to rebase on”
9. Test `sdk/web/apps/workspace/test/ui.test.tsx`: “history shows the revision, the approver, the proposal and the short receipt”
10. Test `sdk/web/apps/workspace/test/ui.test.tsx`: “an approved proposal names who approved it, across every document”
11. Test `sdk/web/packages/server/test/revert.test.ts`: “is refused for an agent, a stale head, a revision that is not below the head, and one equal to the head”
12. Test `sdk/web/packages/server/test/revert.test.ts`: “rebuilds the requested bytes without writing a commit, including for an agent”
13. Test `sdk/web/packages/server/test/read-only.test.ts`: “is LICENSE_LIMIT with a stable reason, and a message with the reason and the upgrade path verbatim”
