This shelf holds 12 nodes, from a 1945 design axiom to a 2016 empirical audit, ordered by the argument rather than by date. Tools go out of date; axioms do not. Read the axioms first, then pick a tool.
Node sequence
Suggested reading order · from the design axiom to the scientific audit
№ 01§ First ask: why externalise knowledge at allOrder within the group: the design axiom is proposed → naming and bidirectional links
The Memex is a hypothetical personal information desk proposed in 1945: microfilm storage for a person's entire library and records, with entries chained together by associative trails. The insight is not the capacity. It is the retrieval paradigm: any item can pull up another instantly, supplying routes that library-style hierarchical indexing cannot. The original keeps the ordinary index; association is a layer added on top.
The word "hypertext" is defined in Nelson's 1965 paper, meaning interconnected text that paper cannot present. Transclusion, which Nelson says his concept already contained, goes one layer deeper: the same content is embedded by reference in several places, so changing the source changes every instance.
3 min read
№ 02§ How to capture: three philosophies of the atomic noteOrder within the group: networked permanent accumulation → linear immediate capture → conceptual atomisation (digital)
A Zettelkasten is a networked accumulation system. Each card carries one concept and a unique address, cards point at one another by reference, and decades of accumulation turn the pile into a web of knowledge.
The Cornell system divides a page into three zones: the right column for live capture, the left for questions drawn out afterwards, and a band at the foot for a summary in your own words.
Evergreen notes are a set of disciplines: one concept per node, organised by concept rather than by source or topic, densely linked between nodes, and iterated on each revisit rather than rewritten.
Lab cases ×23 min read
№ 03§ How to organise and navigateOrder within the group: where things go → how material becomes finished work → how many at once → what form to write in → how to find them again
The first question in personal organisation is not what topic this belongs to. It is when you will need it. PARA arranges the answer into four tiers ordered by actionability: Projects are short-term efforts with a goal, Areas need ongoing attention, Resources are held for reference, Archives are no longer active.
Material you collect goes through four steps before it becomes finished work: Capture keeps only what resonates, Organize files it by actionability, Distill marks the essentials layer by layer, and Express assembles output from intermediate packets.
Personal kanban has two rules: visualise the work, and limit how much of it runs at once. A to-do list answers what needs doing. A board answers two more questions: how much is running right now, and where is it stuck.
Documentation usually fails for structural reasons rather than stylistic ones: four different reader needs get pushed into one document. Diátaxis separates them along two axes, whether the reader is doing or thinking and whether they are learning or working, producing four types: tutorial, how-to, reference and explanation.
A map of content is a note that references other notes: a hub for gathering, developing and navigating rather than a container. The essential difference from a folder is membership. A folder requires each thing to have exactly one home; a map only references, so one node can appear on any number of maps at once.
Lab cases ×23 min read
№ 04§ Does it actually work: the scientific auditOrder within the group: the empirical limits of the fragmentation cost → a stage model of personal information behaviour
Personal information management is an empirical science, not productivity folklore. Two central findings: search dominates for public information, but used for personal information it works less well, and the authors argue their user-subjective approach does not replace folders; and fragmentation has clear scope conditions, covering only splits across tools that system design forces.
Self-tracking systems pass through five stages: preparation, collection, integration, reflection and action. Each stage has its own barriers, and the barriers cascade forwards, so choosing the wrong collection tool only shows up at reflection when the data will not assemble.
3 min read
Read it yourself · Theory layer
The whole theory layer is here, with no account needed. Read it and go.
Trigpoint Pass · Application layer
The case layer (our own knowledge system under test, with the doctrine clauses) and the full verification layer of most nodes (how far each source was checked, counter-evidence and failure boundaries).