Get AI summaries of any video or article — Sign up free
Knowledge Vault – Notion Knowledge Management System (Life OS) thumbnail

Knowledge Vault – Notion Knowledge Management System (Life OS)

August Bradley·
5 min read

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

TL;DR

The knowledge lab turns collected inputs into topic-based workspaces that become more actionable over time.

Briefing

A “knowledge lab” inside Notion is positioned as the missing layer between collecting information and turning it into usable insight. Instead of storing books, media, training, and raw notes as separate silos, the system organizes knowledge by topic—then links that topic to notes, projects, habits, and even planned content—so ideas resurface exactly when they’re needed. The payoff is “emergence”: insights that appear to be more than the sum of individual inputs because the relationships inside the system create new, actionable understanding over time.

The core distinction is that a knowledge lab isn’t defined by source type (book vs. podcast vs. personal note). It’s defined by topic category—examples include community building, course creation, design thinking, discipline, divergent/convergent thinking, fitness goal setting, home creation, metacognition, product design, professional networks, sales, SaaS development, systems thinking, team building, and travel hacks/time management/workflow. Each topic becomes a workspace where research is aggregated and shaped into something digestible: a structured page with a table of contents, headings, diagrams, quotes, and highlighted “gems” pulled from multiple upstream vaults.

To make this knowledge actually usable, the lab relies on relational links across databases. Topic pages link to relevant notes and ideas from the notes-and-ideas database, and projects link back to the topics that matter. If someone is building a membership community, the project workspace connects one step away to the “community building” topic page—so the project immediately gains access to extensively researched material. The same mechanism can connect topics to habits/routines and to content pipelines (for example, newsletter drafts drawing heavily from a “design thinking” topic). The system also supports active vs. archived states, encouraging users to keep older material without deleting it.

A key mechanism is contextual resurfacing. Notes and ideas are captured as small, narrowly defined nuggets and tagged to one or more knowledge lab topics. When the user later opens a specific topic—say “systems thinking”—only the notes linked to that topic appear, sorted by last edited so the most recent insights come first. This is contrasted with arbitrary time-based reminders (like “bubble back up after 90 days”), which often miss the moment when the information is actually needed.

The lab’s workflow is designed for rapid growth: users can drag notes out of the notes database into the topic workspace (or copy them while preserving the original), convert them into text if desired, and embed them without breaking their connections. Templates further automate setup: a “new topic template” uses a self-referencing filter so newly created topic entries automatically pull in the right notes, and it auto-generates a table of contents using markdown-style headings.

Finally, the system is framed as a “brain extension,” not a second brain. The goal isn’t duplicating human thinking, but enhancing what brains struggle with—remembering and holding information in the right context. By interconnecting databases through relational links and self-filtering resurfacing, the knowledge lab turns scattered inputs into a living, navigable repository that supports execution across work, learning, and personal growth.

Cornell Notes

The knowledge lab in Notion is built to convert scattered inputs—books, media, training, and raw notes—into topic-based workspaces that become increasingly useful over time. Instead of organizing by source type, it organizes by topic category (e.g., design thinking, systems thinking, discipline) and aggregates the best insights into structured pages with tables of contents, headings, diagrams, and highlighted takeaways. Notes and ideas are captured as small, narrowly defined nuggets and tagged to one or more knowledge lab topics, then resurface contextually when the user opens that topic. This “emergence” comes from relational links between notes, topics, and projects, so ideas appear at the right moment for execution rather than at arbitrary dates. Templates and self-referencing filters automate setup and keep the system scalable.

Why does organizing knowledge by topic (rather than by source type) matter in this system?

The knowledge lab treats each entry as a topic workspace—like “community building” or “design thinking”—so the page becomes a single home for everything relevant to that subject. Source-specific vaults (books, media, training, personal notes) feed into the topic, but the topic page itself is defined by what the user wants to understand or do. That structure makes it easier to aggregate insights across many inputs and then reuse them in projects, content, and learning without hunting through separate silos.

How does contextual resurfacing work, and what problem does it solve?

Notes and ideas are tagged to knowledge lab topics (for example, a note tagged to “systems thinking”). When the user opens the “systems thinking” topic, only the linked notes appear—filtered by relational links between the notes-and-ideas database and the knowledge lab. Sorting by last edited helps prioritize the newest insights. This avoids time-based resurfacing (like “after 90 days”), which often returns information at the wrong moment; contextual resurfacing returns it when the user is actively working on that topic.

What does “emergence” mean here, and where does it come from?

Emergence refers to outcomes that are greater than the sum of individual parts due to dynamic interaction inside the system. Rather than simply “mashing” inputs together, the knowledge lab creates new value through relationships: topic pages link to related notes, projects link to relevant topics, and content can draw from topic research. Those connections let insights combine gradually into bigger, more actionable ideas.

How do projects benefit from the knowledge lab’s linking structure?

Projects connect to knowledge lab topics so execution starts with the right research. For instance, a project to hire a video editor might link to “team building,” giving immediate access to the topic’s organized research. The system can also support multi-topic projects, where a single project workspace pulls in several knowledge lab topics relevant to the work.

What role do templates and markdown-based table of contents play in scaling the system?

A “new topic template” uses a self-referencing filter tied to the knowledge lab so newly created topic entries automatically pull in the notes tagged to that topic. The template also auto-creates a table of contents using markdown-style headings (H1/H2/H3 via pound signs). As headings change, the table of contents updates automatically, keeping each topic workspace navigable as it grows.

How can a user move from raw notes to a developed topic page without losing connections?

If a note is only linked to one topic, it can be dragged into the topic workspace to become part of the developed page. The system also supports copying while preserving the original connection: holding Alt and dragging creates a copy, so the note remains linked to other topics it was already tagged to. Users can then convert the embedded note into text or keep it as a subpage, depending on how they want to structure the knowledge.

Review Questions

  1. How does the system ensure that notes resurface based on context rather than arbitrary time delays?
  2. Describe how relational links connect notes, knowledge lab topics, and projects. What does a project gain from those links?
  3. What design choices (topic-based organization, table of contents, highlighting, templates) help a knowledge lab page stay usable as it grows?

Key Points

  1. 1

    The knowledge lab turns collected inputs into topic-based workspaces that become more actionable over time.

  2. 2

    Organizing by topic (not by source type) creates a single place to aggregate insights across books, media, training, and personal notes.

  3. 3

    Relational links connect notes-and-ideas to knowledge lab topics and connect projects to the topics they need for execution.

  4. 4

    Contextual resurfacing filters notes to the exact topic being worked on, avoiding unreliable time-based reminders.

  5. 5

    Notes are captured as small, narrowly defined nuggets so they can be linked to multiple topics and reused efficiently.

  6. 6

    Templates with self-referencing filters and auto-generated tables of contents make new topic pages scalable and consistent.

  7. 7

    Dragging or copying notes into topic pages lets users develop ideas while preserving connections across the system.

Highlights

The knowledge lab is framed as a “brain extension”: it doesn’t replace human thinking, but improves remembering and retrieval by surfacing ideas in the right context.
“Emergence” comes from dynamic interactions inside the system—especially relational links between notes, topics, and projects—rather than from simply combining inputs.
Contextual resurfacing is presented as the key advantage: notes return when a user opens the relevant topic, not after an arbitrary number of days.
Topic pages are built to be skimmable and reusable, using tables of contents, headings, diagrams, quotes, and color-based highlighting of the most valuable takeaways.
Templates automate the setup of new topic workspaces, including self-filtering and table-of-contents generation via markdown headings.

Topics

Mentioned