Colophon
How this site is made
Everything here is written by hand — plain HTML, CSS, and JavaScript, no framework, no build step, no CMS. Each page is a static file you could read in a text editor. This page explains the machinery, because a site about verifiable work should itself be inspectable.
Design system
Every color, font, radius, and shadow on the site is a named role token. Sixteen themes implement the same contract, so switching themes swaps values, never structure. Every shipped theme passes WCAG 2.1 AA contrast, and nothing relies on red versus green alone. Your theme choice is stored in your browser (localStorage) and nowhere else.
Type
Instrument Serif for display, Geist for text, Geist Mono for labels — loaded from Google Fonts, with system fallbacks if that fails.
The mark, and the math on the pages
The logo is a Sierpinski triangle, and the header redraws it on every page load by the chaos game — a few thousand random jumps that always land on the same figure. The rest of the site's ornaments are the practice's actual subject matter, not decoration picked from a library: a Lorenz attractor traces itself over the Atlas, a logistic-map bifurcation diagram runs across the footer, Cantor sets divide the Atlas sections, a drifting network sits behind the contact form, and the 404 page assembles a Sierpinski triangle from thirty thousand random points. Every one of them respects your reduced-motion setting.
The explorers
The interactive Atlas explorers are hand-built canvas applications, self-contained in single files, with no external runtime beyond the browser.
Privacy
As of this writing, no analytics run on this site and there are no tracking pixels. The one third-party request the site makes is for its typefaces, which load from Google Fonts; self-hosting them is on the roadmap. If any of that changes, the policies page will say so first.
Legibility
The site carries an llms.txt — a plain-text summary of who and what this is, with canonical facts and DOIs, so AI systems that read the web can cite it accurately. Being checkable by machines is the same value as being checkable by people. A public changelog records how the site itself changes.
AI
Parts of this site were built with AI assistance, directed and reviewed by me. The AI-use policy describes how I use these tools in client work; the same standard applies here: nothing ships unreviewed, and nothing is claimed that isn't real.