14 Nov 2026
How I built this
I built this site by talking to an agent. I chose, it built, I judged. Here is the log, including everything that did not survive.
The site is its own example. I did not write the code. I chose the problem, said what I wanted, set limits and rejected what came back until it was right. That is the job this site describes.
Two limits held the whole way. The site that was live at the time was not touched while this one was built. And nothing invented could be shown as fact: when the agent put a made-up number on the home page, it was replaced with a real one from the talk.
The first version was built from the talk. On 16 Nov 2026 the home page was rebuilt round the letter and the essay, and the skill library was brought in.
The method came from Adam Perlis, who published the recipe for his own site. I used his recipe and made my own design language with it.
The recipe
Write the one line firstWhat should the site get you? Mine is still a working line: people building with agents come here to learn how to run them.
Bring references and study them closelyFive sites, taken apart: how many type sizes, how much on a screen, what moves and for how long.
Start the log on day oneEvery message I sent is kept word for word, with what changed because of it.
Pick a boring, static stackAstro and plain CSS. Pages are plain files. No animation library: the motion is written by hand.
Build the system before the screensColours, type, radii and easing live in one file. Everything else reads from it.
Put one signature thing inLiving dots: coarse blue dither on black. Everything around it stays quiet.
Throw things awaySeven attempts are in the table below. I threw away six. Only the last one is on this site.
What I said to each attempt
Seven attempts. I threw away six. My messages are word for word.
Three looks for one site
i'm not attached to the design, can we explore completely brand new approach to the designs?
The look was not settled.
Four directions: field manual, logbook, blueprint, letters
i really like these layouts and design, i also like blueprint but too basic, is there a combination possible?
I respond to references more than to descriptions.
A documentation layout with a simulation
i hate the layout and the design tbh, feels vanilla with no personality
A tidy documentation page is not a personality.
Box-headed characters on a red field
doesn't work, still looks awful do not like this visual direction. look at the websites i sent and come back with afresh idea
Loud colour and cartoons were the opposite of what I had sent.
A white page written live by cursors
Still not it
An idea with no craft on show.
A terminal, a narrator and a contract to sign
Change the style
Right structure, wrong materials.
Three new layouts in one round
Stick to the previous layout
I had already accepted the layout by sending shader settings for it.
The design language
- Anything alive is drawn as dots: coarse blue dither on black. I picked it by its code, D2, from a page of fourteen versions.
- One accent, signal yellow, and only where a person decides.
- White page, small text, numbers in a dot-matrix face.
- The site opens in a terminal. A command starts the program, it fetches what the site holds with the counts running up, and asks if you are ready. The terminal then shrinks and becomes the guide in the corner, so the same black is handed along.
- The home page is the letter, then everything under it: the essay’s ten chapters, one rule from each lesson, and what went wrong. The page gets darker the further down it goes.
- The letter is read by scrolling. The page holds it still and the words come up out of grey in order.
- Every lesson has a short story that plays by itself, drawn by a renderer written for this site. A circle is an agent, a square is something made, a line is a boundary, yellow is a person, grey is stopped. There are no buttons on them: you are the yellow dot.
- Six lessons use a diagram instead, and it plays through its steps the same way.
- Friday, the square face in the corner, runs the team of agents. Her eyes are two terminal cursors. She reports to me, reacts to what you do, and goes quiet when asked.
- The skill library lists the 90 skills the agents run on, in the order the work needs them, each with the name of whoever made it.
- Sound is off until you turn it on. It follows the same meanings as the shapes: a plucked note when an agent arrives, a small bell for a check, a low thud when something goes wrong, a question and then an answer for your part. Anything that loops by itself stays silent.