The launch story
How this book was built
I finished From Archivist to Architect working alongside Claude Code, in a deliberate back and forth. This page is the honest record: what the tool did, what I did, and what went wrong on the way.
The manuscript was not new. I am Jovan Smith, and I drafted it into May 2026, when it was reviewed as publication-ready in substance. Then I stalled. For two months the draft sat in Google Drive while the launch work waited for a stretch of open time that never arrived.
The restart began with an inventory, not with writing. On Saturday, July 18, 2026, the sessions recovered the draft from Google Drive into a fresh private repository, along with a full accounting of what existed, what was missing, and what was already good enough. The finding: the remaining work was launch execution, not drafting.
The build
The draft went from recovered to release-ready without ever losing the thread. I worked the manuscript passes, figures, metadata, and quality checks with Claude Code alongside me, and every ruling landed in a decisions ledger the moment I made it. Nothing had to be re-litigated at 3am, because nothing was left in a chat window to forget.
The quality pass treated the book like production software: a full proofread, a cover-to-cover reader pass flagging every place a real reader would stall, and a visual check on each figure. Nothing shipped on an unresolved finding.
Every merge along the way, and the publish click itself, was mine.
None of this was the machine writing a book by itself. It was one operator who knows the material using a powerful tool at full speed. The judgment stayed human at every gate. That is also what the book argues, and one of its chapters documents the exact workflow that produced it.
What went wrong
Plenty. A 10pm publish target slipped, and the finish became an overnight session. A duplicate pull request had to be closed as superseded. A late change to the merge order could have scrambled the final build. The decisions ledger and the human review gates caught it before anything shipped wrong. The point of the system was never zero mistakes. The point was making them visible while they were still cheap.
Read more
This page is the full build story. The companion repo above is where the templates, checklists, and skills behind it live.