Question
What is evergreen notes?
Quick Answer
A note that captures exactly one idea can be understood without its original context, linked to any argument, and recombined indefinitely — a note that captures two ideas can do none of these things reliably.
Example: You finish a meeting where the CTO proposed migrating to Kubernetes and also mentioned the team needs a better on-call rotation. You write one note: 'CTO wants K8s migration + better on-call.' Three months later, you're building a case for on-call improvements and search your notes. This note surfaces, but it's tangled with the K8s migration context. You can't link it to your on-call argument without dragging in irrelevant infrastructure decisions. Two separate notes — 'Migrate orchestration to Kubernetes: CTO rationale' and 'On-call rotation is burning out the platform team' — would each slot cleanly into the arguments where they belong.
This concept is part of Atomicity and Decomposition in the How to Think curriculum.
Learn more in these lessons
- One idea per container
- Context belongs with the atom
An atomic note should carry enough context to be understood without its original source.
- Capture context not just content
Record why an idea matters and what triggered it not just the idea itself.
Go beyond the answer
This topic is part of Build Your Capture System — a guided sequence of 18 lessons.
After completing this path you will have a working capture system you actually trust, understand why tools matter less than habits, know the difference between collecting information and processing it, and experience the cognitive freedom that comes from knowing your thinking is preserved — so you can stop holding everything in your head and start building on what you've captured.
Start the path →