How This Book Was Made

One person. One AI. Two versions, a few months apart.

The book you just read was written in a single day. One person, working with an AI assistant, starting with a closet full of old papers and ending with a published book, complete with an illustrated cover, source links, and a "Read the Book" button on the archive website.

I want to explain how, because the world is changing fast, and I think you should know.

What I Started With

The Queen Anne Fortnightly Club had been meeting every two weeks since 1894. Over 130 years, their members wrote more than 450 papers on everything from the founding of Children's Hospital to Marilyn Monroe to the price of real estate on Queen Anne Hill. These papers existed as stacks of old documents, handwritten pages, typewritten manuscripts, and faded photocopies.

Over the previous few months, I had used AI-powered tools to scan all of these documents and convert them into readable text. That cost about $15 total. The result was a digital archive of over a million words of women's writing spanning three centuries.

But nobody was going to read a million words of raw text. That's like asking someone to read an entire encyclopedia to find the good parts. I knew the good parts were in there. I just needed to find them and stitch them together into something people would actually want to read.

What Happened in 24 Hours

Morning. I told the AI: go through this entire archive and find the best stories. It read the catalog, the themes, the member profiles, and about 30 of the most promising papers in full. Within a couple of hours, it had identified the moments that would make people lean forward: the fish-net ceiling, the baby diary, the king who fined himself a cow, the 90-year-old in a rocking chair, the letter that makes you cry.

Afternoon. A complete first draft of the book was written. I read it and said: too polite, not enough surprises, needs more "oh my God, are you kidding me" moments. The AI went back into the archive, found a whole second layer of material I hadn't seen, and rewrote the entire book from scratch with a completely different structure.

Evening. I reviewed the rewrite and we did an enrichment pass: adding historical context (what was Seattle like in 1894? what did the Depression feel like?), sensory details (the smell of ground coffee and smoked meats in the grocery store), and source links so readers could click through to the original papers. An AI-generated book cover was created. The book was deployed to the web.

Night. I wrote the foreword in my own voice. We added the prologue, the epilogue with my five favorite papers, the "About the Author" section, the invitation to ArtLove Salon, and this page you're reading now. The book went through three rounds of revision based on my feedback about tone, voice, and what felt right.

What This Means

I'm not telling you this to brag. I'm telling you because the world is about to change very fast.

One person, working alone, produced a complete illustrated book from raw historical documents in less than 24 hours. The AI read hundreds of papers, identified the best stories, wrote 25,000 words of narrative, formatted everything as a beautiful web page, generated a book cover, and deployed it to a live website. I directed every decision, wrote the foreword, chose the tone, and decided what stories mattered. But the heavy lifting? That was the machine.

This is going to transform how we work. A lot of jobs that used to take teams of people will soon be done by one person with the right tools. That's exciting and also scary. It means the bonds between people, the face-to-face connections, the kind of thing the Fortnightly women built in their parlors, matter more than ever. Because when machines can do the work, what's left is the human part. The showing up. The listening. The caring.

I should mention: my brain works a certain way. I'm a polymath, an engineer, a painter, a builder. I think fast and I've been coding since I was twelve. I have a Ph.D. from Stanford and thirty years of experience building websites. So when I say "one person did this in 24 hours," I mean one person with a very specific set of skills and a very fast brain, plus a very powerful AI. Your mileage may vary. But the tools are getting better every month, and the gap between what experts can do and what anyone can do is closing fast.

The women of the Fortnightly understood something important: if you don't write it down, it's gone. They wrote everything down. They kept their yearbooks in pink and green. They preserved their minutes for 130 years. This book is just the latest attempt, using the latest tools, to make sure their voices are heard.

Now might be a good time to get to know your neighbors.

What Happened Next

The book above was written in a day, and it was good, but it wasn't deep enough. A few months later I went back in. This time with a different approach.

I pointed the AI at the archive again and asked it to mine: every paper, systematically, for the hardest emotional material, the most specific sensory details, the longest first-person passages. It worked for several hours. It came back with a list of ten sentences a woman of my grandmother's generation was not, strictly, allowed to say aloud in public — and each of which one of these women had said aloud in a Queen Anne parlor in the last thirty years. It came back with a thirty-seven-page private memoir a mother had written for her three children and that her dying daughter had read aloud to the club thirty years later. It came back with a meeting on February 22, 1917, so richly documented in the archive that we could reconstruct it minute by minute.

So we rewrote the book. It is now thirteen chapters instead of ten. It has about 60,000 words instead of 25,000. The emotional peak is not one letter anymore; it is a quiet chorus of seven voices across four generations of women. The book you just read is that second version. The first version still exists, in a backup, in case anyone ever wants to see where this started.

The Setup

I'll skip the pleasantries. Here's what happened.

I had a digital archive of 458 extracted text files from the Queen Anne Fortnightly Club (1894-2025), totaling 1,075,701 words. The OCR was done over previous months using Claude Sonnet via the Anthropic API at a total cost of about $15. The files were cataloged in a master _catalog.json with metadata (author, date, topics, one-liners, summaries). Member profiles, themes, photo metadata, and gallery data were in separate JSON files. The whole archive was served as a static site built by a Python script that injected all JSON into an HTML template.

The archive site was already live at conru.com/queenanne. Nobody was going to read 458 raw papers. I wanted a book.

The Stack

Everything was done inside Cursor IDE using Claude (claude-4.6-opus-high-thinking) in Agent mode. No other tools except SSH for deployment to a VPS (Debian, nginx) at 107.161.22.39:9221.

The AI had access to: Shell, file read/write/edit, Grep, Glob, semantic search, web fetch, image generation, and the ability to spawn background subagents for parallel work. No database. No framework. Just HTML, CSS, and raw text files.

Phase 1: Research (2 hours)

The AI read _catalog.json (201K chars, too large for one read), _themes.json, _member_profiles.json, _summaries.json, and _gallery.json. It then spawned 4 parallel subagents to read approximately 30 full papers from _extracted_text/, selecting them based on the summaries and one-liners that indicated narrative richness. Each subagent returned the full text of 4-6 papers.

Phase 2: First Draft (3 hours)

An 11-chapter book was written in a single HTML file (book.html) with embedded CSS for print-ready styling (6x9 inch pages, Garamond fonts, drop caps, scene breaks). Deployed via SCP.

Phase 3: Critical Review and Full Rewrite (4 hours)

After reading the first draft, I said it was too reverent. The AI spawned 3 more parallel research subagents to find juicier material: Mrs. Fry's 1898 poem, the 13 Years History by 6 charter members, Adelaide Pollock's biography, the grocery stores paper with Don Nelsen's secret projection room. Two background subagents then wrote chapters 1-5 and 6-10 in parallel, each receiving detailed prompts with all source material. The chapters were assembled into a new HTML file by a third subagent that read both the chapter text files and the CSS template from the first draft.

Phase 4: Enrichment (3 hours)

A subagent added: (a) "From the Archive" source link cards at the end of each chapter (23 links total), and (b) 1-2 paragraphs of historical context per chapter (Depression breadlines, 1918 flu, etc.). One real quote from the archive about the grocery store smell was added because it was too specific and good to paraphrase. File was modified in-place using StrReplace operations.

Phase 5: Design (2 hours)

Book cover generated via AI image generation (watercolor style, Queen Anne Hill at twilight). A Python patch script was written locally, SCP'd to the server, and executed to inject a "Read the Book" button into the archive site's header. The button CSS was injected before </style> and the HTML after </header>. A movie-trailer prologue was added between the dedication and TOC using StrReplace.

Phase 6: Voice and Framing (4 hours)

The AI read Andrew's 78,000-word memoir (conru.com/unadulterated/read.html) to understand his writing voice. A foreword was written and revised 3 times based on voice-match feedback. An epilogue with 5 favorite papers was added. An "About the Author" section with foundation links. A "Start Your Own Fortnightly" invitation card. Em-dashes were globally replaced (124 instances) because the author doesn't use them. This "How It Was Made" page was written.

Phase 7: The V2 Rewrite (separate session, several months later)

The v1 book above was good but observational. A few months later I came back with a specific mandate: push the emotional floor lower, add one chapter a woman would forward to a friend in her chest, get more specific about interior life, and use the archive more completely. The tooling had also moved forward: Claude Opus 4.7 instead of Sonnet, better agent orchestration, better long-context handling.

Seven parallel mining agents were spawned in a single turn, each with a narrow brief:

  1. Emotional Archaeologist: find ten Siegley-caliber passages across the 13 autobiographies from the 2007–2009 C'est Moi series.
  2. The Senses: extract 50+ concrete sensory details by category (smells, tastes, sounds, light, dress, weather).
  3. Interior Life: find 100+-word first-person passages; rank which voices could carry an entire chapter.
  4. Missing Layers: husbands, children, resistance, obituaries, modern loss.
  5. A Single Meeting: reconstruct one 1910s meeting minute by minute from the minutes and memoirs.
  6. Biographies: build dossiers on six women who could anchor biographical chapters.
  7. Creative Provocateur: propose ten bold structural alternatives to the current book.

Each agent wrote its output to a markdown file in _mining_output/. Total research output: ~215,000 words across seven files.

Findings were synthesized into a structural plan, with two opening versions drafted and a recommendation. Final call: keep the ten-chapter spine but expand to thirteen chapters, add an Author's Note disclosing method, replace the Pike 1911 epigraph with Alice Rayner's 1919 flu-year sentence (“We are all different women because we have known them”), and add a short italic Andrew-returns braid at the very end of the book.

Three entirely new chapters were written from archive material: February 22, 1917 (the single-meeting immersion), Have Any of You Heard of Her? (Pam Miles resurrecting Adelaide Pollock in 2019), and Dorothea (Checkley's 1978 private memoir, read by her dying daughter in 2008). A new WWII chapter, We Weren't That Kind of Club, was written from the 1934–44 and 1944–54 decade papers. The central emotional chapter, Scared Pink, was rewritten from one voice to seven. Chapter 1 was rewritten in Version B (second person, projects forward to Siegley on page one). Chapter 13 closes with the Rayner epigraph echoing back and a short italic author's return.

A Python integration script read the existing book.html, extracted kept chapters, converted the new markdown chapters to the same HTML format, renumbered everything, replaced the epigraph, inserted the Author's Note and Before You Begin sections, regenerated the table of contents for 13 chapters, and emitted a complete new book.html. OG/Twitter meta tags were updated to describe the new book ("Seven voices across four generations, a letter from 1987"), the optimized share image was swapped in, and the public book went live in one scp.

A Start Here page was added as the onboarding for archive-first visitors, with four progressive reading paths: five minutes (Siegley's letter), twenty minutes (Christoffersen's 1988 memoir), an hour (Checkley's 1978 memoir), a day (the book).

By the Numbers (v1 + v2 combined)

465 source papers (1,075,701 words)
~30 papers (v1) + ~100 papers (v2) read in full by AI
22 subagents total across both versions
13 chapters + Author's Note + Foreword + Epigraph + Before You Begin + Epilogue
~60,000 words final book (v2) · up from 25,000 (v1)
1 generated image (book cover) + 1 optimized JPG (share preview)
4 Python build scripts across both versions
0 fabricated facts (every quote real; Author's Note discloses interior reconstruction)
~20 hours (v1) + ~10 hours (v2) wall clock
1 person (directing) + 1 AI (executing)

What I'd Do Differently

On v1: the em-dash removal should have been a constraint from the start, not a 124-instance find-and-replace at the end. The first draft's chronological structure was the wrong call; character-driven would have been better from the start if I'd done a better initial brief. The subagent writing was sometimes hit-or-miss on tone; having the AI read 2-3 chapters of the author's memoir BEFORE writing would have saved a revision pass.

On v2: I should have launched the seven mining agents in parallel earlier — they produced more material in three hours than the v1 research phase produced in two. The Author's Note should have been drafted on v1 too, not deferred until v2. The integration script should have lived in the repo from v1; I ended up writing it fresh under pressure. The single largest mistake: assuming the archive's "obvious" emotional material was the whole of it. Systematic mining found seven Siegley-tier voices that the v1 pass had missed.

The whole thing — v1 plus v2 — could probably be done in 20 hours end-to-end now that the architecture and scripts exist. The bottleneck was, and is, iteration on voice and tone, which requires a human with taste. The AI is fast. The human deciding what "right" sounds like is slow. That's the job that remains.