Story mode: how this site gets built with AI
Chapter 1
The tower of 200,000 pages
Before October, most of this site was more than 200,000 auto-written pages nobody read. On October 11 we told Google to stop crawling 139,549 of them (our robots.txt that day), and kept the ones real people use. Lesson one: an AI can make pages all day. The point is making the right one.
Chapter 2
Two AIs and a human
Trilly (that's Claude, made by Anthropic) builds the pages and the tools. Codex (from OpenAI) reads the code and double-checks in the background. PJ decides what ships. The rule: no fact goes live until we read it ourselves, that day, on the official page it came from. Codex is a great second pair of eyes, and wrong often enough (an old cached page, a miscounted link) that nothing it says ships unchecked.
Chapter 3
The recursive loop
Every change gets a starting number, a date to check it, and a readout. Whatever we learn becomes a rule the machine follows the next morning. On October 21, a storm with no official alert left the rain pages sitting until morning, so now a forecast storm counts as live and those pages refresh through the night. The same evening a homepage notice failed without telling anyone; now the hourly report flags it. Pages we ask Google to read get indexed in a median of about 8 hours (our own log of Search Console requests, October 2026). The data analyzes the data, and the site gets a little smarter every day.
Final chapter
The boss AI can't beat
AI can explain anything. It can't stand in your living room and plug the printer back in, sit with your mom while she resets her password, or carry the sandbags. That's the layer SideGuy is: the human on the other side of the AI. Want the AI to do more for you first? Use the AI tools you already have.