Published text

Structured research records

1. vannevar bush · lineage · 1945 (year)

   Original location · source-fd58a838a7085d7193ed

   Original structured fields

   {
     "contribution": "the memex: 'the human mind does not work that way. it operates by association.' the founding image of knowledge as a trail network.",
     "era": "1945",
     "id": "lin-memex",
     "name": "vannevar bush",
     "sourceIds": [
       "src-as-we-may-think"
     ]
   }

2. doug engelbart · lineage · 1962–1968 (approximate)

   Original location · source-f4f588e9c873fad1deb6 · source-eb0d33cee7f7fb19b938

   Original structured fields

   {
     "contribution": "augmenting human intellect — the 1962 framework that made 'tools for thought' a research program, and the mother of all demos that showed it working in 1968.",
     "era": "1962–1968",
     "id": "lin-engelbart",
     "name": "doug engelbart",
     "sourceIds": [
       "src-i-engelbart-1962",
       "src-i-mother-of-all-demos"
     ]
   }

3. niklas luhmann · lineage · 1950s–1981 (approximate)

   Original location · source-4b1542e40855793231f1 · source-8a2ea6fce927a268320c

   Original structured fields

   {
     "contribution": "the slip-box as communication partner — ~90,000 cards behind ~70 books; the method every linked-notes tool claims descent from.",
     "era": "1950s–1981",
     "id": "lin-luhmann",
     "name": "niklas luhmann",
     "sourceIds": [
       "src-wikipedia-zettelkasten",
       "src-i-luhmann-slip-boxes"
     ]
   }

4. ted nelson · lineage · 1960– (approximate)

   Original location · source-feb479740f103c184a1c

   Original structured fields

   {
     "contribution": "project xanadu — nelson's transclusion-and-visible-links hypertext dream that never shipped, the cautionary half of the lineage.",
     "era": "1960–",
     "id": "lin-xanadu",
     "name": "ted nelson",
     "sourceIds": [
       "src-i-xanadu"
     ]
   }

5. xerox parc · lineage · 1980s (decade)

   Original location · source-5b2b7d14ed65042b92f5

   Original structured fields

   {
     "contribution": "xerox notecards — the hypertext note system for researchers; the academic branch obsidian's users keep rediscovering.",
     "era": "1980s",
     "id": "lin-notecards",
     "name": "xerox parc",
     "sourceIds": [
       "src-i-notecards"
     ]
   }

6. wikiwikiweb · lineage · 1995 (year)

   Original location · source-1b9734a158ee2c586350 · source-e736cee16e428f7791e5

   Original structured fields

   {
     "contribution": "the wiki — ward cunningham's smallest viable hypertext, and the proof that editable link networks grow themselves.",
     "era": "1995",
     "id": "lin-wiki",
     "name": "wikiwikiweb",
     "sourceIds": [
       "src-i-wikiwikiweb",
       "src-i-wiki-history"
     ]
   }

7. andy matuschak · lineage · 2019– (approximate)

   Original location · source-4e556d955977a08f7d93 · source-f790dc32dbbf474f1521

   Original structured fields

   {
     "contribution": "evergreen notes — matuschak's writing on notes as compounding objects; the intellectual frame kepano's own essay canonized for obsidian's users.",
     "era": "2019–",
     "id": "lin-evergreen",
     "name": "andy matuschak",
     "sourceIds": [
       "src-i-evergreen-notes",
       "src-p-evergreen-notes"
     ]
   }

8. ink & switch · lineage · 2019 (year)

   Original location · source-82914319d3c543c55d4a · source-11ca8f6cecf9573264a5

   Original structured fields

   {
     "contribution": "local-first software: you own your data, in spite of the cloud — the ink & switch paper that named the architecture obsidian shipped. an intellectual neighbor of the ceo, not his employer.",
     "era": "2019",
     "id": "lin-local-first",
     "name": "ink & switch",
     "sourceIds": [
       "src-local-first",
       "src-inkandswitch"
     ]
   }

9. roam research · lineage · 2019–2020 (approximate)

   Original location · source-2467b0562d313ebb93d5 · source-f8dc3538f9a741fbef8b

   Original structured fields

   {
     "contribution": "the roam wave — graph-first networked thought in the cloud, $200m of paper valuation, and the lock-in lesson obsidian inverted: same idea, opposite storage.",
     "era": "2019–2020",
     "id": "lin-roam-wave",
     "name": "roam research",
     "sourceIds": [
       "src-i-roam-home",
       "src-i-roam-200m"
     ]
   }

10. tiago forte · lineage · 2017–2022 (approximate)

    Original location · source-5ef201638ed62e8b67b0 · source-4ab51a723abce6268aaf

    Original structured fields

    {
      "contribution": "the building a second brain industry — forte's para method and course economy that turned pkm into a consumer market obsidian inherited.",
      "era": "2017–2022",
      "id": "lin-basb",
      "name": "tiago forte",
      "sourceIds": [
        "src-i-basb-book",
        "src-c-forte-milo-video"
      ]
    }

11. file over app works · idea-claim

    Original location · source-c52605da6fcedec6451c · source-1fcf66a460bdeeda42ba · source-9f04ff1ce068ad93f61e

    Original structured fields

    {
      "detail": "the file outliving the app is not a slogan — markdown vaults opened in 2020 read identically in any editor in 2026, and every 'leaving obsidian' essay proves the exit door works. the moat is that there is no moat around the data.",
      "id": "clm-proved-file-over-app",
      "sourceIds": [
        "src-file-over-app",
        "src-c-amber-ditching",
        "src-c-hn-ditching"
      ],
      "title": "file over app works"
    }

12. no vc worked · idea-claim

    Original location · source-4eb4bd05ead39729adc1 · source-71f577b026b0578aa239 · source-428ac006b29b222f4314

    Original structured fields

    {
      "detail": "obsidian grew to a self-reported million-plus users and ten-thousand-plus organizations on licenses and services instead of venture rounds — proof that a tools-for-thought company can fund itself from users who pay for software they keep.",
      "id": "clm-proved-no-vc",
      "sourceIds": [
        "src-h-blog-new-sync-plans",
        "src-h-blog-free-for-work",
        "src-p-vcware"
      ],
      "title": "no vc worked"
    }

13. the plugin economy is the moat · idea-claim

    Original location · source-145aa08119bf52dd815e · source-868c5f71ca308fce1867

    Original structured fields

    {
      "detail": "the plugin directory passed 4,000 plugins and themes with 120m+ downloads — the community built more product than the company ever could, and the review queue became the governance problem that proved the scale.",
      "id": "clm-proved-plugin-economy",
      "sourceIds": [
        "src-i-obsidian-future-plugins",
        "src-h-cl-2020-10-29"
      ],
      "title": "the plugin economy is the moat"
    }

14. open format beat open source · idea-claim

    Original location · source-5f635ff7067dd71a8e64 · source-7d36eee0e358ea6b1f03 · source-045b468859c3561e77e5 · source-b2f278630904089ddaec

    Original structured fields

    {
      "detail": "a closed app with an open format outcompeted the open-source rivals on the thing that mattered — dendron's venture-funded team folded while obsidian's closed core kept shipping. the 'closed-source freeware' slur coexists with 'i pay for it anyway.'",
      "id": "clm-proved-format-beats-source",
      "sourceIds": [
        "src-c-dendron-eol",
        "src-c-abell-logseq",
        "src-c-tombert-logseq",
        "src-c-hn-vcware"
      ],
      "title": "open format beat open source"
    }

15. services can fund a free core · idea-claim

    Original location · source-71f577b026b0578aa239 · source-eb6031ec7de16983f358 · source-8c93ac8217aac57e5d90

    Original structured fields

    {
      "detail": "sync, publish, and catalyst monetize convenience without renting the files — the services layer funds the free core, and the 2025 decision to make the commercial license optional showed the model can afford to get more generous.",
      "id": "clm-proved-services",
      "sourceIds": [
        "src-h-blog-free-for-work",
        "src-h-blog-standard-plan",
        "src-i-obsidian-pricing"
      ],
      "title": "services can fund a free core"
    }

16. privacy survived the audits · idea-claim

    Original location · source-adff7365d3a49f2e5199 · source-e7ab0c4e37e393e4c3f9 · source-302bce77a9bbf807741e

    Original structured fields

    {
      "detail": "privacy-by-architecture held: no account required, no analytics, e2e-encrypted sync with published third-party audits — including a disclosed high-severity flaw found and fixed by trail of bits rather than discovered in the wild.",
      "id": "clm-proved-privacy",
      "sourceIds": [
        "src-h-security",
        "src-h-blog-sync-audits",
        "src-h-tob-pdf"
      ],
      "title": "privacy survived the audits"
    }

17. the graph didn't compound · idea-claim

    Original location · source-b37dc2abed9dd9b8f323 · source-dd6e545ddf0b385f9cf1 · source-4baced8d0a630a4bec3f

    Original structured fields

    {
      "detail": "the graph that was the launch poster became decorative — the most common veteran confession is that backlinks accumulate faster than insight. 'thousands of notes that i never referred to' is the unfinished half of networked thought.",
      "id": "clm-stalled-graph",
      "sourceIds": [
        "src-i-graph-useless",
        "src-i-graph-useful",
        "src-c-darcy-reboot"
      ],
      "title": "the graph didn't compound"
    }

18. capture without synthesis · idea-claim

    Original location · source-237b5747cb5a01193917 · source-375967e90724bc7813f7 · source-f2481ddd4f734f6127f2

    Original structured fields

    {
      "detail": "capture outran synthesis — the chapin critique and the departure genre converge on the same confession: the vault became a high-maintenance hobby. the tool organized thinking; it didn't do the thinking.",
      "id": "clm-stalled-synthesis",
      "sourceIds": [
        "src-c-chapin-notes",
        "src-c-obsidian-trap",
        "src-c-xda-memos"
      ],
      "title": "capture without synthesis"
    }

19. no real-time collaboration · idea-claim

    Original location · source-d5fdd594fe9b525f4e96 · source-317081692a4ae4d8d28b · source-4779a94bfa6bc702bd03

    Original structured fields

    {
      "detail": "real-time collaboration never arrived — sync merges files, it doesn't share a cursor. the single-writer assumption is the standing con in every review and the boundary the idea hasn't crossed.",
      "id": "clm-stalled-collab",
      "sourceIds": [
        "src-c-pcmag-review",
        "src-i-collab-live-editing",
        "src-i-collab-same-time"
      ],
      "title": "no real-time collaboration"
    }

20. mobile capture lagged · idea-claim

    Original location · source-0204db226c2f870e3f65 · source-6f5cf2920ec2049eafc8 · source-41312ccb6749a55bdfcc

    Original structured fields

    {
      "detail": "the mobile capture story stayed weak for years — 'more of a library than a notepad,' startup friction, icloud hangs. the idea promises thinking anywhere; the product mostly delivered thinking at a desk.",
      "id": "clm-stalled-mobile",
      "sourceIds": [
        "src-c-xda-quick-notes",
        "src-i-mobile-quick-capture",
        "src-c-forum-ios-slow"
      ],
      "title": "mobile capture lagged"
    }

21. publish stayed a niche · idea-claim

    Original location · source-756708134c8a8087d622 · source-e8323e80b37e8ea1b339 · source-220d315bddbf7ed3f326

    Original structured fields

    {
      "detail": "publish never became the public-web layer the local files deserved — a paid feature repriced down in 2023 and still mostly a garden tool, while the open web publishing dream kept drifting to quartz, astro, and hugo pipelines.",
      "id": "clm-stalled-publish",
      "sourceIds": [
        "src-c-unmarkdown-publish",
        "src-c-unmarkdown-alternatives",
        "src-c-hn-ingau"
      ],
      "title": "publish stayed a niche"
    }

22. the closed source taxes the story · idea-claim

    Original location · source-99246b935b5a5773d87d · source-f681355134f8b0ace026 · source-82b9b6655ef84ff52769

    Original structured fields

    {
      "detail": "the closed core keeps taxing the philosophy — every year a new audience rediscovers 'obsidian isn't actually open source,' and each files.md-style clone gets a hero thread. the file-over-app answer satisfies hn less each cycle.",
      "id": "clm-stalled-closed",
      "sourceIds": [
        "src-c-yahoo-not-oss",
        "src-c-hn-files-md",
        "src-p-forum-open-source"
      ],
      "title": "the closed source taxes the story"
    }

23. plain markdown files on a local disk turn out to be the best substrate an ai agent could ask for — readable, writable, searchable, diffable, versionable, and already organized as a graph. the accident became the feature. · argument

    Original location · source-242bf9fda9747bd9ca4f · source-cb999e23da7c9c9a2bdb · source-2616f7a9cf435f5d4634

    Original structured fields

    {
      "claim": "plain markdown files on a local disk turn out to be the best substrate an ai agent could ask for — readable, writable, searchable, diffable, versionable, and already organized as a graph. the accident became the feature.",
      "id": "arg-files-for-agents",
      "side": "for",
      "sourceIds": [
        "src-wordcell",
        "src-i-wordcell-readme",
        "src-i-basic-memory"
      ]
    }

24. obsidian shipped the infrastructure itself: the 2026 cli lets agents 'read, search, and write to your vault programmatically,' and headless sync puts the vault on servers where agents live. the company is building the agent front door, not just inheriting one. · argument

    Original location · source-2f7d2d8193afdd918051 · source-1061cc30b1058ce6da0d · source-325ea24225b41623a124

    Original structured fields

    {
      "claim": "obsidian shipped the infrastructure itself: the 2026 cli lets agents 'read, search, and write to your vault programmatically,' and headless sync puts the vault on servers where agents live. the company is building the agent front door, not just inheriting one.",
      "id": "arg-cli-headless",
      "side": "for",
      "sourceIds": [
        "src-i-obsidian-cli",
        "src-i-obsidian-sync-headless",
        "src-h-cl-2026-02-27"
      ]
    }

25. karpathy's llm-wiki post recast the vault as the ide for agent-compiled knowledge — web clipper for ingest, markdown as the compiler target, obsidian as the inspection surface. 1.2m views is the strongest signal the reframe landed. · argument

    Original location · source-a8f93e2f9d621655cb9a · source-d9fffa3624b70de02678

    Original structured fields

    {
      "claim": "karpathy's llm-wiki post recast the vault as the ide for agent-compiled knowledge — web clipper for ingest, markdown as the compiler target, obsidian as the inspection surface. 1.2m views is the strongest signal the reframe landed.",
      "id": "arg-karpathy-reframe",
      "side": "for",
      "sourceIds": [
        "src-c-karpathy-llm-wiki",
        "src-c-analyticsdrift-karpathy"
      ]
    }

26. the mcp ecosystem arrived before the official one — community servers plus claude code workflows already read and write vaults. 'claude just killed the note-taking app' and 'how i use obsidian + claude code' describe the same reality from opposite sides. · argument

    Original location · source-a491144eb4396b0f23a6 · source-1911bd4caf725114fdac · source-5e1b1c79f937a09d49c5 · source-e4a8103a9d8409910b8b

    Original structured fields

    {
      "claim": "the mcp ecosystem arrived before the official one — community servers plus claude code workflows already read and write vaults. 'claude just killed the note-taking app' and 'how i use obsidian + claude code' describe the same reality from opposite sides.",
      "id": "arg-mcp-ecosystem",
      "side": "nuance",
      "sourceIds": [
        "src-i-mcp-obsidian",
        "src-i-mcp-servers",
        "src-c-yt-icor-claude",
        "src-c-yt-isenberg-claude"
      ]
    }

27. the counter-case: if agents do the synthesis, the human-facing app is just storage — and a plain folder of markdown needs no obsidian at all. the files survive; the app that made them durable may not be needed to read them. · argument

    Original location · source-5754f90f69232ca53afc · source-c15fecf7198cf900db0e

    Original structured fields

    {
      "claim": "the counter-case: if agents do the synthesis, the human-facing app is just storage — and a plain folder of markdown needs no obsidian at all. the files survive; the app that made them durable may not be needed to read them.",
      "id": "arg-routes-around",
      "side": "against",
      "sourceIds": [
        "src-c-xda-plain-folder",
        "src-c-xda-notebooklm"
      ]
    }

28. kepano's own bet is local: 'language models need to be local to the device so that they can be private, offline and future-proof.' if inference stays cloud-side, the vault's local-first advantage is real but the agent that reads it is not. · argument

    Original location · source-1f6dcb581044aaca8f58 · source-a046fac0b2ab81c7036b

    Original structured fields

    {
      "claim": "kepano's own bet is local: 'language models need to be local to the device so that they can be private, offline and future-proof.' if inference stays cloud-side, the vault's local-first advantage is real but the agent that reads it is not.",
      "id": "arg-local-llm",
      "side": "nuance",
      "sourceIds": [
        "src-p-photoshop-for-text",
        "src-p-saw"
      ]
    }

29. wordcell · successor

    Original location · source-242bf9fda9747bd9ca4f · source-7d512451fecceab6638e · source-73d58e858f729704aeb9

    Original structured fields

    {
      "href": "https://wordcell.io/",
      "id": "suc-wordcell",
      "name": "wordcell",
      "note": "the obsidian idea rebuilt for agents — a knowledge base for coding agents from markdown, backlinks, semantic search, and git context.",
      "sourceIds": [
        "src-wordcell",
        "src-wordcell-github",
        "src-i-wordcell-skill"
      ]
    }

30. sponge · successor

    Original location · source-66745ddca5a55f1e3501 · source-faf32e52f4123f23b987

    Original structured fields

    {
      "href": "https://github.com/hraness/sponge",
      "id": "suc-sponge",
      "name": "sponge",
      "note": "hraness's knowledge harness for agentic research — the capture-and-synthesis layer the vault never grew.",
      "sourceIds": [
        "src-i-sponge",
        "src-i-sponge-docs"
      ]
    }

31. oh · successor

    Original location · source-f6676ea250640bb70b1f · source-424de19342568435f47f · source-b68bbaf80b39b4bf68a5

    Original structured fields

    {
      "href": "https://oh.computer/",
      "id": "suc-oh",
      "name": "oh",
      "note": "the ontology kernel for agent knowledge work — where a markdown vault stops being the answer and starts being the substrate.",
      "sourceIds": [
        "src-i-oh-computer",
        "src-i-oh-repo",
        "src-i-oh-skill"
      ]
    }

32. basic memory · successor

    Original location · source-2616f7a9cf435f5d4634

    Original structured fields

    {
      "href": "https://github.com/basicmachines-co/basic-memory",
      "id": "suc-basic-memory",
      "name": "basic memory",
      "note": "markdown-plus-mcp persistence for claude — the vault format held; the app that tended it became an agent.",
      "sourceIds": [
        "src-i-basic-memory"
      ]
    }

33. obsidian mcp servers · successor

    Original location · source-a491144eb4396b0f23a6 · source-afff77317ecf94c87af3 · source-87db77a172d789be8b56

    Original structured fields

    {
      "href": "https://github.com/MarkusPfundstein/mcp-obsidian",
      "id": "suc-obsidian-mcp",
      "name": "obsidian mcp servers",
      "note": "the community's agent bridge — multiple mcp servers exposing vaults to agents before the official cli arrived.",
      "sourceIds": [
        "src-i-mcp-obsidian",
        "src-i-obsidian-mcp-steven",
        "src-i-obsidian-mcp-bilal"
      ]
    }

34. obsidian itself · successor

    Original location · source-2f7d2d8193afdd918051 · source-1061cc30b1058ce6da0d · source-cc7dbdd6a47ea76154df

    Original structured fields

    {
      "href": "https://github.com/obsidianmd",
      "id": "suc-obsidian-cli",
      "name": "obsidian itself",
      "note": "the strongest successor claim is the incumbent's — cli + headless sync + the clipper's mit codebase is obsidian turning itself into the agent vault front end.",
      "sourceIds": [
        "src-i-obsidian-cli",
        "src-i-obsidian-sync-headless",
        "src-i-obsidian-clipper"
      ]
    }

35. tana · successor

    Original location · source-0a0a3327a6cc166b43f5 · source-3143c1eca88605dc4b18

    Original structured fields

    {
      "href": "https://tana.inc/",
      "id": "suc-tana",
      "name": "tana",
      "note": "the supertag outliner — the structured-data branch of the lineage, cloud-side.",
      "sourceIds": [
        "src-i-tana",
        "src-i-tana-outliner"
      ]
    }

36. capacities · successor

    Original location · source-3cdf9ace9a19adb6b90d · source-332a3afd961ca2099456

    Original structured fields

    {
      "href": "https://capacities.io/",
      "id": "suc-capacities",
      "name": "capacities",
      "note": "the object-based pkm that absorbed the first wave of obsidian departures — 'why are people leaving obsidian' was a capacities review.",
      "sourceIds": [
        "src-i-capacities",
        "src-c-yt-shu-capacities"
      ]
    }

37. anytype · successor

    Original location · source-4ad9feb4496c736ff8af

    Original structured fields

    {
      "href": "https://anytype.io/",
      "id": "suc-anytype",
      "name": "anytype",
      "note": "the open-source, local-first, e2e-encrypted rival — the lineage's answer to 'closed source, open files.'",
      "sourceIds": [
        "src-i-anytype"
      ]
    }

38. subconscious · successor

    Original location · source-00568364568f7dd61be6

    Original structured fields

    {
      "href": "https://subconscious.substack.com/",
      "id": "suc-subconscious",
      "name": "subconscious",
      "note": "gordon brander's sphere-descended project — the 'noosphere' branch of the lineage, still chasing the collective half of the memex dream.",
      "sourceIds": [
        "src-i-subconscious"
      ]
    }

39. does file-over-app survive the agent era — or does the agent become the app that owns the files? · open-question

    Original location

    Original structured fields

    {
      "text": "does file-over-app survive the agent era — or does the agent become the app that owns the files?"
    }

40. if agents do the linking, what is the human-readable artifact — the graph, the diff, or the file itself? · open-question

    Original location

    Original structured fields

    {
      "text": "if agents do the linking, what is the human-readable artifact — the graph, the diff, or the file itself?"
    }

41. does the vault's graph become the audit surface for agent actions — provenance as a first-class citizen? · open-question

    Original location

    Original structured fields

    {
      "text": "does the vault's graph become the audit surface for agent actions — provenance as a first-class citizen?"
    }

42. who maintains the vault when machines become the gardeners — and does 'high-maintenance hobby' stop being a critique when the gardener is free? · open-question

    Original location

    Original structured fields

    {
      "text": "who maintains the vault when machines become the gardeners — and does 'high-maintenance hobby' stop being a critique when the gardener is free?"
    }

43. can local-first survive enterprise governance — audit logs, retention, access control — without recreating the cloud it refused? · open-question

    Original location

    Original structured fields

    {
      "text": "can local-first survive enterprise governance — audit logs, retention, access control — without recreating the cloud it refused?"
    }

44. does obsidian become the agent vault's front end, or does the agent route around the app to the files it made durable? · open-question

    Original location

    Original structured fields

    {
      "text": "does obsidian become the agent vault's front end, or does the agent route around the app to the files it made durable?"
    }

45. can agents solve collaboration — merge, provenance, intent — without recreating cloud lock-in? · open-question

    Original location

    Original structured fields

    {
      "text": "can agents solve collaboration — merge, provenance, intent — without recreating cloud lock-in?"
    }