🔗 Open in Obsidian and connect the sources

The Graphify export left a folder full of markdown—but Obsidian won't find it on its own. You need to point it to the directory. This is done once, from the Manage vaults, choosing Open folder as vault and selecting the generated folder.

Open a note-node any and follow the [[wikilinks]] inside it: each one leads to a neighboring concept. It’s the second brain in action — you explore the knowledge through relationships, not by typing searches.

↑ You open a note and jumps through the backlinks to the neighborhood you need — each node knows its relatives. It’s like walking through the neighborhood, not consulting a list of addresses.

In addition to a .md per node, the export generates a file graph.canvas. Open it in Obsidian: it draws the communities — the groups of concepts detected by the Leiden algorithm—like named boxes on a board. This is the corpus’s high-level view of its themes.

~/vault/graphify/claude-code/
├── graph.canvas      ← abra ESTE: comunidades como grupos nomeados
├── Hooks.md
├── Subagentes.md
├── Context-Window.md
└── … (um .md por nó)

Use the canvas to choose where to start: each group is a topic. Click a community you're interested in and enter through one of its notes — from there, navigate through the backlinks (topic 2). The canvas gives you the overview; the backlinks give you the details.

Each node is a summary of a concept—not the full text. The provenance (which file that concept came from) is recorded in the graph.json, but the source documents no are copied to the vault. The step that closes the loop is bringing these sources closer and adding, in each node note, a signpost pointing to the source document.

↑ The node stays connected to its neighbors through backlinks (cyan), and gains a "source doc" sign pointing to the full file. The concept becomes an entry point to the entire text.

Obsidian has a graph view own — that pretty little dot-and-line. Watch out for the confusion: it only draws the [[links]] among the markdown notes. It's a mirror from the vault, no Graphify's graph. The original typed relationships (with names and direction) live in the graph.json and in the view graph.html.

Doing topic 4 by hand, node by node, is a lot of work. The good news: Claude Code reads the graph.json and the vault folder — then you can delegate wire the sources to it with a single prompt. It finds where they came from, brings the documents into the vault, and writes the "source-doc" link in each note.

Bring the source documents into the vault at
~/vault/graphify/ and link each node to its source.

Steps:
1. Read the provenance in graph.json (the source-file field for each entity).
2. For each node, copy the source document into a subfolder
   called sources/ inside the vault.
3. In each node note’s Markdown file, add a "source doc" link
   pointing to the corresponding file in sources/.

Source of the original documents: 
Important: Obsidian’s graph view is just a mirror of the notes —
the true provenance lives in graph.json; use it as the source.