Structure Beats Magic
← All concepts
System architecture

The Three-Worlds Split

Content, data and code live in deliberately separate zones.

The Three-Worlds Split
Content, data and code each do one job and stay in their own world. Content is authored; data is derived from it — a queryable view that never owns the source; code produces both. The failure modes along the bottom — a database in the vault, a note in the repo, an import in the content tree — are what mixing the worlds actually costs.

A personal system has three distinct worlds that must not be mixed: content (markdown — the second brain), data (databases — the queryable layer) and code (scripts, repos). Notes aren't a database; databases aren't a repo; code doesn't live inside the content vault. Mixing them is how systems break — a database inside the content vault tanks its performance. Data-architecture discipline applied to a personal system.