Org mode

The oldest continuously used plain-text system in this corpus’s tools-for-thought set, and the one it did not hold. From the Org manual (T1, first-party): “Org mode is an authoring tool and a TODO list manager for GNU Emacs.”

That double description is the whole point. obsidian, logseq, roam-research and tana each pick a centre — notes, blocks, graph, database — and grow outward. Org grew from an outliner (it sits on top of Emacs’s Outline mode) and then absorbed everything a working researcher does around an outline: TODO states, scheduled and deadline dates, “dynamic agenda views” computed across files, tables with a spreadsheet, executable source blocks, and export to LaTeX, HTML, and the rest.

The format is the durability argument. Org files are “strictly plain text files, the most portable and future-proof file format” — readable in any editor, though Emacs is where the behaviour lives. Set that beside roam-research‘s hosted database and the local-first turn the corpus has been tracking: Org made that choice in 2003 and never had to reverse it.

The manual describes the design stance as a toolbox: the basics stay simple, the rest is there when wanted, and nothing forces the user through the full system. That is a different answer to complexity than the one tiddlywiki5 or logseq give — not a smaller feature set, but an optional one.

Its distinctive contribution: code in the document

Org Babel — executable source blocks in many languages inside a single file — is the piece nothing else in this corpus matches, and it has a peer-reviewed account of its own (org-mode-literate-programming). It puts Org in two of the spoke’s threads at once: tools-for-thought, and the executable-markdown / literate-computing lineage that runs from augmenting-human-intellect through today’s notebooks.

Not read here: Org’s own history, its user base, and how it has fared against the newer generation — the manual documents the system, not its adoption.