[[Obsidian]] is purpose-built for personal knowledge work — for [[Personal Knowledge management|personal knowledge management]] the question is not whether it fits but what discipline the user has to bring. ## [[Obsidian]] ![[Obsidian#^definition]] For single-user PKM, Obsidian is purpose-built - the personal-tool DNA that makes it weak for organisational use makes it excellent here. ## [[Personal Knowledge management]] fit For personal knowledge management the relevant requirements are the four baseline axes from [[Knowledge management]] - the three collective-only axes (Securability, Ownership clarity, Agent-readiness for multi-author governance) drop out because the single user is the producer, reviewer, and consumer. ### [[Discoverability]] ![[Knowledge problems#^discoverability]] Strong. Backlinks, graph view, and plugin-extended search ([[Obsidian Dataview]], [[Obsidian Bases]]) make findability first-class. The graph view exposes connections the user did not consciously author; backlinks surface incoming references without anyone curating them. ^discoverability ### [[Maintainability]] ![[Knowledge problems#^maintainability]] Strong. Markdown on disk, git-friendly, plugin ecosystem for automation. Single user means no merge conflicts. Updates cost what the change costs, not what the vault size is. ^maintainability ### [[Connectivity]] ![[Knowledge problems#^connectivity]] Strong. Wikilinks, backlinks, graph view. The connection graph is the medium, not an afterthought. Every relationship is explicit and queryable via Dataview or Bases; the structure of the personal knowledge base is itself first-class data. ^connectivity ### [[Survivability]] ![[Knowledge problems#^survivability]] Strong. Plain Markdown, [[File over app]]. The vault remains readable in any text editor, today and in fifty years. No vendor dependency. ^survivability ## Verdict - [x] [[#Discoverability]] - [x] [[#Maintainability]] - [x] [[#Connectivity]] - [x] [[#Survivability]] ^verdict Adopt for PKM. The four baseline knowledge-management requirements are all met strongly. The real cost is the linking discipline the user has to maintain - but that is the work of personal knowledge management, not a tool deficiency. ^answer The conclusion lives in none of the requirements on its own. Obsidian's design centres the relationship graph and treats the file system as the source of truth - exactly what a single-user, durable, navigable knowledge base needs. The personal-tool DNA that limits its collective use is the same DNA that makes it the natural choice for PKM.