second-brain

Obsidian vault notes are routed by prioritizing reusable wiki knowledge versus vault-wide personal documentation, using deterministic folder and globally-unique filename conventions based on the note's content type. This prevents misrouted notes before any vault operations happen.

Personal knowledge management notes are organized using deterministic routing rules that separate quick note inboxes, daily-scoped notes, and personal entries like travel or admin logs into consistent markdown folders. This structure ensures long-term retention and easy retrieval.

Yes, vault organization dynamically routes content unit types such as profiles, cases, references, and raw sources. It applies episode-style grouping and specific filename and date conventions to ensure each unit reaches its correct long-term destination.

No, personal documentation routing explicitly excludes project-notes requests. Project-scoped notes are deferred to a separate project-notes skill to maintain clear boundaries between personal knowledge and project-owned documentation.

Searching the vault before choosing a destination is a safety-first convention to prevent duplicate notes and respect existing nearby folder structures. It ensures new markdown notes follow established patterns rather than creating isolated or misrouted files.