3.3 · Editing and versioning

How the editor works: saving, restorable history, and locks so 2 people cannot collide on a document.

Context documents, the record of what GrowthOS knows about your company, open in an editor that autosaves as you type, keeps history you can restore, and locks documents so 2 people never overwrite each other. This guide covers the mechanics, then the part that matters more: what happens to your edits after you save.

The editor

Context documents open in a full document editor. Type / for the block menu: headings, lists, task lists, quotes, code blocks, dividers, tables, and images. Changes save automatically as you type, and the footer shows Saved or Saving. Cmd+S saves on demand.

Your edit is not saved to the document until you click Done. The button sits at the bottom of the section, low enough that the macOS dock can cover it. No Done, no save.

One person edits a document at a time. If a document is open elsewhere, you see who has it and a Take over button to claim it. That person may be your strategist, your GrowthX contact, rather than someone on your team.

AI quick edits

Select any text and choose AI in the floating toolbar to describe a change in your own words, or pick a preset:

Preset	What it does
Humanize	Strips hyperbole and AI clichés, varies rhythm so it reads human
Tighten	Cuts padding and redundancy while keeping every point
Break up the wall	Splits dense paragraphs, adds bullets where they help scanning
Match our voice	Rewrites to follow your brand writing guidelines
Answer first	Leads with the key point, then support
Fix grammar & spelling	Corrects errors only, leaves voice and structure untouched

Quick edits work on style and structure only. As the menu itself says: no research access, so it cannot add new facts, statistics, or sources. Facts stay your job in this area, which is the point.

Version history

On your foundation documents, the 4 base documents of your context, the History button opens Named Versions. Every change autosaves regardless, and on top of that you can:

Save a named version before a big rework, so there is a labeled point to come back to.

Compare any version against the current draft, side by side.

Restore a version when a rework went wrong. Your current draft is kept in history too, so restoring is itself undoable.

Save a named version before a big rework and nothing is lost. Autosaves between named versions are pruned over time, so a named version is the durable checkpoint.

What happens after you edit

Your edits do not sit in a document waiting to be noticed. Context flows downstream in 2 ways:

Immediately: agents read context documents at the moment they work, so the next opportunity researched (the pages agents propose writing or rewriting) and the next draft written start from the calibrated version.
On recalibration: your accumulated context edits get folded into the Writing Profile, the compiled version of how you sound, and refreshed drafts, so the voice and claims stay in sync with what you calibrated.

This is why stage 3 of the tutorial comes before creating anything. An hour of calibration here quietly improves every page of the hundreds that follow.

Common questions

Can I break something by editing? Not if you checkpoint: History keeps the agent's original draft plus every version you named, restore is one click, and restore itself is undoable. Autosaves between checkpoints get pruned over time, so name a version before a big rework.

Do I edit the document or regenerate it? Edit when the document is mostly right. When it misses broadly, ask your strategist to regenerate it, with a note from you to steer the rewrite: regenerating replaces the document rather than editing it, so save a named version first.

Does fixing context fix the drafts I already have? No. A context change applies to work generated after it. Drafts already in production keep the facts they were written with until you regenerate them, so if you correct something material, sweep the open briefs that relied on the old version rather than assuming they picked up the change.

Do we keep our context somewhere else and paste it in? No. Edit it here. History, named versions and locking exist so the in-app copy is the safe place to work, and a copy maintained elsewhere goes stale the moment an agent updates something.