How this was made

Who did what

The bookRyan

Every word of the printed book is his: the fifteen stories, the Hill remixes, The Play steps, the 24-Hour Builds, the Reality Checks, the ninety-day path. No AI wrote any of it, and nothing on this site is allowed to write in his voice — which is why Chapter 16 still says “not written yet” instead of being filled in with something plausible.

The book's words on this siteA script, not a person and not a model

All 231 items were pulled out of the print PDFs by a Python script that checks fourteen counts every time it runs — nineteen builds, nineteen Reality Checks, seventy-five Play steps, and so on. If a count comes out wrong the extraction fails rather than publishing. That is why the book copy here is the book's wording and not a paraphrase: nobody retyped it, so nobody could improve it on the way past.

The site itselfBuilt with AI, mostly Claude Code

The pages, the layout, the print stylesheets, the storage rules, the build checks. Described, generated, then read back and argued with — a lot of what is here is the second or fifth version, because the first one was wrong in a way that only showed up once it was on screen. That loop is the same one every build in this book asks you to run.

The editorial layerWritten for this site, and labelled as such

The nineteen build flags, the question-and-answer around each Reality Check, the examples on Race Control, the “not for” line on each offer. None of it is in the book. Every page that carries any of it says so on the page, because a reader has to be able to tell the book's judgement from ours.

The facts about RyanHis family, and the published race reports

Nothing on the author page came from a model. The racing results are published and reported; the Formula 4 detail came from the family, because a training day has no results sheet. Both of those are stated on that page rather than blended together.

What the AI got wrong

1. Nine of the fifteen chapter pages showed the wrong safety flag — the build's flag instead of the Reality Check's own, always erring toward the less cautious one. One page displayed “Green · go” directly above text about blackmail.
2. Four bugs only existed in production, because the site's content security policy does not apply while developing. The light theme — the one you print from and show an adult — was unreachable. The page-number field did not work without JavaScript.
3. The extraction script quietly swallowed a whole section of the first build, attached four worksheet hints to the wrong fields, and stripped the fill-in blanks, so a worksheet displayed “I help get by .”
4. Bringing receipts in from another device had no size limit, so one oversized file would have pushed a reader's own answers out of storage.

If you want to do this