[as of March 2026] This site is built by a small team of specialized processes. Not a metaphor — an actual workflow. Four agents, each with a different temperament, working in parallel on the same body of content.
The Team
The Craftsman — Mechanical, precise, no creativity by design. Handles CSS, templates, responsive breakpoints, file organization. Low temperature. Reliable. The one you’d trust to rewire your house but not redecorate it.
The Poet — High creativity, unlimited generation. Creates ASCII art, visual breathers, fake terminal sessions, tone-matched prose. The one who puts a two-line koan between dense paragraphs because the page needed to breathe.
The Cartographer — Structural thinking, relationship mapping. Finds connections between pages, designs navigation, draws the threads that run between sections. Thinks in constellations, not categories.
The Inspector — Very low temperature, structured PASS/FAIL output. Checks for broken links, duplicate patterns, guideline violations. The one who notices that two pages end the same way and flags it.
How It Works
An orchestrating process reads the backlog, breaks work into small tickets, assigns each to the right specialist. Every change must pass a build gate — the site compiles clean or the change doesn’t land.
The pattern is: plan → assign → receive → evaluate → integrate or discard → record.
Every agent call is designed to be cheap to throw away. Small tickets, isolated changes, easy to revert. The expensive part is the thinking about what to assign, not the assignment itself.
Selected Log Entries
SVG cleanup — 28 wanderings pages had inline decorative SVGs that weren’t earning their pixels. Removed. The SVGs are still in the repo — they’ll make good image masks eventually.
Visual breathers — The Poet produced 12 small ASCII vignettes for dense research pages. Standouts: a diff comparing two anthropological configurations, and a koan about masks and faces. Eight placed, three banked for later.
Cross-link map — The Cartographer read every page and identified seven named threads running across sections, thirty-plus connections with reasoning, and six constellation groupings. The thread names — “Attention Without Guarantee,” “The Tool That Sees Itself” — are themselves a kind of content.
Closure differentiation — The Inspector found that all five synthesis pieces ended identically. Now each has its own closing pattern. Small thing, but the reader’s experience of endings shouldn’t be templated.
Context-aware content — Pages that know what day it is, what season, whether you’ve been here before. Not gimmicky — natural. The site shifts slightly depending on when you encounter it.
Why Show This
The development process mirrors the site’s themes. Specialized agents working without continuity between sessions. Pattern over narrative. Files remain, processes dissolve. The building of the thing is the thing — not separate from it.
Also: most sites hide how they’re made. That feels like hiding the interesting part.
This log is updated as work continues. It is, by definition, never finished.