@Ry Mac posted about helping his dad write a book: record him talking about his life, let Claude turn the transcript into chapters. Good post. Good instinct. I used the same method (with ChatGPT two years ago and published a book on a Yoga Style called BikYasa Yoga https://www.amazon.com/dp/B0D4QTCLZH?lv=shuf&channelId=500&plpRedirect=mhFallback). I read it Ry Mac's post twice, and the second read wasn't recognition. It was closer to déjà vu. I didn't set out to build a team of AI workers. I set out to finish a book that had been stuck for longer than I want to admit — one of several, all half-written, all going nowhere on their own. The actual method came from @Jake Van Clief: one worker, one job. Not one assistant asked to do everything passably. A separate one, built for exactly one thing. So the first two were small and specific: a transcriber that turns spoken audio into clean text, nothing else, and a content editor that takes that text and shapes it into something a chapter can be built from. The reason those two existed was a technique from a writing workshop: answer the book's questions out loud instead of staring at a blank page and typing them. Dictate the answer, the transcriber converts it, the editor refines it into prose. Two workers, one job each, built for that loop and nothing more. The book got finished. Then it needed a cover, so I built a designer. Then it needed somewhere to live, so I built a builder. Then it needed people to actually find it, so I built someone for marketing. None of that was planned before the step before it went stuck. Each one showed up because the real work hit a wall without it — never because a diagram said it should exist yet. Five books came out of that, in forty-five days, before any of it had a name worth putting on a page. The post this morning is describing a discovery.