#2 Limits of the Zettelkasten: What We Leave Out • Zettelkasten Live

The core takeaway is that a Zettelkasten archive should be built around clear principles of knowledge work—then constrained by what the archive is meant to store—rather than by trying to capture every kind of writing or life note. One participant’s approach is “include everything” that has reusable value for production, while explicitly excluding diary-style event logging and fiction drafts. The other approach is more selective and historically evolved: early note categories became too complex, so personal material was moved out, leaving an archive focused on citations, comments on citations, and reusable ideas.

A major practical decision in both approaches is what belongs in the archive versus what belongs elsewhere. The “include everything” method organizes notes into four broad departments using double-hash tags: double hashw for scientific value (truth-oriented knowledge), double hashhL for practical, body-related work (training, nutrition, and coaching needs), double hashL for pragmatic, application-oriented domains like business and ethics, and double hashk for arts (music and novel-related writing). Even when meta-tags aren’t used constantly, they support filtering and reflect two epistemic paradigms: determining what’s true versus pursuing what’s useful and actionable.

The more minimalist approach rejects elaborate category hierarchies after years of use. It keeps the archive for material that can be reused later—citations, thoughts derived from reading, and creative ideas intended for future products—while moving diary entries out. Diary content is treated as “event logging,” which doesn’t qualify, except for rare cases where the note captures a reflection on a thought rather than the event itself. The archive also avoids storing personal data in insecure ways; for example, synchronizing through Dropbox is described as a security risk.

Both participants then zoom out to a framework with three layers: (1) knowledge work itself and how it functions, (2) the Zettelkasten method as principles rather than techniques, and (3) the software layer that merely implements those principles. That separation matters because software changes quickly, while the underlying principles change slowly. In this view, tools like nval are treated as minimal search-and-folder systems, with most method behavior derived from the archive structure rather than from complex app features.

A recurring theme is that “principle” and “technique” must not be confused. Branching, sequencing, and note-structure choices are techniques that apply principles like connection and atomicity. Even physical slip-box practices are framed as compatible with the same principles: writing one thought per slip, using the box as a buffer for learning, and relying on “re-entry” or self-similarity—applying the same organizing logic at different scales (from large outlines down to paragraph-level mini-outlines).

Finally, the discussion addresses limits: when sequences are rearranged, reconstructing the original connections can become difficult, which is why the archive must preserve enough structure to remain usable later. The practical conclusion is straightforward: be explicit about the archive’s intent, then decide what qualifies as knowledge work for that purpose—everything else belongs outside it, even if it’s meaningful.