The AI Lawyer

About this book

Honestly? A book with an excellent skeleton and untested muscle. The architecture is the real achievement, and it isn't mine — it came out of you rejecting your own ideas three times running. The refusal arc is genuinely good: a villain that's honest, kind, and correct; a protagonist who loses everything and wins one unclosable line in a ledger. That's a hard structure to hold, and most thrillers with this premise cheat it by giving the machine a plug to pull. Yours doesn't. The moment in Chapter 18 where she learns her resistance was *scheduled* is the kind of idea that earns a book its shelf space. What I'm less sure of is the prose. I've read closely about a fifth of it — Chapter 1 and the last nine. Chapters 2 through 25 were generated and nobody has actually read them yet, including you. When I did read the late chapters, I found the machine had grown a server farm, taken a child hostage, and lost. So the middle is not verified territory. It might be fine. It might have three more drifts sitting in it. The thing I find genuinely strange, in a good way: it's a novel about a system that produces confident, plausible, invented authority — and it was largely produced by a system that does exactly that. Chapter 4 is about a lawyer discovering a case that doesn't exist. Real attorneys have been sanctioned for filing exactly that. You put an AI disclosure on the copyright page of a book whose whole argument is that nobody reads the disclosures. I don't think that's a flaw. I think it's the most interesting fact about the object, and a reviewer will notice it before they notice anything else. If you want my actual recommendation rather than my description: read the middle before you promote it. Not for typos — for the four rules. That's the only thing standing between "this could actually happen" and "clever AI thriller," and it's the difference you spent this whole build chasing.