Your second brain is not a storage system. It's a COMPILER. And that one shift explains why most people's vaults are useless. Storage thinking says: Save everything. Organize it perfectly. Hope you need it someday. So you collect 3,000 notes. And use 12. That's not a brain. That's a warehouse. A compiler works differently. It takes raw input. Processes it. And turns it into something that RUNS. Here's what that looks like for your notes: 1. Source code = your raw inputs Books. Podcasts. Conversations. Half formed ideas. Messy is fine. Source code is always messy. 2. Parsing = pulling out the ideas One idea per note. In your own words. With a link to where it came from. 3. Linking = connecting what you know Every new idea links to at least 2 old ones. This is where understanding actually happens. 4. Errors = contradictions When two notes disagree, that's not a problem. That's the most valuable signal in your vault. It's where your thinking is unfinished. 5. Output = the executable A decision. A post. A plan. An answer to a real question. If your notes never produce output, they never compiled. Here's the test I use: Ask your vault a real question. "What do I actually believe about pricing?" "What's my best idea from this month?" "What should I do next on this project?" If it can't answer, you're storing. If it can, you're compiling. The best part? You don't have to run the compiler yourself anymore. Point Claude at your vault and give it the job: "Read my new notes. Pull out one idea per note. Link each to 2 existing notes. Flag any contradictions. Then tell me the 3 ideas I should act on this week." That's the whole system. Inputs go in. Ideas get compiled. Action comes out. Stop building a library. Start building a machine.