Dump, map, think, collapse.
Four steps. The first takes you ten seconds. The second takes the engine about twenty. The third is where you live. The fourth is how you leave with something you can use.
- 1
Dump
Type or paste. Nothing needs to be in order. If you have a voice memo transcript, paste that. If you have a Slack thread, paste that. The splitter turns it into fragments, one thought each, and numbers them so everything downstream can point back.
- 2
Map
The engine reads every fragment, groups the ones that are about the same thing, names each group plainly, and draws connections between thoughts that belong together, each with a short reason. Questions you half asked are gathered into one node. Thoughts that fit nowhere stay loose at the edge.
- 3
Think
Hover a node to see the exact lines it came from and light up its connections. Rename, merge, remove. Add new thoughts next week and re-map; the meadow morphs rather than resets. Zoom out to see the shape, zoom in to argue with it.
- 4
Collapse
Fold a cluster into an outline when you need to write, or a next-steps list when you need to do. Export markdown. Share a read-only link with your team on Studio. Come back when the next dump arrives.
The rules the map follows
- Every node cites the fragments it came from. No source, no node.
- Every connection has a reason you can read.
- Open questions are framed as things you could decide, not verdicts.
- Nothing you wrote is dropped. Uncited fragments become loose thoughts.
- Re-mapping keeps ids stable so you can watch the change.