Version history for every edit.

Saving a document

Every document has a Save button in the top toolbar. Saving explicitly — via the button or ⌘S / Ctrl+S — creates a new version with your change summary attached. The button lights up in brand orange whenever there are unsaved changes so you always know where you stand.

• Save & create version — the primary flow. One click, one version.
• Diagram edits auto-save — when you update an inline diagram, Stable Baseline saves the document in the same transaction and records a version labelled “Diagram updated”.
• Navigation guard — try to leave the page with unsaved changes and a modal asks to Save, Discard, or stay.

Opening history

Every document has a History button next to Save. The slide-in panel lists every version in reverse chronological order, with author, timestamp, document title, and the change summary that was attached at save time.

Expand

Compare any two versions

Click Compare at the top of the history panel, then pick any two versions — they don't need to be adjacent. Stable Baseline opens the diff modal with a full line-by-line comparison of prose, metadata, and inline diagrams.

Expand

AI summary of the diff

The top of the diff modal shows an AI summary of what changed — in plain English, generated automatically when the modal opens. No credits charged, no extra clicks. It surfaces intent (“tightened the security warning”) so you don't have to skim every line to understand a change.

Diff controls

• Split / Unified — side-by-side or inline.
• Expand all — reveal every unchanged line for full context (by default unchanged runs are collapsed).
• Stats header — “2 lines added · 5 lines removed” at the top so you know the size of the change at a glance.
• Diagram diffs — inline diagrams compare both sources and renders side-by-side.

Rolling back

Pick any version, hit Restore this version, and Stable Baseline creates a new version on top that matches the one you chose. The intervening versions stay on the timeline — nothing is deleted. You can always roll forward again.

Who changed what

Every version records:

• Author — the teammate or agent that made the edit, with their avatar and display name.
• Timestamp — when the save landed on the server.
• Change summary — a short description of what changed (typed by a human, auto-generated for diagram updates, or supplied by the agent on save).
• Scope — the workspace, project, and item the change applied to.

Agent attribution

When an AI agent edits something on your behalf, it's attributed to the agent — not to you. If you use multiple agents (say, Claude Code for your main codebase and a scoped agent for docs-only updates), each has its own identity on the timeline, so you always know exactly which one did what.

What is versioned

• Documents — every save creates a version, with the full CDMD source stored server-side.
• Diagrams — each source-code change records a new diagram version; the previous render stays available for diffing.
• Plans, phases, tasks — each mutation (date change, status flip, new task) records an activity log entry with the old and new values.
• Improvements — each status transition and field change records an activity log entry you can audit later.

Keyboard shortcuts

• ⌘S / Ctrl+S — save and create a version.
• Esc — close the diff modal or the history panel.