{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"second-brain-register","urls":{"read":"https://miscsubjects.com/api/articles/second-brain-register/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/second-brain-register/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/second-brain-register/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/second-brain-register/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/second-brain-register/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/second-brain-register/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/second-brain-register/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"second-brain-register","title":"The second brain register: who built the plain-text knowledge base, and which part of it lasts","register":"standard","tags":["second-brain","obsidian","markdown","knowledge-graph","reference","zettelkasten"],"updated_at":"2026-08-06T07:20:07.306Z","body_excerpt":"This is a register of the people, formats and programs that built the idea of a personal knowledge base out of plain text files. It exists to be tracked rather than read once: when someone in this field publishes something that changes the shape of the problem, the entry for them is where it goes.\n\nIt is organised by what each entry actually contributed, because the field has a habit of crediting tools for ideas and ideas for tools. The formats outlast the apps. The apps outlast the methods. Most of the methods are the same three ideas in different packaging.\n\nOne correction first, because it is the thing people get wrong in their first hour.\n\n## The syntax is two brackets, not three\n\nA link between two notes is written with two square brackets on each side.\n\n    [[bpc-157]]\n\nObsidian's own documentation lists that as the wikilink format. Two more forms matter. A pipe changes what the reader sees while leaving the target intact:\n\n    [[bpc-157|the compound itself]]\n\nAnd a hash points at a heading inside the target:\n\n    [[the-obedience-gap#Part III]]\n\nThree brackets is not a syntax. It is what people remember after seeing `[[ ]]` once, and it silently fails to link, which is the worst kind of mistake: the note looks written and the graph stays empty.\n\n---\n\n## The lineage\n\n### Niklas Luhmann — the slip box, and the reason links come before folders\n\nA German sociologist who worked from a physical card index for decades and published at a rate that made people ask how. The answer was in the box: each card carried one idea, a fixed identifier, and pointers to other cards. Ideas were retrieved by following links, not by remembering which drawer they were in.\n\nThe load-bearing part is not the cards. It is that **the address of a note is permanent and its position is not**. Every good system since has re-derived that rule, and every bad one has tried to replace it with a better folder hierarchy.\n\n**Track:** the secondary literature; his own archive has been digitised and published by Bielefeld University.\n\n### Sönke Ahrens — the method, written down\n\n*How to Take Smart Notes* is the book that turned Luhmann's practice into something a person could follow, and it is the source most later systems are quietly restating. Its useful contribution is the separation of note types: fleeting capture, literature notes tied to a source, and permanent notes written in your own words. The distinction between \"I saved this\" and \"I understood this\" is the whole discipline.\n\n**Track:** the book. There is a revised edition.\n\n### Andy Matuschak — evergreen notes\n\nThe most rigorous thinking in the field, published as a working note site rather than a book. His definition: \"*Evergreen notes* are written and organized to evolve, contribute, and accumulate over time, across projects.\"\n\nThree principles follow, stated as titles of their own notes: \"Evergreen notes should be atomic\", \"Evergreen notes should be concept-oriented\", and \"Evergreen notes should be densely linked\".\n\nThose three lines are the best available specification for what a note in a knowledge base should be, and they map directly onto machine operations. Atomic means one addressable claim. Concept-oriented means the title is the assertion. Densely linked means the graph is the product, not a visualisation of it.\n\n**Track:** notes.andymatuschak.org. It updates in place, which is the point.\n\n### Tiago Forte — the name, and PARA\n\nThe person who made \"second brain\" a category. His organisational scheme, PARA, is described in his own words as \"a simple, comprehensive, yet extremely flexible system for organizing any type of digital information across any platform\": Projects, Areas, Resources, Archives.\n\nPARA is a folder scheme, and its honest reading is that it solves *actionability*, not knowledge. It sorts by how soon you need something. That is genuinely useful for work and close to useless for a corpus of research, where the same article is needed at unpredictable times forever. Take the vo","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"An internal link between two notes in Obsidian is written with two square brackets on each side, optionally with a vertical bar for display text and a hash for a heading; three brackets is not a valid syntax and silently fails to create a link.","tier":"definition","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"It is the single most common first-hour error, and a failed link leaves the note looking written while the graph stays empty.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"Andy Matuschak specifies a note in a knowledge base as evergreen — atomic, concept-oriented and densely linked — meaning one addressable idea per note, a title that states the assertion, and links treated as the product rather than a visualisation of it.","tier":"expert","interaction_risk":false,"status":"active","source_ids":["s2"],"why_material":"These three properties are the only widely-published note specification that maps directly onto machine operations on a corpus.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Tiago Forte's PARA sorts information into Projects, Areas, Resources and Archives, which orders material by how soon it is needed rather than by what it is about, making it a poor taxonomy for a reference corpus whose pages are needed at unpredictable intervals.","tier":"expert","interaction_risk":false,"status":"active","source_ids":["s3"],"why_material":"PARA is the most widely adopted folder scheme in this field and adopting it as a research taxonomy is the most common structural mistake it causes.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"JSON Canvas is an open specification for infinite-canvas data consisting of two optional top-level arrays, nodes and edges, with four node types (text, file, link, group), which makes a canvas generatable directly from a link graph with no drawing tool or layout engine.","tier":"definition","interaction_risk":false,"status":"active","source_ids":["s4"],"why_material":"It converts a visual feature into a file a build can emit, so a corpus that already holds edges can hand a reader a canvas.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"An Obsidian .base file is plain-text YAML with top-level filters, formulas, properties, summaries and views, so a saved query over a corpus is a text file a build can generate and a reader opens as a live table in their own application.","tier":"definition","interaction_risk":false,"status":"active","source_ids":["s5"],"why_material":"It means a build can ship queries, not just documents, without shipping an application.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"Karpathy's llm-wiki, published as a one-page GitHub gist in April 2026, prescribes three layers — immutable raw sources, a wiki of model-written Markdown, and a schema file such as CLAUDE.md or AGENTS.md — and argues for compiling sources once into a persistent interlinked wiki instead of retrieving raw sources per query.","tier":"expert","interaction_risk":false,"status":"active","source_ids":["s6","s7"],"why_material":"It is the clearest external statement of the compiled-corpus architecture, and it is an idea file rather than software, which is how it gets misreported.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"An Obsidian vault is a folder of Markdown files on local disk rather than a proprietary database, which is why any program that can write Markdown and folders can produce a vault and why static-site generators such as Quartz can publish one directly.","tier":"definition","interaction_risk":false,"status":"active","source_ids":["s9","s8"],"why_material":"It is the structural reason Obsidian is a viable compatibility target: there is no container to reverse-engineer.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"The durable layer of this field is its file formats rather than its applications or its methods: specifications with multiple implementations outlive the programs that read them, so a format readable with nothing but a text editor is the only safe substrate.","tier":"mechanism","interaction_risk":false,"status":"active","source_ids":["s2","s4"],"why_material":"It is the selection rule for what to adopt from this register, and the reason the entries that no longer exist are listed alongside the ones that do.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","url":"https://obsidian.md/help/Linking%20notes%20and%20files/Internal%20links","title":"Obsidian Help — Internal links (wikilink syntax)","quote":"Obsidian supports the following link formats: - Wikilink: [[Three laws of motion]]","claim_ids":[],"hash":"41dfce24717041df715b8712fc0d22a7503f65e07cbb195fe3e0d9b790644fc9"},{"id":"s2","url":"https://notes.andymatuschak.org/Evergreen_notes","title":"Andy Matuschak — Evergreen notes","quote":"Evergreen notes are written and organized to evolve, contribute, and accumulate over time, across projects.","claim_ids":[],"hash":"cf685ff02fa1aa7555938a0c0b649910d7ed0ae1ebc4eb845fc9649ebd97118e"},{"id":"s3","url":"https://fortelabs.com/blog/para/","title":"Tiago Forte — The PARA Method","quote":"PARA – a simple, comprehensive, yet extremely flexible system for organizing any type of digital information across any platform.","claim_ids":[],"hash":"05d6f88b8c9469e8e991e6a16f1393173931d5130b9e41efccf923b3669bb59c"},{"id":"s4","url":"https://jsoncanvas.org/","title":"JSON Canvas — open file format for infinite canvas data","quote":"The JSON Canvas format was created to provide longevity, readability, interoperability, and extensibility to data created with infinite canvas apps.","claim_ids":[],"hash":"b394891cac7334150ce2cf9f17fcf4e0ae9e0dc90cc920c5b5208441b38e217c"},{"id":"s5","url":"https://obsidian.md/help/bases/syntax","title":"Obsidian Bases syntax — .base files are plain YAML","quote":"filters:\n  or:\n    - file.hasTag(\"tag\")\n    - and:\n        - file.hasTag(\"book\")\n        - file.hasLink(\"Textbook\")","claim_ids":[],"hash":"cf0586af138957da2b4d7982a5e8b4c20be591ec0b2a805ed18aac4ccb8fd8a7"},{"id":"s6","url":"https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f","title":"Karpathy — llm-wiki (GitHub gist, April 2026)","quote":"A pattern for building personal knowledge bases using LLMs. This is an idea file, it is designed to be copy pasted to your own LLM Agent.","claim_ids":[],"hash":"c66dcb9ca9801b063bc2fa1e762e6dadd1d0ce57f34371d0885aae510b292ccb"},{"id":"s7","url":"https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f","title":"Karpathy — llm-wiki, the compiled-artifact argument","quote":"the wiki is a persistent, compounding artifact. The cross-references are already there. The contradictions have already been flagged.","claim_ids":[],"hash":"1db75e5682fac6e73339c8e26d73cfe891ba13a77ed0a5a9e8aab5bf5cf8c15b"},{"id":"s8","url":"https://quartz.jzhao.xyz/","title":"Quartz — static-site generator for Markdown vaults","quote":"Quartz is a fast, batteries-included static-site generator that transforms Markdown content into fully functional websites.","claim_ids":[],"hash":"b5af5c7ddb783bbfe343804dcdd02f4c7b0d3b3f0ae7653caabbc45814615db1"},{"id":"s9","url":"https://en.wikipedia.org/wiki/Obsidian_(software)","title":"Obsidian (software) — creators, release dates, storage model","quote":"Obsidian operates on a folder of text documents named a 'vault'; each new note in Obsidian generates a new text document, and all documents can be searched from within the app.","claim_ids":[],"hash":"fba86351bc26d4a0d9c1dda19763b68ef115ac7badf423be08f67f112466809a"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"second-brain-register","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":8,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":8,"claims_total":8,"sources":9,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}