🧩 The 4 integration strategies

The simplest strategy is not to integrate anything: keep the vault generated by Graphify as a separate, dedicated vault of your main vault. It lives on its own — you open it when you need that knowledge and close it when you’re done. That’s the default and the safest of all.

↑ The four strategies on a single axis: on the left, you can undo with one click; on the right, the knowledge merges with yours—more valuable, harder to reverse. The standalone is the left endpoint.

One step beyond standalone: put everything into a subfolder of your main vault — for example graph-imports/claude-code-docs — which you can delete entirely at any time. The knowledge stays close, in the same context as everything else, but isolatable: if you don't like it, delete the folder and that's it. It's the perfect middle ground.

meu-vault/
├── Projetos/
├── Diário/
└── graph-imports/          ← a quarentena
    └── claude-code-docs/    ← apague esta pasta e nada mais é afetado
        ├── Hooks.md
        ├── Subagents.md
        └── Context-Window.md

Instead of bringing everything in, you gathers a subset: ask Claude Code to import only the relevant notes — for example, the ~100 that mention subagents — and ignore the rest. It’s curation: the main vault grows only with what you’ll actually use, and the 500 files you’d never consult are left out.

No vault gerado em ~/vault/graphify/claude-code, traga apenas as
notas relacionadas a <tema> (ex.: subagents) para a subpasta
graph-imports/<tema> do meu vault principal em <caminho-do-vault>
e ignore o resto. Preserve os wikilinks entre as notas que vieram.
Liste o que trouxe e o que ficou de fora.

Maximum integration: Claude Code redistributes each note to the vault subfolder that makes the most sense — a note about hooks goes in your automation folder, one about context goes in your fundamentals folder. The knowledge dilutes into your existing structure, as if it had always been there. Total consistency—and the hardest path to undo.

Chose the quarantine? Here's how to do it in practice. Instead of dragging folders one by one in the file explorer, describe what you want and Claude Code will transfer the entire structure for you—in less than a minute, preserving the wikilinks.

Mova a estrutura do vault em ~/vault/graphify/claude-code para
dentro do meu vault principal em <caminho-do-vault>, numa subpasta
graph-imports/claude-code-docs. Preserve os wikilinks [[...]] e não
sobrescreva nada que já exista lá. Ao terminar, liste o que foi
movido e avise se algum link quebrou.

Four options can make the decision difficult. This tree sorts it out in seconds: answer yes or no and it takes you to the right strategy. The underlying rule is always the same — the more integrated it is, the more coherent and less reversible.

↑ Follow the green (yes) and red (no) arrows. Notice: the first question isn’t even about the vault—if the source was code, the Graphify graph is already enough, and you don’t even export to Obsidian.