Runic
MAP

Every document and every link, on one canvas

Map draws your whole workspace as a graph: processes as circles, sequence diagrams as rounded squares, .do and .go lines as arrows, missing targets as hollow red ghosts.

Try it free →Read the docs

What the map shows

Every document is a node, sized by its line count: a 40-line process reads as bigger than a 4-line one. Processes are circles, sequence diagrams rounded squares. Every .do and .go line, in either kind, becomes an arrow from the calling document to the called one. The header counts 'N processes · M sequences · K links · J missing targets'; a legend spells out the shapes and colors: ○ process, ▢ sequence, violet for .do, blue for .go, dashed red for missing.

A referenced name with no document behind it becomes a ghost: a small hollow node with a dashed red outline. However many documents point at the same missing name, there is one ghost for it, so a typo shows up once instead of staying invisible. Documents that nothing references and that reference nothing draw in gray with a muted label; the tooltip says 'not linked yet'.

The document you came from is filled violet. A translucent ring marks incoming references and thickens with the number of distinct callers.

How the layout works

The layout is a force simulation: nodes repel each other, linked nodes pull toward a rest length, and gentle gravity keeps the graph centered. Runic starts from a deterministic ring and runs 320 steps before showing anything, so the same documents always open to the same picture, fitted to the screen.

Hover a node and everything outside its neighborhood dims, with a tooltip giving '<name> — N lines · called by K documents — click to open', prefixed 'sequence diagram ·' for a diagram, or 'Referenced but never written — a broken link.' for a ghost. Drag a node and it stays pinned under your pointer while the rest relax around it. Drag empty space to pan; scroll to zoom between 25% and 250% (Fit lands between 25% and 160%); Fit frames the whole graph again.

Why it matters

A sidebar lists documents; a map shows structure. Hubs stand out by their rings, orphans sit gray at the edge, and every broken link is a red dashed arrow you can see from across the room. It is the fastest way to answer 'what does this depend on' for a workspace you did not write yesterday.

Limits and gotchas

Self-references are not drawn, and repeated links of the same kind between the same two documents collapse into one arrow. The map also works in guest mode, on the documents in your browser.

Clicking a ghost does nothing, because there is no document to open. Fix the reference in the calling document, or create the missing process from the 'Create as process' quick fix in the editor. Positions are recomputed whenever the document set changes; the map does not remember a manual arrangement. The MCP tool workspace_graph returns the same edges, orphans, unresolved names and cycles as text.

How to use it

  1. Click Map in the top bar
    The map opens full-screen over the editor, titled 'Process map'.
  2. Read the header
    'N processes · M sequences · K links' plus a red '· J missing targets' when any reference points nowhere. The legend on the right decodes the shapes and arrow colors.
  3. Hover a node
    Its neighbors stay bright, everything else dims, and the tooltip in the corner shows line count and caller count, or 'Referenced but never written — a broken link.' for a ghost.
  4. Rearrange if you like
    Drag a node to pin it while the rest settle. Drag the background to pan. Scroll to zoom. Click Fit to frame everything again.
  5. Click a node to open it
    The map closes and that document opens in the editor. Close or Esc returns without changing documents.

Commands & shortcuts

MapTop-bar button; opens the process map
FitFrames the whole graph in the canvas
Close / EscReturns to the editor
Click a nodeOpens that document in the editor
Drag a nodePins it while the layout relaxes around it
Drag the backgroundPans the map
ScrollZooms between 25% and 250%
workspace_graph (MCP)The same graph as text: edges, orphans, unresolved references, cycles

Tips

  • Open the map after a big import or an AI-generated system: any name the generator misspelled is a red ghost.
  • Thick rings mark the hubs. Rename those with care; the rename feature updates every caller, but the map shows you how many there are first.
  • Gray nodes with 'not linked yet' are candidates for a .do from a parent process, or for deletion.
  • Names longer than 26 characters are cut to 25 plus an ellipsis on the canvas; hover to read the full name in the tooltip.

Questions

Why is a node hollow and red?

It is a ghost: some document references that name with .do or .go, but no document with that name exists. Fix the spelling or create the document.

Does the map include sequence diagrams?

Yes. Diagrams draw as rounded squares, their .do and .go lines are arrows like a process's, and a process's .do to a diagram lands on the square. The header counts them separately.

Will my dragged layout be saved?

No. The layout is recomputed from the documents each time, deterministically, so it looks the same on every open.

What do the two arrow colors mean?

Violet is .do, a call that returns. Blue is .go, a jump that ends the current path. Dashed red means the target is missing.