Examples

Four maps worth stealing

Each one is a finished canvas you can load with a click and reshape into your own situation. They are the same worked material the app ships: real titles, real descriptions, connections that mean something, and a Situation already framed, so the exported brief reads like a brief from the first second.

Investigate a bug

The walkthrough's case: checkout fails for some people, nobody knows why, and you want a coding assistant to read the repository instead of inventing a plausible theory. Twelve blocks that separate the symptom from the beliefs around it, framed in Investigate mode with the reproduction as the first boundary. If you only load one example, load this one, then read the walkthrough that builds it from nothing.

12 blocks · Investigate mode · your current canvas is left alone until you confirm.

Investigate a bug, the blank template

The same shape without the checkout story: symptom, suspects, evidence, then a fix that has to prove itself. Use it when the bug is yours and the story above does not fit. It lands arranged, framed for a repository you have open, and told to reproduce before theorising.

13 blocks · Investigate mode

Inherit a codebase

Somebody left, the repo is yours now, and the first wrong move is trusting what the README says. This map works from "unknown repo" to a first safe change: what is believed, what is actually verified, and the questions whose guessed answers cost the most.

13 blocks · Investigate mode

Migrate a system

Old to new with a way back at every step. The shape most migrations skip is the reconciliation loop: old versus new, per entity, every day, with a threshold that blocks the next phase. This map carries it, plus the risks that live at the cutover and the terminator that only fires when the old system is off, not merely unused.

15 blocks · Plan mode

Make one of these yours

Open the canvas Nothing is uploaded. Your canvas stays in this browser.