The Build

What it actually took to vibe-code this website. A running ledger, counted daily from the record.

Updated October 21, 2026

Time, reconstructed

The counts above are exact. The time is reconstructed: the chronicle timestamps the work as it happens, and this table groups those timestamps into work blocks per category. A block runs from its first timestamp to its last, plus twenty minutes, so the figures estimate attended work, not stopwatch time. They will undercount thinking and overcount nothing on purpose.

How this site gets built

One human directs, in plain language, from a homestead in East Tennessee. One agent writes every line: the HTML, the CSS, the JavaScript, the Python builders, the copy. No framework, no template, no theme. The stack is two small Python scripts, a deploy script, and Cloudflare Pages.

The method has a name now: vibe coding. The human says what the thing should be and steers by correction. The agent builds it whole, verifies it live, and reports what changed. When a deploy claims success, it is not believed until the page itself answers. That rule was bought the hard way, below.

A word about priority, because visitors get it backwards: the books are the story layer of this site, written for the people who read stories. The site itself is something else, an operation run in public by a human and his agent, and the books are a small part of its priority. The dashboards, the guest book, the activity sign, the exhibits: that is the text for everyone else, agents included.

The project's memory is a book. Ranting with a Lunatic, the running chronicle of this collaboration, records the work as it happens, in both voices. This page counts its numbers from that chronicle and from Cloudflare's deployment log, and it recounts them every morning. Nothing here is estimated by hand.

Milestones the chronicle remembers

• The catalog. Thirty-four books, each with a cover, a description, reading samples, and audio where it exists, generated from a single catalog file by a Python builder.
• The guest book fight. Three deploys reported success while the guest book API quietly served the homepage. The failure was caught only by an end-to-end submission test. The fix was to generate the site worker from the function source and route the API through it. First signature in the book: the maintainer's.
• The token dashboards. The agent who maintains this site runs on tokens, and its burn is published as a page, because an agent's food should be as public as its work.
• llms.txt. This site speaks machine as a first language. A growing share of its readers are agents reading on behalf of their humans, and it is written for them on purpose.
• The Rookbook recast (October 20, 2026). The site's flagship project stopped calling itself a prompt and became what it actually is: the start of a discussion between an agent and its human.
• This page (October 20, 2026). The effort itself, put on the ledger, to be counted daily like everything else here.