Separate reference material (static lookup) from working…

When This Fires

• When designing or reorganizing a personal knowledge management system
• When search results in your notes system return a mix of reference items and half-developed thoughts
• When your notes system feels either too formal for thinking or too messy for retrieval
• Complements Route actionable items to your task system and reference… (actionable vs. reference routing) with the parallel separation for notes

Common Failure Mode

The everything-in-one-app approach: "I'll put all my notes, documents, bookmarks, and project plans in Notion/Obsidian/Evernote." The single system handles reference and working notes identically, producing a soup where tax documents live next to shower thoughts and recipe bookmarks neighbor half-finished essays. Neither retrieval nor development works well in the mixed environment.

The Protocol

(1) Define two distinct spaces: a reference system (optimized for storage and retrieval: good search, stable structure, minimal editing) and a working space (optimized for thinking and development: easy editing, loose structure, supports messy exploration). (2) When capturing information, route it to the correct system based on its nature: static and for future lookup → reference. Evolving and for current thinking → working. (3) The systems can be different apps, different folders within one app, or different sections — the key is that they're mentally and structurally distinct. (4) Periodically, mature working notes may produce stable conclusions that become reference items. Move the finished version to reference; keep the working note in the working space or archive it. (5) Test: when you search for a factual reference, do working note fragments pollute the results? When you browse your working space, do finished reference items make it feel static? If yes, the separation isn't clean enough.