Front Matter Is the Schema of Your Knowledge Base

Sun, 19 Apr 2026 00:00:00 +0000

Front Matter Is the Schema of Your Knowledge Base

There is a Dataview query I run at least once a week:

TABLE date, author, genre
FROM "30-books"
WHERE contains(tags, "non-fiction") AND status = "finished"
SORT date DESC

It gives me a table of every non-fiction book I have finished, when I completed it, and who wrote it — in about 200 milliseconds. When I want to find what I read on a specific topic, I do not dig through folders or search my memory. I run the query.

That query only works because every note in that folder has structured front matter. Without it, Dataview has nothing to read, and the query returns zero results. I would be back to scrolling through files, reading titles, hoping I named things consistently.

That is not a trivial difference. It is the difference between a note-taking app and a knowledge base.

The Unstructured Vault Problem

Most people start Obsidian the same way: create a folder structure, drop notes in, link a few things. It feels organized at first. Folders give the illusion of structure.

The problem is that folders are physical storage, not logical structure. A note about a book you finished sits in 47-books/. That tells you where the file lives. It tells you nothing about when you read it, whether you finished it, who wrote it, what genre it is, or whether it connects to three other books you read on the same topic in a different folder.

Worse, that knowledge is invisible to anything that tries to read your vault programmatically. Dataview cannot query it. A PAI skill cannot filter for it. An AI context loader cannot select it by relevance. The information exists, but it is locked inside prose — retrievable only by a human reading the file.

When your vault grows past a few hundred notes, that model collapses.

What Front Matter Actually Is

Front matter is a YAML block at the top of a markdown file, delimited by triple dashes. It holds structured key-value pairs that describe the note — not the content itself, but metadata about it.

It is not magic and it is not complicated. It is a schema.

A minimal front matter block for a knowledge base note might look like this:

---
title: "Thinking, Fast and Slow"
date: 2026-03-12
tags:
  - non-fiction
  - psychology
  - behavioral-economics
status: finished
author: Daniel Kahneman
rating: 5
---

Three fields do most of the work: tags (what domain and type is this), date (when), and a status or type field (where in its lifecycle). Everything else is optional until a specific query demands it.

What It Unlocks

Dataview queries. Once your notes have consistent front matter, Dataview turns your vault into a queryable database. You can build a live table of unresolved issues, a list of certification notes by module, a filtered view of blog drafts not yet published. The query language is simple. The payoff is immediate.

Cross-domain filtering. My vault spans four domains: career notes, AI governance certification notes, PAI infrastructure documentation, and blog post drafts. Without front matter, navigating across those domains means folder-hopping. With front matter, I can query across all four simultaneously — surface everything tagged behavioral-economics regardless of where it lives, or find all notes with status: in-progress across every section at once. The folder structure stays for physical organization. Front matter handles the logical layer.

AI context loading. This is the one that changed how I think about it. PAI does not load my entire vault into context when I ask a question about something I have read. It loads notes that match specific criteria: the right tags, the right domain, the right status. That selection mechanism is front matter. Without structured metadata, the system gets everything or nothing. With it, loading can be precise.

Before and After: The Same Note

Without front matter:

# Thinking, Fast and Slow

Really good book. Kahneman breaks down how we make decisions — System 1
is fast and intuitive, System 2 is slow and deliberate. The section on
cognitive biases was the most useful part. Finished it in March. Would
recommend to anyone interested in decision-making or behavioral economics.

This is a fine note. It has the information. But Dataview cannot surface it in a query. PAI cannot identify it as a finished book on behavioral economics. Six months from now, I will not remember I wrote it unless I happen to search the right words.

With front matter:

---
title: "Thinking, Fast and Slow"
date: 2026-03-12
tags:
  - non-fiction
  - psychology
  - behavioral-economics
  - decision-making
status: finished
author: Daniel Kahneman
rating: 5
---

Now the note is queryable. PAI surfaces it automatically when I ask about books on decision-making. Dataview includes it in my Q1 reading table. I can filter for all five-star books across my entire reading folder. The content of the note is identical — only the schema changed.

The Architecture Argument

A relational database without a schema is just a collection of text files. An Obsidian vault without front matter is nearly the same thing — a sophisticated folder system with backlinks and a graph view, but still fundamentally unqueryable by anything that needs to select notes by attribute.

Front matter gives your vault a schema. Folders give it a physical address. You need both, but the schema is what makes a vault a knowledge base. Without it, you are building a library where every book is correctly shelved but nothing has a catalog entry. Finding anything specific means walking the stacks and reading spines.

Where to Start

Do not design an elaborate front matter schema before you have written a hundred notes. That is premature optimization and it will not survive contact with actual usage.

Start with three fields: tags, date, and status. Add type if your notes serve different purposes (reference, log, draft, fix-doc). Add domain-specific fields only when a query demands them.

The schema should be pulled from how you actually search, not pushed from how you think you might want to search someday. Write the notes, run queries against three fields, and let the gaps tell you what to add next. The vault teaches you what it needs — if you have given it enough structure to communicate.

Note-Taking on

Front Matter Is the Schema of Your Knowledge Base

Front Matter Is the Schema of Your Knowledge Base

The Unstructured Vault Problem

What Front Matter Actually Is

What It Unlocks

Before and After: The Same Note

The Architecture Argument

Where to Start