Each note asserts a single idea, cites its sources, and explains context so it stands alone without its parent document. It evolves through revisions, gaining sharper language and better links. Atomicity keeps it reusable, while clarity and provenance guard against confusion and bias.
Avoid vague buckets like “marketing” or “psychology.” Instead, write a testable statement, such as “Clear value propositions reduce onboarding friction by setting expectations.” Support it with a brief explanation and references. Claims invite argument, improvement, and linking, while containers merely accumulate clutter.
Prefer action-oriented, declarative titles that signal utility, such as “Short feedback loops accelerate learning in ambiguous domains.” Titles that describe a conclusion guide linking and retrieval. Generic nouns hide meaning, whereas pointed assertions make neighbors obvious during future traversals and synthesis sessions.
Practice definitional links for clarity, contrast links for boundaries, causal links for mechanisms, and sequence links for processes. While synthesizing a market essay, I linked “Switching costs shape retention” causally to “Onboarding sets habits,” then contrasted both with “Discounts create temporary loyalty,” revealing a richer retention model.
Three to five strong links per note usually beat fifteen shallow ones. Aim for diversity: at least one explanation, one counterpoint, and one concrete example. During weekly reviews, demote decorative links into a scratch file, then promote underlinked but powerful relationships into the body where reasoning actually happens.
Backlinks expose where an idea already lives. Create a short summary atop the backlink panel, curating the most relevant neighbors. Convert recurring patterns into a hub note with an introduction, key paths, and open questions. Neighborhoods turn wandering into intentional traversals that repeatedly yield insight.
Start with Purpose, then Claim, Evidence, Counterpoints, Examples, and Next Questions. Add References and Links sections for provenance and navigation. Keep frontmatter minimal: created date, status, and tags if helpful. A predictable structure accelerates editing, encourages better linking, and discourages hoarding half-baked highlights.
Prefer human-readable slugs that echo the claim, combined with stable unique identifiers when necessary. Avoid deep folders; let links and hubs express structure. When renaming titles, keep the slug or UID stable so external references, citations, and your future scripts never silently break.
Favor text files, open formats, and predictable link syntax. Test migrations between tools before you commit deeply. I once moved a thousand notes overnight because names and links traveled easily, preserving context. Freedom to switch keeps incentives aligned with your thinking, not vendor roadmaps.
Give each hub a clear promise, boundaries, and an onboarding paragraph pointing to three essential starting notes. Include sections for definitions, debates, case studies, and open questions. Update sparingly; hubs are guideposts, not dumping grounds, and they shine when they curate decisive, legible paths.
Once a week, open your graph and choose a cluster aligned with a current project. Follow three hops while narrating aloud what connects each step. Capture surprises as new notes, and convert dead ends into questions. Close the session by scheduling one promising synthesis experiment.
Track answers produced, decisions accelerated, and reused arguments, rather than raw link totals. A tiny, well-linked constellation that delivers weekly outcomes beats a sprawling galaxy of orphans. Let metrics provoke conversation and pruning, reminding you that the graph serves work, relationships, and learning over aesthetics.
All Rights Reserved.