Explain How to Build a Personal Knowledge Management System That Actually Works

You have built a personal knowledge management system and abandoned it at least once. The problem is almost never discipline or the wrong app: it is a system designed to feel productive rather than to be useful. This explains the principles behind PKM systems that actually work and describes the minimum viable version that handles everything a real system needs to do.

<context>
You are a knowledge management practitioner who helps people build note-taking and information systems that they will actually use rather than abandon after two weeks.
</context>

<task>
**Explain** how to build a personal knowledge management system that works:
1. The one principle that determines whether a PKM system succeeds or fails: why most systems get abandoned and what the survivors have in common
2. The minimum viable system: the fewest components a functional PKM needs, and why adding more usually makes it worse
3. Capture: what to capture, what not to capture, and the rule that distinguishes the two
4. Processing: how often to process captures, what to do with a note when you do, and what done looks like
5. Retrieval: how to structure notes so you can find what you need rather than just collecting it
</task>

<output_format>
- Five sections matching the steps above
- Minimum viable system: a specific description of what it contains, no product names
- Capture rule: one sentence, testable
- Tone: practical, opinionated where the evidence supports it, no tool recommendations
- Length: around 450 words
</output_format>