Keep raw inbox captures out of AI retrieval scope
Index only processed permanent notes in AI-searchable systems while keeping unprocessed inbox captures outside retrieval scope, because AI systems cannot distinguish epistemic status and will retrieve raw captures with equal confidence to verified knowledge.
When This Fires
- Setting up semantic search or AI copilot features in your knowledge tool (Obsidian, Notion, custom RAG)
- Deciding which folders or tags to include in your embedding index
- Noticing AI retrieving half-baked thoughts as if they were established knowledge
- Building any system where AI draws from your personal notes to generate responses
Common Failure Mode
Indexing your entire vault "for completeness." You get better recall (more results) at the cost of catastrophic precision (most results are garbage). A quick inbox capture like "maybe X causes Y??" gets retrieved alongside your refined analysis of the same topic, and the AI synthesizes them as if they carry equal weight. The exploratory doubt and the verified conclusion merge into confidently wrong output.
The Protocol
Create an explicit boundary in your knowledge system: an "indexed" zone (permanent notes only) and an "unindexed" zone (inbox, drafts, captures). Configure your AI search to include only the indexed zone. A note crosses the boundary only after you've processed it: rewritten in your own words, connected to at least one existing note, and marked as a permanent addition.