brief/launch-plan.md

The brief is a plain file any agent can edit.

Review the agent's edits after it finishes. Every agent edit is reviewed before it lands.

Claude · state the review rule

An agent edit, caught in review.

A map of the neighborhood

Where do I think? That's Obsidian. A vault for connecting ideas, with a plugin for everything. Keep it. Stet and Obsidian →

Where do my agents keep their memory? That's OpenKnowledge. A wiki agents can grow on their own. A different bet than ours. Stet and OpenKnowledge →

Where do I run my coding agents? That's Nimbalyst, or Cursor. Cockpits for shipping software. Stet and Nimbalyst →

What did the AI paste into my draft? That's iA Writer. It dims the text you didn't write. We admire it. Stet and iA Writer →

Who approved this?

That one is Stet.

Stet is a document editor for writing that carries your name. The spec that ships. The brief the agent acts on. The SOW that gets signed. Agents propose changes. You review each one and accept, reject, or refine it. Nothing lands without your sign-off, and the record of what you approved stays with the file.

The other tools trust the AI and check later, or never. Stet asks first. That's the whole product, and no one else builds it.

It's all the same files

You don't have to leave anything. Stet works on plain markdown in a folder. Keep your vault. Keep your terminal. Keep Claude Code, Codex, whatever comes next. Point Stet at the folder where the words matter, and every change becomes a proposal you can stand behind.

Still using Google Docs or Word for the documents with stakes? That comparison is less friendly. →