Content health & curation

A wiki decays because nothing watches it: duplicates breed, stale pages read as true, and cleanup never happens. rooms works the problem from the other end — every document has an owner, a live dashboard shows what's orphaned, stale, or unread, and a curation queue turns those signals into a short, reviewable to-do list. Nothing is ever changed or deleted behind your back: the system suggests, a person decides.

Every document has an owner

When a document is created, whoever made it becomes its owner — the person to ask about it, and the one accountable for keeping it current. The owner is preserved across edits (editing someone's document doesn't quietly make you the owner) and can be transferred to any company member at any time. Ownership is what makes "who do I ask about this?" always have an answer — and what lets the system notice when a document is left orphaned because its owner has left the company.

Claude tool: setDocOwner · In the web app: the owner shows on each document, with a transfer control.

The content-health dashboard

The Content health view (admin only, 🩺) is a fast, live picture of your corpus — no waiting on AI, just a read of the facts. It gives you a single health score (the share of documents with no outstanding flag) and lists the documents that need attention, grouped by room:

Claude tool: getContentHealth.

The curation queue

The dashboard tells you what's wrong; the curation queue (the Curation view, 🧹) tells you what to do about it — one card per suggestion, each with a visible reason and a one-click action. It's suggest-only: the queue never acts on its own, and there's no nagging — a suggestion appears once and stays put until someone resolves or dismisses it.

Most actions resolve their own suggestion by changing the underlying state — verifying a document clears its "verify" card; reassigning an orphan clears its "reassign" card. Every action is logged, so the queue doubles as a record of the upkeep that's actually happening.

Claude tools: getCurationQueue, curate (verify / reassign / dismiss), verifyDoc. Appointing curators is done in the web app by an admin.

The Curation view has two tabs: Documents (the suggestions above) and Rooms (below).

Whole rooms — empty & stale

Documents aren't the only thing that goes stale — rooms do too. A room created for a project that never happened sits empty; a room whose last activity was a year ago is likely done. The Rooms tab of the curation queue surfaces both, so the room list stays a set of live, useful spaces instead of an attic.

Archiving a room is reversible and is not deletion. An archived room drops out of the room list, navigation, the Files browser, search, and health — but its documents keep serving at their URLs, and you can restore it anytime from the Archived rooms panel at the bottom of the Rooms tab. Nothing is ever deleted by the queue.

Claude tools: getCurationQueue (returns room suggestions too), curate with archive-room / verify-room, and archiveRoom / unarchiveRoom / listArchivedRooms to manage rooms directly.

What people looked for and didn't find

The best signal for what to write next is what people searched for and got nothing. rooms keeps a quiet log of searches and questions, and the Search gaps panel (admin) surfaces the queries that came back empty — grouped, counted, and dated — right next to overall demand. Each empty query is a document waiting to be written.

Claude tool: searchGaps.

Tidy a room into folders

As a room fills up, related documents drift out of order. Organize is an on-demand helper that reads a room's documents and proposes how to file them into folders — grouping ones that belong together and naming a new folder when a cluster has no home. It's suggest-only and scoped to one room: nothing moves, nothing changes access, and you accept or dismiss each suggestion individually (or apply them all at once). Each suggestion shows its confidence and the reason it grouped that way.

In the web app: the Organize ✨ button in a room's header (editors and up). Claude tool: suggestReorg — apply an accepted suggestion with setDocFolder. It's available in rooms with a handful of documents or more; very small rooms and deal rooms are skipped.

Everything, both ways