two ways to look
Each situation below comes twice: the evening somebody built its map of connected blocks, and the map itself. Both open without an account, and neither saves anything you do.
The interview asks its own questions, and the answers come back exactly as the person typed them at the time. The map then builds itself in front of you, block by block, in the order the agent wrote them. All of it already happened, so nothing here calls a model.
A real map, published by the person who keeps it. Open it, move around it, read what is on it. Then take it away: one .mmap file, or the same map as a document, a PDF and slides.
situations
One person, their own maps, and nobody else in them. Everything here works on the free plan.
A ready interview, Project kickoff, asks its questions first and lays out the answers as branches. On this map, each thing you don't know yet connects to the stage or task that answers it. As you build, Claude Code marks each stage's progress, with a key narrowed to this map and nothing else.
The map
The replay
Its four files
The import takes a web page whole and lays it out as blocks. On this map, connections between eight car companies show what passed from one to another: a designer, parts, a plant. Open a block, and its Nearby section lists what is close to it in meaning, on any of your maps.
The map
The replay
Its four files
An interview asks, you answer as much as you feel like, and the map's chat files the answers into branches. The map keeps the conclusions: a branch per principle, and under each, rules for when to do what.
The map
The replay
Its four files
A map that something else writes into: a site, a shop, a script of yours. Nobody has to open the app for a block to appear.
The form on your site carries a key narrowed to the leads map, and nothing else of yours. Every submission arrives there as a block: name, company, what they asked, in the order they came. By Wednesday morning yesterday's enquiries are on one map, beside everything else you keep.
The map
The replay
Its four files
Each order lands on the orders map as a block under its day: the item, the amount, the time. That map keeps a schedule of its own, and a standing instruction to go over the week. Overnight its chat works through the orders and lays out what sold and when.
The map
The replay
Its four files
One map, several people, each opened to their own part of it. One shared map comes with Pro; more of them come with Workspace.
One map holds the whole project, and you keep it. Somebody joining on Monday gets one branch of it, and that branch is what the map is for them. The blocks they see are the blocks you see, and their comments land where you can find them.
The map
The replay
Its four files
You take one of these maps by downloading it and importing it into a map of your own. The .mmap file carries the blocks, the connections and the layout, and importing works on the free plan. Whatever you change after that is yours.
in practice
Two questions everybody asks before starting: what happens tonight, and what happens once the novelty has gone. Tonight needs nothing but a browser. What changes as the months go by is how little of the sorting you do by hand.
Sign in with your Corlecti ID, and open an empty map. Put in three thoughts, a link, the PDF you meant to read. Then ask the map's chat to build, and it lays them out as blocks with the connections between them.
A thought goes to the Telegram bot the moment you have it, typed or spoken. You sort nothing then, and one pass with the agent in the evening lays out what piled up. On Friday the graph lens shows the same map as connections: where it is dense, and what stands alone.
Every map above began from nothing, on the free plan. Pick a situation, or bring your own.
