The video explains how to turn raw, fleeting notes into a reliable, scalable knowledge system by creating “atomic” notes—small, self‑contained units written in your own words that are highly composable (they work well together) and loosely coupled (each can be understood on its own). Using a single trusted repository (e.g., Obsidian with only a few tags) and a daily processing routine powered by spaced‑repetition, you review fleeting notes, either act on them immediately, defer them (snooze), or rewrite them into atomic notes that are linked to related ideas via an “up” property and tagged for easy retrieval. These atomic notes form an interlinked, tree‑structured web (the Zettelkasten approach) that can be composed into essays, projects, or other outputs without starting from scratch. The method scales because you only ever review the most urgent notes, and the system’s simplicity—few tags, no folders, clear file names—keeps it manageable as it grows. The presenter demonstrates the workflow in Obsidian, shows how to capture literature and fleeting thoughts, and ties the process to the broader FLAP system for project‑based writing.
1. Tris introduces the video as part of the “no boilerplate” series focusing on fast technical videos.
2. The video addresses the common unanswered question in note‑taking guides: what to do after taking notes.
3. Tris dedicates the video scripts to the public domain; the markdown document with scripts, links and images is freely available on GitHub and namtao.com.
4. The video shows how to forge work such as essays, exam revision, books, or video scripts from atomic notes.
5. Atomic notes are the core unit of the Zettelkasten system, also called smart, main, or permanent notes.
6. Atomic notes form an interlinked web of knowledge where information is digested, deconstructed, and rebuilt in one’s own words.
7. Two principal features of atomic notes are high composability and cohesiveness, and low coupling so each note can be understood without reading many others.
8. Atomic notes are described as compiler artifacts of learning before they are linked into their final form.
9. The analogy is made to software modules: high cohesion and low coupling allow reuse in multiple programs.
10. Outputs like essays are compositions of atomic notes, similar to how a program is a composition of modules.
11. The FLAP system component discussed is taken directly from the Zettelkasten method as presented in Bob Doto’s book *A System for Writing*.
12. Atomic notes are small, self‑contained notes that hold the best understanding of a topic in one’s own words, as simply as possible.
13. A claimed benefit of a mature Zettelkasten system is that you never need to start from scratch because notes are already in your words and can be stacked, glued, and turned into a first draft.
14. The graph illustration of notes does not scale well; with 30‑40 notes the view becomes too crowded to read names.
15. The original Zettelkasten metaphor organizes notes on paper inside a linear card file, browsed by thumbing through cards and flicking titles.
16. Paper Zettelkasten notes include numerical references that create a logical graph, but primary retrieval is done by thumbing through the cards.
17. In Obsidian, Tris uses the Vert Folder plugin to visualize a tree of notes, which he finds preferable to a graph because it can be navigated with a mouse scroll wheel.
18. An example atomic note has a file name detailed enough to remind the user next week and a body detailed enough to remind after a year.
19. The uplink property slots the note next to a closely related note, storing trains of related thought together.
20. Atomic notes are tagged “atomic” for easy searching and filtering, and include a “see also” section linking to related atomic notes.
21. References to literature notes (either in the vault or external links) are included in atomic notes.
22. Uplinks are used for structure; tags indicate note type (atomic, project, etc.); file names serve as human‑readable identities rather than IDs or date stamps.
23. Tris’s system has three parts: capture (notes on lectures, literature, fleeting thoughts), process (write an interlinked network of atomic notes), and write (compose clusters into outlines, essays, etc.).
24. In Obsidian, Tris uses no folders and only four tags: fleeting, literature, atomic, and project.
25. The previous video focused on the capture stage; this video focuses on processing raw notes into atomic notes.
26. The video is sponsored by Let’s Get Rusty; Bogdan runs Rust training with a new cohort each month.
27. The processing goal is to build a daily practice of distilling atomic notes into a single trusted system.
28. The phrase “single trusted system” is borrowed from David Allen’s 2001 book *Getting Things Done*.
29. Two vital components of a fleeting‑note system are: storing notes in a single place, and processing them reliably without missing anything.
30. Multiple storage locations create uncertainty because you cannot be sure you have checked every place.
31. Human eyes can only read one thing at a time, which the brain knows, making multiple places inefficient.
32. During processing, literature and fleeting notes are raw materials that are honed into atomic notes.
33. The process has two main parts: rewriting fleeting notes to atomic notes (keeping original wording as a reference) then tagging them atomic; and linking unfiled literature notes from new atomic notes then retagging them literature for long‑term reference.
34. Processing must be done daily, especially for fleeting notes that may contain urgent tasks.
35. Fleeting notes represent a temporal contract: the “you of yesterday” counts on the “you of today” to fulfill them.
36. Processing every fleeting thought and highlight can become overwhelming.
37. For fleeting notes or highlights that are unclear or irrelevant now, Tris proposes misusing spaced repetition as a solution.
38. Spaced repetition increases retention time with each review, eventually flattening the forgetting curve.
39. Tris uses Stephen Wang’s Obsidian Spaced Repetition plugin for both study aid and managing his fleeting‑note backlog.
40. He offers a compiled Obsidian vault with the setup for Patreon supporters to download and use immediately.
41. Daily processing example: open notes for review using the Spaced Repetition plugin command, select the fleeting tag, and the plugin opens the first due fleeting note (e.g., “ask Mom when she is free for a catch‑up chat”).
42. On the first review, you go through every fleeting note; doing it sooner is better.
43. Each note is reviewed as good, medium, or hard, which corresponds to snoozing for a while, a short time, or tomorrow; subsequent days only review notes previously marked as most important.
44. If a fleeting note is a task that takes less than two minutes, do it immediately, delete the note, and rerun the review command.
45. If the task belongs to a different project (e.g., a shopping list), copy‑paste it into the appropriate note, delete the fleeting note, and rerun the command.
46. When unsure what to do with a fleeting note, snooze it by reviewing it as easy or “to later”; the plugin schedules it for future review.
47. After a review, the plugin adds a due date and two other numbers that track cumulative difficulty/urgency.
48. After several days of this routine, the list shortens to only those notes consistently ranked as hard (urgent).
49. At that point, you can do the tasks, file or research them, or delete them if they no longer make sense.
50. A scalable system is needed to trust that the process will work in the long run.
51. Tasks that must be done later should be added to an existing project or captured in another note by cutting and pasting the fleeting thought into the appropriate note.
52. More advanced project management with due dates is covered in the final video of the series and is already available in the Patreon vault.
53. Capturing what other people have said is important for students, teachers, office workers, and friends who want to help.
54. Notes from lectures, talks, interviews, YouTube videos, and podcasts are scattered and informal.
55. When the speaker’s words are still fresh, it is the time to expand those notes into atomic notes or tasks.
56. An example fleeting thought is “Writer's block is caused by reader's block.”
57. This thought was expanded into an atomic note by putting it in one’s own words, cross‑referencing other notes, and keeping the original capture as a reference.
58. The tag was changed from fleeting to atomic for the expanded note.
59. The Zettelkasten method’s usefulness includes having a definite place to file each note, not in a folder bunch or drifting aimlessly.
60. Each new atomic note is placed directly behind exactly one other note, modeled using the “up” property.
61. In a physical card box, this corresponds to placing note cards one behind another.
62. The single “up” property technique builds a tree of related links that can be explored and visualized more understandably than a graph.
63. Tris demonstrates this tree visualization using the Vert Folder plugin in Obsidian.
64. Another fleeting‑note category is pure knowledge (names, addresses, code blocks, verbatim facts) that only needs verbatim storage.
65. For such notes, create a new note with the information, add sensible tags, and file it safely for later retrieval.
66. Highlights are handled in three ways: written into their own atomic notes, referenced in existing atomic notes, or snoozed for later.
67. An example highlight is from *How to Take Smart Notes* by Sönke Ahrens quoting Niklas Luhmann, whose Zettelkasten contained over 90,000 notes.
68. After highlighting, Tris processed the insight into a new atomic note with the file name as the fully developed learning, referenced the Luhmann quote, browsed related atomic notes via the tree, added two more linked concepts as references, and slotted the note behind a related thought using the up property.
69. The only two organizational features needed in atomic notes are: normal links between related notes, and a parent note linked via the up property.
70. If using a Readwise template or highlights importer that formats highlights as markdown checkboxes, the final step is to check off the checkbox to indicate the highlight has been processed.
71. Once the habit of daily processing is established and loosely coupled but highly cohesive atomic notes are produced, you have everything needed to build novel work of your own.
72. Time‑boxed projects, the subject of the final video, complete the FLAP system.
73. Tris thanks viewers and directs them to his Patreon or Ko‑fi for early ad‑free videos, name in credits, and one‑to‑one mentoring.
74. He promotes his weekly sci‑fi audio fiction podcast *Lost Terminal* and mentions finishing season three of the *Phosphine Catalog*.
75. Transcripts and compiled markdown source code are available on namtao.com and GitHub, with corrections in the pinned errata comment.