Ever hit this wall? You open Obsidian or any PKM app to create a new note, and suddenly you're frozen, second-guessing yourself:
"Which folder should this note live in?"*
"What tag should I add so I can actually find it later?"*
"Or should I just make it a [[ ]] link instead?"*
"And how is that YAML Property block at the top different from a tag?"*
Without a clear filing philosophy, the inevitable result is digital clutter — a tag explosion with hundreds of orphaned labels, folder trees so deep you've forgotten they exist, and notes that drift into the void, never to be found again.
In this article, we're decoding the 4 Pillars of Metadata Architecture in a Second Brain system so you know exactly when to reach for which tool — and how to structure your thinking without the mental spaghetti.
---
### 1. Folders: High-Level Physical Boundaries
A folder in a file system is a physical container. The single most important constraint: a file can live in only one folder at a time.
#### Best Practices:
* Use them for high-level scope only: Folders work best for broad top-level categories — think PARA Method (1_Projects, 2_Areas, 3_Resources, 4_Archives) or system-level functions like Inbox, Templates, Attachments.
* Never nest deeper than two levels: Building a path like Work / 2026 / Content / Blog / PKM is the beginning of a nightmare, because your brain now has to memorize the entire tree structure.
> Rule of Thumb: Think of a Folder as a "main filing cabinet," not a "sub-file organized by topic."
---
### 2. Tags: Status & Activity Dimensions
A Tag (#tag) is a cross-cutting label that spans across folders. A single note can carry as many tags as you need. Tags are ideal for information that shifts over time or moves through a workflow.
#### Best Practices:
* Use them to mark "status" or "activity type": e.g., #status/draft, #status/review, #action/todo, #type/book-note.
* Leverage nested tags: Obsidian supports hierarchical tags like #book/non-fiction or #project/active, which keeps your tag namespace tidy and easy to filter.
What to avoid: Don't use tags to represent concepts* like #Zettelkasten or #ArtificialIntelligence. Tags can't carry their own descriptions or context — they're just floating strings.
> Rule of Thumb: Use a Tag to answer "What state is this note in?" or "What action does it need next?"
---
### 3. Internal Links ([[ ]]): Conceptual Networks
Internal Links (bidirectional links, [[Note Name]]) are the beating heart of any Second Brain or Zettelkasten system. Creating a link is a way of saying: "These two ideas are related — here's how."
#### Best Practices:
* Link concepts, people, tools, or places: e.g., [[Zettelkasten]], [[Tiago Forte]], [[Obsidian Dataview]].
* Create dynamic notes: The moment you link to [[Zettelkasten]], that name becomes a new note you can flesh out — write a definition, build a Map of Content (MOC), or review its backlinks. A tag, by contrast, is just a label with no body.
* Surface connections in Graph View: Every [[ ]] link creates a node in your knowledge graph, revealing connections your brain might never have spotted on its own.
> Rule of Thumb: Use a Link when you want to point to a "concept or core topic that deserves its own page."
---
### 4. Properties (YAML Metadata): Structured Data for Queries
Properties live in the YAML frontmatter at the top of a Markdown file and store data in key-value pairs — like author: Tiago Forte or rating: 5.
#### Best Practices:
* Store structured, predictable data: Perfect for specific note types — book summaries, meeting notes, project briefs — where the fields are always the same.
* Pair them with the Dataview plugin: Once your Properties are consistent, Dataview can pull them into powerful tables and lists, such as:
* A list of every book you finished in 2026, sorted by rating
* All notes created this week, grouped by type
* Example Properties block:
```yaml
---
type: book
title: "Building a Second Brain"
author: "Tiago Forte"
status: read
rating: 5
created: 2026-08-11
---
```
> Rule of Thumb: Use a Property when you need to "query, filter, or compute on this data."
---
### The Decision Matrix
Not sure which format to use for a given piece of information? Use this quick-reference table as your compass:
| Format | Core Purpose | Example Use Case | Decision Question |
|---|---|---|---|
| **Folder** | High-level physical boundary | `Inbox`, `Projects`, `Resources` | Which zone of my vault does this belong to? |
| **Property** | Structured data for queries & computation | `author:`, `date:`, `rating:` | Is this a clear key-value fact? |
| **Tag** | Status & workflow context | `#status/wip`, `#type/article` | What state or process is this note in? |
| **Link (`[[ ]]`)** | Conceptual & topical connection | `[[Second Brain]]`, `[[PARA]]` | Is this a concept or topic that deserves its own note? |
---
### A 3-Step Pre-Note Workflow
To keep your Second Brain tidy without overthinking every single note, run through these three steps before you hit save:
1. Pick the top-level folder: Drop it in Inbox if you're unsure, or file it under a category like Notes.
2. Add Properties & Tags: Set the status — e.g., status: draft — and tag the type, like #type/permanent.
3. Extract key concepts into Links: Skim your content and turn important terms into [[Concept]] links, weaving the note into your existing knowledge network.
A metadata structure that's simple but deliberate cuts down cognitive load on the filing side — freeing up your mental bandwidth for what actually matters: thinking, analyzing, and creating.
---