Skip to content

TopicsIdea

Versions

A version is a topic as it read after one sitting of work. It says who worked on it, when, and what changed.

A colleague has the agent rewrite the reply to a customer. An agent task rewrites a runbook overnight. Anyone can read what the topic said before, and who changed it, without reading every small edit.

Work in the topic’s own chats goes into one version until an hour passes with no change. The next change opens a new one. Everyone who changed the topic during the sitting is in its version. We weighed one version a day and one per chat, and left both. A day mixes a morning run with an afternoon discussion, and a chat can go on for days.

Some work always gets a version of its own. A run of the topic’s agent task is one, and so is a page imported into the topic. So is a session of a coding agent like Claude Code writing to it, or the agent writing into it from another topic’s chat. A change that leaves the topic saying the same thing opens no version.

Emargen writes each version’s line itself. The line says who worked on the topic (“with the topic agent” when the agent wrote for them), and when. It also says what changed, down to each field’s old and new value. It never quotes anyone’s chat.

ACM-281's versions, newest first: v2, Tom Weber, with the topic agent, Changed What we tell them · Status Open → Waiting on the customer, Mon 12 Oct, 14:10; v1, Ana Ruiz, with the topic agent, Created the topic: wrote The question and What exists today · Customer set to Northgate · Status set to Open · Reply by set to Tue 20 Oct, Sat 10 Oct, 09:30.ACM-281's versions, newest first: v2, Tom Weber, with the topic agent, Changed What we tell them · Status Open → Waiting on the customer, Mon 12 Oct, 14:10; v1, Ana Ruiz, with the topic agent, Created the topic: wrote The question and What exists today · Customer set to Northgate · Status set to Open · Reply by set to Tue 20 Oct, Sat 10 Oct, 09:30.
A customer question at ACME, the company in the docs' pictures: its owner made it with the agent, then a colleague in sales had the agent write the reply.
  1. Who worked on it, here with the topic agent.
  2. The day and time of the sitting.
  3. What changed: the section rewritten, and the field’s old and new value.
  4. The first version, the one that started the topic.

Open a version, and you read the topic as it was, with its title, sentence, sections and fields. Comments, files, labels and lists aren’t part of a version. Turn on Changes to compare a version with the one before it, and what changed is marked.

Version 2 of ACM-281 with Changes on: the strip says against version 1, Status shows Open with an arrow to Waiting on the customer, and What we tell them is marked Changed, with a green bar beside its new paragraph and its open decision.Version 2 of ACM-281 with Changes on: the strip says against version 1, Status shows Open with an arrow to Waiting on the customer, and What we tell them is marked Changed, with a green bar beside its new paragraph and its open decision.
The second version against the first: the status moved, and the reply and its open decision were added.
  1. Version 2 of 2: when, who worked on it, and the version it’s compared with. The arrows step to the older and newer ones.
  2. Changes, switched on.
  3. A field that changed, its old value then its new one.
  4. Changed: a section that changed.
  5. What was added, with a bar beside it.

We left out a button that puts an old version back. If you take part in the topic and want something back, ask the agent. Say which version to take it from: “Put What exists today back as it read in version 1.” It reads that version and writes what you asked for. That change is a version like any other, and every version is kept.

Everyone who can open a topic can read its versions, including people who only read the topic.

How to

Page by page