Take Permanent Notes in Obsidian

Permanent notes succeed—or fail—based on one requirement: they must be the product of the writer’s own thinking, not a copy of what was read. Unlike literature notes, which can follow recognizable templates and “prescribed ways” of recording, permanent notes (often called slip box notes, Zettels, or evergreen notes) need a structure that comes from process rather than format. That process is elaboration: expanding an idea and connecting it to other ideas until new relationships emerge. Elaboration only works when the idea is abstracted out of its original text—stripped of the supporting context that made sense in the book, but would clutter the note later.

Abstraction is what makes a note “atomic,” a term tied to smart notes and the “little castle” method. An atomic note is permanently understood: it can be rewritten in the author’s own words and still make sense to someone else independently of the original arguments, evidence, or connected ideas. That independence is what makes the note malleable—capable of being linked, discussed, and used to build arguments, narratives, or chains of reasoning inside a larger knowledge system.

The workflow described starts with batching. Instead of converting notes immediately as they’re taken, the approach is to accumulate a backlog of literature notes, then process them later in a focused session. The rationale is practical: after fully consuming a book, the reader has a better sense of how the knowledge should be organized, and the translation from literature notes to permanent notes becomes more coherent. This mirrors a method attributed to Niklas Luhmann’s “slip box” tradition (referenced indirectly through the “Aluminum himself” phrasing), where literature notes are collected first and only later transformed.

In Obsidian, the conversion is demonstrated as a hands-on editing loop. The writer highlights the relevant passage in a literature note using Obsidian’s “double equal sign” markup, then creates a new permanent note (often from a placeholder) in a separate panel. The permanent note is drafted by elaborating on the highlighted idea in the context of the book, then abstracting it into an atomic statement—such as reframing “writing” as a process of abstracting ideas from original context so they become generally usable.

To keep the system navigable, the workflow adds cross-references. The permanent note includes a link back to the source literature note and often records a page number so the author can trace the origin without repeatedly “ping-ponging” between notes. Obsidian supports this through aliases and backlinks: typing a link creates an alias that opens the permanent note, while backlinks allow the literature note to show which permanent notes depend on it. The result is a growing network where notes connect like a lattice.

Finally, not every fleeting or literature note becomes permanent. Time and judgment matter. In the example, three permanent notes are created, and an additional literature note is added when an earlier one failed to expand into the intended permanent insight—reinforcing the idea that permanent notes are selected and refined, not generated indiscriminately. The next step after building these notes is adding them into the slip box to form the knowledge base’s structure.