Get AI summaries of any video or article — Sign up free
How To Build Your Entire Second Brain System In 2026 (With Templates) thumbnail

How To Build Your Entire Second Brain System In 2026 (With Templates)

Noah Vincent·
6 min read

Based on Noah Vincent's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use an action/purpose folder architecture (Inbox, Projects, Areas, Resources, Archive, Galaxy) instead of topic-only folders to avoid digital junk drawers.

Briefing

A second brain only becomes useful when it turns constant consumption into connected knowledge and repeatable output. The system laid out here targets the common failure mode: people read, highlight, and save—then forget—because there’s no workflow that converts raw inputs into retrievable ideas and publishable content. The proposed fix is a purpose-driven “external brain” built from apps, folders, and processes that capture what’s learned, organize it by action, connect it into a knowledge layer, and then reuse it to create content.

The foundation starts with folder architecture built around what information is for, not what it’s about. Instead of topic folders like “Self-Improvement” that become giant, meaningless buckets, the framework uses an EARG-style six-layer structure: Inbox (a temporary brain-dump that gets processed to zero regularly), Projects (time-bound outcomes with deadlines), Areas (ongoing responsibilities like health or finances), Resources (reference material that supports current projects and future needs), Archive (completed or inactive items kept for future reference), and Galaxy (the knowledge layer where permanent notes live in a flat structure). The Galaxy is intentionally hierarchical-free to encourage serendipity—unexpected connections—while the upper folders manage active work.

A key design principle is combining top-down and bottom-up organization. Top-down structure (Inbox/Projects/Areas/Resources/Archive) keeps active documents manageable, while bottom-up organization inside Galaxy relies on nodes, tags, and links rather than rigid folder hierarchies. The result is a system where knowledge can grow organically: new notes become connected pieces rather than isolated files.

For capturing inputs, the content acquisition system prioritizes quality and intentionality over volume. It uses a content hierarchy—books at the top (dense, timeless signal), then articles/newsletters, then YouTube/podcasts for nuance and storytelling, and finally tweets/social posts as low-signal inspiration. Highlights aren’t treated as learning by themselves; saving and highlighting are only the first step. A tool pipeline routes everything into Readwise as a central sync layer: Reader by Readwise for articles/newsletters, Snips for podcast clipping with auto-transcription, and Kindle for book highlights. Tana is positioned as a fast mobile capture layer for quick “content IDs” and thoughts.

The second brain’s note-taking method follows the Zettelkasten workflow with three note types: splitting notes (raw captures and highlights that feed later work), literature notes (summaries in the user’s own words that extract main arguments and add commentary), and permanent notes (one concept per note). Atomicity is treated as non-negotiable: a single permanent note equals one concept, not a broad category like “Productivity.” Value comes from connections—nodes linked to multiple other nodes are more useful than isolated ones. Retrieval is supported through tags and links (e.g., Obsidian-style double brackets), and when clusters grow large, Map of Content (MOC) notes act as navigable indexes.

Finally, the system turns notes into content without starting from a blank page. Content IDs captured in Tana can be converted into tweets, newsletters, YouTube scripts, or long-form articles using templates or AI-assisted drafting (including voice-note transcription and prompt-based structuring). The full loop runs from reading and highlighting → literature notes → permanent nodes in Galaxy → content outputs, enabling “one idea, multiple formats.”

For implementation, two app options are recommended: Obsidian and Eden (formerly Cortex). Both support Markdown for portability and AI-friendliness. Obsidian is framed as powerful but more technical (plugins, configuration, terminal use for advanced automation), while Eden is positioned as an all-in-one workspace with native AI integration and agentic features designed for simpler onboarding. Templates, SOPs, and AI-guided help are offered via Noah’s ArcBank, with pre-built imports for both Obsidian and Eden.

Cornell Notes

The core idea is to build a second brain that converts information intake into connected knowledge and repeatable content. The system starts with an EARG folder architecture: Inbox (temporary capture), Projects (time-bound outcomes), Areas (ongoing responsibilities), Resources (supporting references), Archive (inactive items), and Galaxy (a flat knowledge layer for permanent notes). Learning inputs are captured through a quality-first pipeline (books/articles/podcasts/social) and synced into Readwise, then transformed using Zettelkasten-style notes: splitting notes → literature notes → permanent notes. Permanent notes follow atomicity (one concept per note) and become valuable through links, tags, and MOCs that create navigable clusters. Content is produced by turning content IDs and connected notes into tweets, newsletters, and scripts using templates or AI-assisted drafting.

Why does organizing by topic often fail, and what replaces it here?

Topic folders like “Self-Development” tend to become giant catch-alls that contain everything and nothing. The replacement is a purpose/action structure (EARG): Inbox for unsorted capture, Projects for time-bound outcomes with clear completion criteria, Areas for ongoing responsibilities without end dates, Resources for reference material that supports current projects and future needs, Archive for completed/inactive items, and Galaxy as the knowledge layer for permanent notes. This keeps active work tidy while letting knowledge grow through connections in Galaxy.

What does “bottom-up” mean inside the Galaxy folder, and why is it useful?

Bottom-up organization means capturing ideas as nodes first and letting structure emerge through tags and links rather than pre-built folder hierarchies. Galaxy holds permanent notes in a flat file structure with no hierarchy to promote serendipity—unexpected connections. In Obsidian, a filter can surface only Galaxy notes and show their connections, making the network of ideas the organizing principle rather than the folder tree.

How does the content acquisition system reduce “highlighting without learning”?

It treats highlights as raw material, not knowledge. The system emphasizes consuming less but better using a content hierarchy: books (highest signal), then articles/newsletters, then YouTube/podcasts for nuance, and tweets/social posts as low-signal inspiration. Tools route inputs into Readwise as a central sync layer: Reader by Readwise for articles/newsletters, Snips for podcast clipping with auto-transcription, and Kindle for book highlights. The goal is to extract key ideas that later become literature and permanent notes.

What are the three Zettelkasten note types, and what job does each one do?

Splitting notes are raw captures and highlights (quotes, interpretations, or key excerpts) that exist mainly to feed later work. Literature notes convert those highlights into the user’s own words by summarizing the main argument, what was learned, and adding commentary and reactions. Permanent notes then extract single concepts from literature notes—one note per concept—so they can be linked, reused, and evolved independently.

Why is atomicity (“one concept per permanent note”) treated as a rule?

Atomicity prevents broad, non-actionable notes like “Productivity” that bundle multiple ideas. Instead, the system splits such content into multiple permanent notes (e.g., separate concepts like “Why we finished should be conserved” and other distinct ideas), then connects them. This makes notes easier to connect, reuse, and evolve, and it supports the system’s main value: compound knowledge through links.

How does the system turn notes into multiple content formats?

Content IDs captured in Tana can be converted into outputs using templates or AI-assisted drafting. The loop is: read and highlight key ideas → create literature notes → write permanent nodes in Galaxy → reuse those nodes to produce tweets, newsletters, YouTube videos/scripts, or long-form articles. The claim is leverage: one idea can become several pieces of content rather than a single post.

Review Questions

  1. What are the six EARG layers, and what distinguishes Galaxy from the other folders?
  2. How do splitting notes, literature notes, and permanent notes differ in purpose and structure?
  3. What does atomicity mean in this system, and how do links and MOCs increase retrieval and usefulness?

Key Points

  1. 1

    Use an action/purpose folder architecture (Inbox, Projects, Areas, Resources, Archive, Galaxy) instead of topic-only folders to avoid digital junk drawers.

  2. 2

    Process the Inbox to zero regularly; it’s a temporary holding zone, not a storage system.

  3. 3

    Capture inputs with a quality-first content hierarchy and route highlights into Readwise as a central sync layer (Reader by Readwise, Snips, Kindle).

  4. 4

    Transform highlights into knowledge using Zettelkasten-style notes: splitting notes → literature notes → permanent notes.

  5. 5

    Enforce atomicity: one permanent note equals one concept, then build value through links, tags, and Map of Content (MOC) indexes.

  6. 6

    Produce content by converting content IDs and connected notes into tweets, newsletters, and scripts using templates or AI-assisted drafting.

  7. 7

    Choose an app based on tradeoffs: Obsidian for maximum control (Markdown + plugins + technical setup) or Eden for an all-in-one AI workspace with simpler onboarding; both support Markdown for portability.

Highlights

Galaxy is a flat knowledge layer designed for serendipity: permanent notes live side-by-side to encourage unexpected connections.
Atomicity is the linchpin: one permanent note equals one concept, preventing vague “category” notes that can’t be meaningfully linked.
Readwise acts as the central sync layer so highlights from Reader by Readwise, Snips, and Kindle flow into one place for later transformation.
MOCs function as navigational indexes that map a territory of related notes without summarizing them.
Content creation is treated as a reuse pipeline: one captured idea can become multiple formats (tweet, newsletter, YouTube script, long-form article).

Topics

  • Second Brain System
  • EARG Folder Architecture
  • Zettelkasten Notes
  • Content Acquisition Pipeline
  • Content Creation Workflow

Mentioned