Extract a map from a document
The fastest way to start a map is the material that already describes how work happens. Compass can read a document and propose the pages and connections for you.
- Bring the right source
Good input is anything that describes how the work is done: a process doc or SOP, a recorded walkthrough's transcript, onboarding notes, a meeting recap. Anything with people, systems, steps, and friction in it. Vague strategy decks make poor input; concrete "here's how it actually goes" material makes great input.
- Hand it over
Choose New page → From a description and paste the material in. (From files does the same thing starting from a document you upload.) It goes to zv1, which reads it and works out what deserves its own page — the workflows, people, systems, and pain points in it — along with how they connect.
- Review before you keep
zv1 searches your existing map first, so it won't propose a page for something you've already written down, and it tells you what it found before creating anything. Each page arrives as a proposal you approve or decline, and you can ask for changes in the same conversation — split one page in two, retype something, skip the parts that are noise. Your judgment is what makes the map correct.
- Fill the gaps and connect
The source won't mention everything. Add the pages it missed, and wire up the typed connections it didn't infer, so the map carries meaning you can traverse.