One body of thinking, every output in sync.
Real strategy work is never one document. It is a folder: research notes, interview transcripts, a working paper, and the three outputs different audiences need. Abstract works across all of it at once.
The thinking lives in six places and the outputs drift.
You update the strategy after a sharp conversation, and now the exec summary is wrong, the deck says something slightly different, and the research doc still argues the old position. Chat tools make this worse: each document is a separate thread, regenerated whole, with no memory of the others.
One corpus, many outputs, one instruction.
Load the corpus.
Research, transcripts, prior drafts, competitor notes: one project folder. The agent can read all of it; you can query it while you think.
Build the outputs.
Iterate a structure with the agent, then grow the set: master research doc, strategy paper, executive summary, deck outline. Four documents, one source of truth.
Change the thinking once.
When the strategy moves, one instruction updates every downstream document. Each change arrives as a diff against the document it belongs to.
Thursday's customer call changed your mind about the wedge. You drop the transcript into the project, update the strategy paper's core argument, and ask Abstract to carry the change through. It proposes edits to the exec summary, the deck outline and two sections of the research doc, each shown as a diff with the reasoning. You reject one (the deck should stay high-level), accept the rest, and every version of the story agrees again by lunch.
Scoped edits, reviewed per document.
Scoped edits mean the agent updates the argument you changed, not the whole document. You review per document, per change.
Nothing rewrites silently, so your voice survives your tools.
Your files in, every format out.
Sources: any files you have; meeting transcripts land as files today, with connectors on the way Coming.
Outputs: DOCX, Google Docs In beta, PDF, and publish to web In beta.
Questions
Can I ask questions of my research without editing anything?
Yes. The chat rail answers from your project sources, cited, without touching a document.
Does it handle long documents?
Projects are folders of Markdown files; long documents work, and long sets of documents are the point.
Will it flatten my writing style?
Edits are proposals against your text, not regenerations of it. Keep your own project style rules and a formatting agent to enforce them.