Context belongs with the atom

The idea

An atomic note should carry enough context to be understood without its original source.

Go open a note you wrote six months ago. Not a polished document — a quick capture, a highlight, a stray idea you jotted during a meeting or after reading something that felt important. Read it cold.

Odds are you cannot tell what it means. You see the words. You might even recognize the topic. But you cannot reconstruct why you wrote it, what you planned to do with it, or how it connects to anything else you know. The note is technically present in your system. It is functionally dead.

An example

You highlight a sentence from a book: 'The map is not the territory.' Six months later you find it in your notes. Which map? Which territory? Was Korzybski talking about semantics, was it Bateson on epistemology, or was it your team lead quoting it in a meeting about architecture diagrams? The sentence is identical in all three cases. Without context, it is a fortune cookie. With context — source, date, why it mattered to you, what you were thinking when you captured it — it is a usable building block.

Where it goes wrong

Treating context as overhead rather than structure. You tell yourself you will 'remember what this means' or 'add context later.' You never do. Three months later, you have got a graveyard of orphaned fragments — technically captured, practically useless. The failure is not that you took bad notes. It is that you took contextless notes and mistook storage for understanding.

Make it stick

For the next week, every time you capture a note, add three metadata fields before you move on: (1) Source — where this came from, (2) Spark — why it mattered to you in the moment, (3) Connection — one other idea it relates to. This takes 30 seconds. It is the difference between a note that compounds and a note that rots.