The recipe, free. Each piece takes one real, working system and shows the method behind it — so you can build your own. Newest first.
Sync brings the data to you. Sometimes you need the opposite — to reach the machine where the data already lives, without opening a single port to the internet.
Structure Beats MagicA named idea is a coat rack. Give someone the rack in two minutes and every example afterwards has somewhere to hang — without it, each new detail lands on the floor.
Structure Beats MagicA binary file can't be searched, can't be queried, and can't hold a single link. Put a markdown note beside it and all three problems go away at once.
For builders & teamsSyncthing replicates, Restic protects, Git remembers. Ask one of them to do another's job and it will fail you politely, at the worst possible moment.
For knowledge workersI turned a shoebox of old drives into a database — every file fingerprinted, deduplication reduced to a single SQL query. It worked better than I expected, right up to the moment it confidently told me two identical photos were different. That's where the interesting part starts: knowing exactly what your certainty is blind to.
For knowledge workersHalf your rules are wishes you're hoping the machine remembers. The other half run whether it remembers or not. The gap between them is the whole game.
For knowledge workersA shoebox of old hard drives is a dread task everyone postpones: what's on them, what's worth keeping, what's safe to destroy? I stopped clearing them one at a time and built a small system instead — an index that makes each drive cheaper than the last, and a gate that never lets me delete before the data is safe. Structure beats effort, even here.
Structure Beats MagicContracts, subscriptions, family arrangements, the promise you made yourself about the gym — model them as one entity, link the evidence, and an expensive class of silent drift becomes a query.
For builders & teamsThe files are canonical. The database is a rebuildable projection of them. Get that one arrow the right way round and everything downstream — queries, AI, sync — becomes trustworthy. Get it backwards and your data quietly rots.
For knowledge workersEveryone sells you data and AI. The pair is unstable on its own. The thing that makes it trustworthy is the word nobody puts on the slide: rules.
Structure Beats MagicAsk an AI to review your own material and it hands back something flattering. Point a second one at it with orders to attack, and you find what the first was too polite to mention.
For knowledge workersYour reading history is already a dataset. Stop treating it as a queue and it will tell you what you think.
For knowledge workersEveryone's tuning prompts. The work isn't in the prompt. It's in whether the thing you point the AI at is structured enough for it to act, not just answer.
Structure Beats MagicGoogle Cloud's Open Knowledge Format turns your data's context into a folder of markdown files with frontmatter — the exact architecture I built for my own knowledge. It's the right shape. But its relationships are untyped, and untyped is where a knowledge graph quietly stops being trustworthy. The missing layer has a name: rules.
Structure Beats MagicA folder of markdown files doesn't hold a model of my knowledge. It is the model — atomic, self-describing, open, queryable. After 25 years of data modeling, I finally built one for myself, and it works exactly like the enterprise kind.
Structure Beats MagicStructure Beats Magic is usually about the invisible half — the model under your knowledge. But structure only pays off when someone can see it. Visual thinking isn't decoration on top of a data model; it's the other half of the same craft.
For knowledge workersThe most valuable facts about your life are the ones you never wrote down — they're inferred. And you don't need an ontology, a triple-store, or RDF to get them. You need structure and a handful of rules. This is what reasoning actually looks like on your own data.
For knowledge workersObsidian or Notion is the wrong question. The right one is: which layer is this? One holds your knowledge in plain files you own; the other is a lovely place to look at it. Confuse the source with the interface and you've handed away the thing your whole system depends on.
Structure Beats MagicI've spent a career doing one thing under many names: taking something complex and giving it a structure everyone can see. I'm widening where I write about it — here's how, and the sabbatical behind it.
For knowledge workersSeven hundred scattered articles don't become a knowledge engine by accident. They become one because you build the machine — and the machine is the proof.
For knowledge workersIf you tell people structure beats magic, your own operation has to be built that way — or the message is hollow. The foundation is the case study.
For knowledge workersZettelkasten, arrived at its conclusion: when your knowledge is stored as reusable units, one body of work becomes an article, a course, and a talk — without ever rebuilding it.
For knowledge workersThe PKM crowd declared folders dead. My whole system runs on them — because folders and links aren't two teams, they're two altitudes. And the folder-note reconciles them.
For knowledge workersStructure and deliberate get the credit. But essence is the drive underneath both — the thing that decides what deserves structure and what's worth choosing at all.
For knowledge workersOne principle runs my whole content system: every article, image, concept, and review is an atomic folder that carries everything about itself — and the database is just a queryable view of it.
For knowledge workersA refused refund, a broken tap, a subscription that came back from the dead. The vault doesn't stop things going wrong — it stops them getting lost, and it learns from each one.
For knowledge workersPlanning ahead, closing the day, and reading back what actually happened — three moves an AI can run for you, but only if the structure underneath is real.
For knowledge workersA knowledge worker and a billion-dollar company reach for the same move: don't bolt AI onto what you have — rebuild around clean blocks an intelligence layer can compose.
For knowledge workersPublishing your method for free doesn't give away the business — it is the business. The recipe is the ad; the kitchen is the work.
For knowledge workersMy site argues that structure beats magic. Then it published AI images with gibberish text and the wrong brand colour — magic, unchecked. The fix wasn't a better generator. It was a gate.
For knowledge workersStop thinking of your notes as a filing cabinet. Think of them as neurons — small, single-purpose, wired together. Once you do, everything about how to build a second brain falls into place.
For knowledge workersThe name is a claim: a clear system beats a lucky flash of genius — in writing, in music, and most of all in what you get out of an AI.
For builders & teamsI built a trip planner for me and my sister: interests in, anti-interests out, a plan ranked by what we actually like, filtering the 642 places we've already been. It ran two real trips — 8 days in Sicily, 18 in the Verdon. Then it hit me that this is somebody's job — and most people do it in their head, badly.
For builders & teamsEvery time you open a fresh chat and re-explain how you like things done, you're paying the same tax twice. I stopped — by turning the explanations into skills. I now have 82 of them, and they're the reason the AI gets more useful every month instead of resetting to zero.
For knowledge workersA structured life is queryable — but a query is a list, and a list doesn't make you feel anything. The moment I asked Claude to draw my timeline instead of listing it, the structure I'd been building for years suddenly became something I could see. Here's how to turn a well-shaped vault into a picture.
For builders & teamsBy now you know what a skill is and how to build one. But a skill is one option among four, and reaching for the wrong one is how people either overbuild a one-off or underbuild something they'll repeat forever. Here's how I actually decide.
For knowledge workersWhen your vault is small, you search. When it's large, search starts failing you — and it fails the AI too. The fix is older than search: a map. A hand-made Map of Content isn't just navigation for humans. It turns out to be the single best thing you can hand an AI to make it find the right notes instead of guessing.
For knowledge workersA daily note that you have to fill in by hand is a chore you'll abandon by February. So I stopped filling mine in. Twenty-odd data sources — mail, calendar, banking, location, photos, reading, health — write it for me. Here's the actual machinery, not the pitch.
For builders & teamsEveryone tags their notes. I assumed it made my AI assistant faster at finding things. Then I actually measured it across ~17,000 files — and found that for the AI, the tags were mostly doing nothing the structure wasn't already doing.
For builders & teamsSkills are the unit that compounds — so this is the part where I hand you the recipe: the actual anatomy of a working skill, so you can build one today. I'll show you a real one from my own system, line by line.
For knowledge workersYou've had thousands of conversations with AI. They're sitting in an export file you'll never open. I take the messiest pile I own — 2,799 ChatGPT conversations and every Claude thread — and route them onto my calendar so they stop being a graveyard and start being a timeline that summarizes itself.
For knowledge workersI turned 155,000 photos into a queryable, geo-indexed library. The work wasn't taking pictures. It was reading the metadata I already had.
For knowledge workersI turned 271 books I own into 13.8 million words of queryable text. The work wasn't reading. It was extraction.
For knowledge workersI read 120 'AI tips' infographics so you don't have to. The good ones all say the same thing — and it isn't a prompt trick.
For builders & teamsOne source of truth in a database, a website derived from it at build time. No CMS, no runtime database, no drift.
For knowledge workersManual Zettelkasten died of one disease — labor. The AI age cures exactly that disease, if you keep the one job only you can do.
For knowledge workersThe personal companion to the anti-interests system: the same list of noes, but about you — identity by subtraction, and the focus on the other side. The via negativa of attention.
For knowledge workersThe two biggest names in PKM both bet on AI in 2026 — in opposite directions. Both are half right. The missing word is the same one missing from every 'data + AI' pitch.
For knowledge workersThe systems piece: give your AI a veto list — the 'NOT' clause every personalization pipeline is missing. (Its companion, What You're Not Is Also Who You Are, is about what that list does to you.)
For builders & teamsAn agent with access to your whole machine is a power tool with no guard. Here's how I put the guard back — permissions, an SSRF you didn't know you had, and one rule that keeps the guard from becoming the problem.
For builders & teamsEvery app has a 'Download your data' button buried in settings. Most people press it once and forget. Here's the dropzone-and-routing pipeline that turns it into a routine your notes consume.
For builders & teamsPhone photos in, vault views out, a folder shared with family — three different sync-flows, one tool, and folder-type as the security boundary.
For builders & teamsEncrypted at the client, deduplicated, EU-resident, about €60 a year. But the setup isn't the point — the restore-test is. Backup is a habit, not a hope.
For knowledge workersYour master vault is for you. Your phone, your family, and eventually your readers each need a different view. Stop syncing it — start publishing it.
For builders & teamsYour watch collects excellent data and shows it badly. Export it once, land it in a local database you own, and the questions the vendor app can't answer become one line of SQL.
For knowledge workersYour photo library is organized for finding. Your daily-notes are where remembering happens. Join them on the one key they already share — the date — and the daily-note becomes a memory-page.
For knowledge workersMost daily-note systems treat the daily-note as the container. I treat it as an index — and put the day's captures in sibling files.
For knowledge workersEverything built into a vault to serve a human — self-describing folders, explicit links, per-type schemas — turns out to be exactly what makes it legible to a machine. You do not build an AI-ready vault; you build a well-structured one.
For knowledge workersMy daily-note isn't typed from a blank page — it's enriched. Two dozen sources pour the day's facts in every morning, and I add only what a machine can't see.