Does EVERY source need a note in your zettelkasten?

A Zettelkasten built around Tle Casten-style notes doesn’t always require a dedicated “source note” for every citation or snippet—sometimes a link inside an existing atomic note is enough. The practical rule is whether that source will be useful beyond a single atomic idea. When a source is only being used for one narrow purpose, creating a separate bibliographic note can become busywork without improving retrieval or connections.

In this workflow, permanent “atomic notes” hold single ideas in a growing knowledge base, while “bibliographic/source notes” store the material behind those ideas—quotes, data, and reference details—so they can connect to the atomic notes they support. The system is typically implemented in Obsidian, with a dedicated “sources” folder for bibliographic notes. Source notes then link back to the atomic notes in the main Tle Casten area, keeping the knowledge network interconnected.

The question driving the discussion comes from Jean Carlo on Instagram: does every reference—no matter how small—need its own source note with a consistent year/title naming format? The answer is yes in spirit, but no in practice. A source note is recommended when there’s uncertainty, because adding more interconnected notes generally strengthens the system as long as links are maintained. But there are rare cases where a source note would add redundancy.

Those exceptions show up when the extracted information will never be revisited as a standalone reference. The decision test is simple: when adding a new atomic note, ask what it connects to that already exists in the Zettelkasten. If the only connection is to one atomic note—and the source’s content will be needed only when that atomic note is opened—then duplicating the bibliographic details into a separate source note may not be worth the time. In that scenario, linking directly to the website or including the book citation inside the atomic note can preserve traceability without creating an extra node in the network.

A concrete example centers on a note titled “juggling as a metaphor in the media.” The creator isn’t trying to analyze the underlying article topics (like tourism policy or market speculation). Instead, the goal is to collect instances where mainstream media uses the word “juggle” metaphorically. Articles such as “Barcelona protesters demand a affordable rents as Spain juggles tourism impact,” “Global markets juggle rate speculations and nvidia's big reveal,” and “five tips to juggle work life balance in agriculture” are treated as evidence for the metaphorical usage of the term. Since the content is only relevant for that specific atomic note—and there are no broader connections to other areas of the knowledge base—the articles can be linked directly within the “juggling as a metaphor in the media” note rather than turned into separate source notes.

The takeaway is a retrieval-focused mindset: create source notes by default when unsure, but skip them when the source will not be consulted again outside a single atomic idea. The key question becomes whether the content will be revisited; if not, a direct link inside the atomic note is sufficient.