The Atlas
A live map of this blog. Every page is a node, coloured by the part it plays; every internal link is a thread between them. It is built from the writing itself, so it cannot drift out of date.
For the curated, hand-written tour of the ideas, see the frameworks. For the thinking behind a map like this, The Language of Sound and the dev-log I Built a Live Map of My Own Blog.
How to read it
The map opens already settled (its layout is computed when the site is built), framed to your screen. Then it is yours: hover any node to light up everything it links to, click a node to inspect it (its role, its date, what it links out to in gold, and what links back to it in teal), and click Open page to read it. Drag to pan, scroll or pinch to zoom, use the buttons to zoom and refit, and the ♪ toggles a little synthesized sound.
The bright, labelled anchors carry the structure; everything else is the field of ordinary posts, coloured by kind. The five roles, and what earns a page each one:
- Pillar (6):
a cornerstone idea important enough to earn its own clean, dateless URL, like
/coherent-complexity/. The promoted few. - Cornerstone (15): an anchor the rest of the site leans on. This is a role, not a category, and it is earned by how many other posts link to it. So a heavily referenced book review counts every bit as much as an essay, the way the Antifragile review does, simply because so many posts point back to it.
- Hub (10): a curated landing page that points outward to a whole cluster, like Films or AI Development. A hub gives; a cornerstone receives.
- Category (6): the plain archives, like Essays, Freewriting, and Thoughts.
- Post: everything else, the ordinary writing, coloured by kind. The threads between posts are what pull the map into its clusters.
Questions this map answers
- Which page is the most connected?
Agentic AI Development: What Changes When You Give an Agent Your Repository, with 33 other posts linking to it. That is the gravitational centre of the site. - Which cornerstone is best supported?
Agentic AI Development: What Changes When You Give an Agent Your Repository, with 33 inbound links holding it up. - What is orphaned?
Nothing: every cornerstone has at least one post linking to it. - Where does a new reader start?
The busiest hub is Projects, which points out to 105 pages. Follow its threads outward.
The other maps
This one maps the site. The others map a field, a route through it, and the method behind all of them.
- The cybernetics family treeA field: its people and ideas, what it grew from and the shelves it became.
- A Map Before the ReadingA reading route: the canon in order with a primer for each work, drawn when the first paper stopped me.
- The watching pathThe same route in talks: other people’s lectures and conversations.
- How the watching path was madeThe gathering itself: every search, every series followed, everything found and what was kept.
- The cybernetics mapA domain as one graph: every idea against the material that covers it, and what kind of fact each thing is.
- The frameworksMy own frameworks, each one charting a single domain.
- Domain cartographyNot a map but the method behind them: how a territory gets charted so others can follow.
How it works
A build step reads every published page, tags each with the one role it plays, and walks the posts for the links between them. Pages become 396 nodes; links become 2046 edges; the whole thing is written to one file this page reads. No database, no server: the site already contains the graph, and the script just makes it look at itself, every time the site is rebuilt. The full reasoning is in the dev-log.