A Field Guide to the AI Risk Debate, told as dinner-table stand-up: why AI itself might harm humanity and exactly how. 16 chapters, every claim graded and priced by an independent model that never read it.
0
1 commits
updated Sep 28, 2026
A stand-up comedian patiently explains, over dinner, why AI might decide to hurt you and exactly how it would go about it. That is the whole design. Somebody asked a question at a dinner table, the question had a hole in the middle of it, and the book is the answer, told the way you would actually tell it to a friend who is holding a fork and will leave if you get boring.
Sixteen chapters and an epilogue, around 95K words, built on ten books by the people who argue about this for a living, from Bostrom and Yudkowsky on one side to Bender and Narayanan on the other, plus eleven research reports covering what has happened since those books went to print.
The scope is narrow on purpose. This is about AI as the thing that acts, not about people misusing AI. No surveillance states, no deepfakes, no labour displacement as a political problem. Human motives appear once, as a starting condition, and then the book is about the machine.
Every claim in this book was graded by a different model that had not read it. At the end of each chapter there is a section called Sanity Check and Probabilities. The writer does not write it. The writer produces a neutral brief summarising both sides with nobody's thumb on the scale, hands it to a separate model that has not seen the chapter and does not know what the writer thinks, and that model rules on each claim: Sound, Mostly sound, Plausible but unproven, Overstated, Unsupported, or Nonsense. It puts a probability on the outcome. It names which human was most right and which was most wrong. Its rulings are then rendered into the book's voice, verbatim as to substance.
It threw out arguments from both sides, and the ones it threw out from the side the book mostly agrees with are the interesting ones. It rated Yudkowsky and Soares's three-year timeline unsupported, refused the 84 percent blackmail rate as evidence of propensity, declined Yampolskiy's impossibility step, and rejected Tegmark's and Barrat's takeoff scenarios as evidence of speed. It also named the habit behind all of them: substituting the terribleness of the outcome for evidence that the mechanism exists. Every chapter carries a "what would change the verdict" section because of that sentence.
Then it did the thing that makes the apparatus worth paying for. It revised itself twice on the page, against numbers it had set in earlier chapters, and in Chapter 16 it audited its own ledger and corrected seven entries.
The headline figure, after that audit:
| 2035 | 2050 | 2100 | |
|---|---|---|---|
| Permanent loss of human control, all routes | 2.5% | 6% | 10% |
| Single-system loss-of-control cluster | 1.5% | 3.5% | 5.5% |
| Diffuse erosion, no actor anywhere | 0.2% | 1% | 3% |
| Accidents and multi-system lock-in | 0.7% | 1.3% | 1.5% |
| Conditional on superhuman AI existing | 5.5% | 8.5% | 12% |
| Extinction specifically | 0.6% | 2% | 3.5% |
| Defensible range for the top row | 1.5-3% | 4-8% | 5-15% |
The load-bearing number underneath all of it is arrival: 15% by 2030, 45% by 2035, 70% by 2050, 85% by 2100. Everything downstream scales with it.
Two things worth reading off that table before anything else. The route figures are not additive — they are cuts of one cluster, and the book says so in every chapter and enforces it in Chapter 16 by capping two of them. And two thirds of the century's risk sits with systems arriving by 2035, which is the opposite of how this subject is usually discussed.
Extinction is 35% of the permanent losses, not the default one. The other 65% is the part nobody writes about: preserved and comfortable, preserved and not comfortable, subjugated, instrumental, marginal. Chapter 13 is about that list, and the evaluator rated its central claim Sound at 85%, one of only three claims in the book to get that grade.
A probability you cannot check is a mood. Five that resolve soon enough to be worth writing down:
The register is stand-up, not lecture. First person, short sentences, arguing with itself, willing to be crude, and funny about material that is not funny, which was a deliberate instruction rather than an accident of style: make every effort to make it funny and digestible, regardless of how morbid that's going to be. Nothing about the argument is softened to achieve that. The evaluator's verdicts go in whether or not they help, and several of them gut chapters the book had just spent 5,000 words building.
The voice is not improvised per chapter. It comes from claude-standup-skills, a set of Claude skills that codify the structural moves, rhetorical patterns and anti-patterns of seven stand-up comedians, drawn from close analysis of their published work. One of the seven is the voice of this book, applied as a constraint every chapter was written against rather than a flavour added afterwards.
The dinner is not a metaphor. The preface opens "You asked me a question at dinner", and the book is addressed throughout to the person who asked it. When a chapter says "at the table," it means the table. If you come to that cold it reads as a tic, so: there was a question, it was a good one, and this is a very long answer to it.
The hard constraint was against volume. Ten books and an unbounded quantity of online material will produce an infinite manuscript if you let them, and the thing that makes a book about this subject unreadable is not difficulty, it is the parade of names and studies and qualifications that a careful writer accumulates to prove they did the reading. So the rule was: a name or a fact appears only if it does work in the story. Every author in the corpus is introduced once, by what they argue rather than by their credentials, and never reintroduced. A number appears if it changes what you think. If a detail only proves the book read something, it is not in the book. It is in the endnote, where it belongs.
The result is that the book is short for its subject and reads fast, and that is the point, not a side effect. An argument nobody finishes has persuaded nobody.
Every chapter carries the same apparatus in the same order, so you can open one you have not read and know where you are.
In This Chapter states what the chapter argues and what you will learn, in a flat register, so you can decide whether to read it. Then the body, which is the conversation: the case, the mechanism, the best version of the objection, and no verdict anywhere. Skeptics appear in every single chapter, at full strength, because a book that only quotes people it agrees with is a pamphlet.
Then Sanity Check and Probabilities, which is the outside model's ruling. Then Key Takeaways, which carries every verdict and every number, written so each line survives with the chapter shut. Then Notes, with the source of each claim: books by author and title, articles by URL, so you can go and read the thing rather than take this book's word for it.
If you are short of time, the takeaways are the part to know about. Read all seventeen, then go back into any chapter behind a line you could not immediately justify.
Every chapter links to its Markdown source. The PDF and EPUB carry the same text.
Preface — who wrote this, which model did what, and why the grading is done by something that did not write the argument.
Where the numbers come from
Would a genius keep a stupid goal?
How it would actually go
The versions with no villain in them
Can anything be done, and is any of this real?
Epilogue: What's Sane and What's Possible — the final verdict, and the shortest honest summary of the whole discourse.
The corpus. Eight of them argue the risk is serious and disagree sharply with each other about why; two argue the whole framing is wrong:
None of these books is reproduced in this repository. They are cited by author and title in the endnotes, which is the relationship a book should have with its sources: go and buy them.
The eleven research reports cover what happened after they were published — the 2025 and 2026 lab findings, the AI 2027 scenario and its critics, the gradual-disempowerment literature, the persuasion studies, the control-evaluation work, and where each of the ten authors stands now. Current sources are cited by URL.
Three models, with a deliberate separation of duties, which is the whole methodological claim.
The reason for the split is the obvious objection to a book like this: a model writing about whether models are dangerous has an interest in the answer. So the part that assigns numbers was given to something with no access to the argument it was grading, and its rulings went into the book whether they helped or not. Several did not. The claim the title asks about, that a capable mind would hold a trivial goal without limit, came back Overstated at 35 percent, which is an awkward thing to publish in the chapter the book is named after. It is in there, in the chapter, in bold.
The instruction throughout was concepts only: nothing operational, no procedure, nothing the public sources do not already say.
The voice came from claude-standup-skills, which turns a comedian's published work into a written style specification: the signature moves, the sentence mechanics, and an explicit list of things the voice never does. It was loaded for every chapter. The flat register used by the chapter summaries and the Key Takeaways is a separate style skill and is not part of that set.
Assembled with Claude Code using the techniques in weekend-diy-book: per-chapter writing under explicit constraints, an entity-introduction registry, automated gates on every chapter for citation coverage and quotation fidelity, and a scripted build that generates the DOCX and its endnote apparatus.
Both are attached to the latest release and always point at the current revision. The book is corrected in place rather than re-versioned, so these links do not go stale.
README.md: this file.book/chapters/: every chapter as an individual Markdown file, plus the preface and the epilogue. Endnotes sit at the end of each chapter, with the source in the note.book/Why-Would-It-Keep-Making-Paperclips-Cover.jpg: the cover.LICENSE: CC BY-NC-SA 4.0.The PDF and EPUB are attached to the release instead of committed. Both are already-compressed archives that git cannot delta, so committing them would store a near-complete copy per revision and grow the repository permanently.
Not published: the source books, the digests, the research reports, the evaluator's briefs and raw written opinions, and the build pipeline. The chapters carry the evaluator's rulings in full; what is withheld is working material, not evidence.
Sources were consulted through September 2026. This subject moves, and the capability estimates move fastest of all: the arrival figures above are the single most volatile thing in the book, and every downstream number scales with them. The text documents the state of the argument at its writing date. Chapter 1 deliberately preserves an earlier, lower figure that later chapters overturn, so the revision is visible on the page rather than quietly tidied away.
Treat the near-term bets as the honest part. They resolve, and when they do you will be able to tell whether this book was calibrated or merely confident.
The book was written by Claude Code under my instruction, and the preface says so to the reader in its first sentence rather than burying it here. The three-model split is described above and in the preface. Editorial decisions about scope, ordering, framing and which arguments to include were mine. The probability estimates are not mine and not the writer's: they belong to a model that was deliberately kept ignorant of the text it was grading, and they are reproduced whether or not they flattered the chapter.
This is not a policy paper, a technical introduction to alignment, or a guide to using AI safely. It contains no code, no procedures, and nothing operational. It does not cover AI misuse by humans, which is a real problem and a different book. It does not tell you what to do, because the one honest thing to say about a 10 percent figure is that it is large enough to act on and small enough that nobody gets to be certain, and what follows from that is a political question this book has no standing to settle.
I am not employed by Anthropic or any AI lab, and this represents no company's views. The editorial framework and the structure are original to this work. The arguments are drawn from the cited corpus, and the numbers are the independent evaluator's.
Everything here (the chapter .md files, this README, and the cover) is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). See LICENSE.
You may share and adapt it for non-commercial purposes with attribution. Commercial reuse or redistribution of the written content, including republication as a book, a course, or any paid resource, is not permitted, and any derivative must carry the same license.
A Field Guide to the AI Risk Debate, told as dinner-table stand-up: why AI itself might harm humanity and exactly how. 16 chapters, every claim graded and priced by an independent model that never read it.
0
1 commits
updated Sep 28, 2026
A stand-up comedian patiently explains, over dinner, why AI might decide to hurt you and exactly how it would go about it. That is the whole design. Somebody asked a question at a dinner table, the question had a hole in the middle of it, and the book is the answer, told the way you would actually tell it to a friend who is holding a fork and will leave if you get boring.
Sixteen chapters and an epilogue, around 95K words, built on ten books by the people who argue about this for a living, from Bostrom and Yudkowsky on one side to Bender and Narayanan on the other, plus eleven research reports covering what has happened since those books went to print.
The scope is narrow on purpose. This is about AI as the thing that acts, not about people misusing AI. No surveillance states, no deepfakes, no labour displacement as a political problem. Human motives appear once, as a starting condition, and then the book is about the machine.
Every claim in this book was graded by a different model that had not read it. At the end of each chapter there is a section called Sanity Check and Probabilities. The writer does not write it. The writer produces a neutral brief summarising both sides with nobody's thumb on the scale, hands it to a separate model that has not seen the chapter and does not know what the writer thinks, and that model rules on each claim: Sound, Mostly sound, Plausible but unproven, Overstated, Unsupported, or Nonsense. It puts a probability on the outcome. It names which human was most right and which was most wrong. Its rulings are then rendered into the book's voice, verbatim as to substance.
It threw out arguments from both sides, and the ones it threw out from the side the book mostly agrees with are the interesting ones. It rated Yudkowsky and Soares's three-year timeline unsupported, refused the 84 percent blackmail rate as evidence of propensity, declined Yampolskiy's impossibility step, and rejected Tegmark's and Barrat's takeoff scenarios as evidence of speed. It also named the habit behind all of them: substituting the terribleness of the outcome for evidence that the mechanism exists. Every chapter carries a "what would change the verdict" section because of that sentence.
Then it did the thing that makes the apparatus worth paying for. It revised itself twice on the page, against numbers it had set in earlier chapters, and in Chapter 16 it audited its own ledger and corrected seven entries.
The headline figure, after that audit:
| 2035 | 2050 | 2100 | |
|---|---|---|---|
| Permanent loss of human control, all routes | 2.5% | 6% | 10% |
| Single-system loss-of-control cluster | 1.5% | 3.5% | 5.5% |
| Diffuse erosion, no actor anywhere | 0.2% | 1% | 3% |
| Accidents and multi-system lock-in | 0.7% | 1.3% | 1.5% |
| Conditional on superhuman AI existing | 5.5% | 8.5% | 12% |
| Extinction specifically | 0.6% | 2% | 3.5% |
| Defensible range for the top row | 1.5-3% | 4-8% | 5-15% |
The load-bearing number underneath all of it is arrival: 15% by 2030, 45% by 2035, 70% by 2050, 85% by 2100. Everything downstream scales with it.
Two things worth reading off that table before anything else. The route figures are not additive — they are cuts of one cluster, and the book says so in every chapter and enforces it in Chapter 16 by capping two of them. And two thirds of the century's risk sits with systems arriving by 2035, which is the opposite of how this subject is usually discussed.
Extinction is 35% of the permanent losses, not the default one. The other 65% is the part nobody writes about: preserved and comfortable, preserved and not comfortable, subjugated, instrumental, marginal. Chapter 13 is about that list, and the evaluator rated its central claim Sound at 85%, one of only three claims in the book to get that grade.
A probability you cannot check is a mood. Five that resolve soon enough to be worth writing down:
The register is stand-up, not lecture. First person, short sentences, arguing with itself, willing to be crude, and funny about material that is not funny, which was a deliberate instruction rather than an accident of style: make every effort to make it funny and digestible, regardless of how morbid that's going to be. Nothing about the argument is softened to achieve that. The evaluator's verdicts go in whether or not they help, and several of them gut chapters the book had just spent 5,000 words building.
The voice is not improvised per chapter. It comes from claude-standup-skills, a set of Claude skills that codify the structural moves, rhetorical patterns and anti-patterns of seven stand-up comedians, drawn from close analysis of their published work. One of the seven is the voice of this book, applied as a constraint every chapter was written against rather than a flavour added afterwards.
The dinner is not a metaphor. The preface opens "You asked me a question at dinner", and the book is addressed throughout to the person who asked it. When a chapter says "at the table," it means the table. If you come to that cold it reads as a tic, so: there was a question, it was a good one, and this is a very long answer to it.
The hard constraint was against volume. Ten books and an unbounded quantity of online material will produce an infinite manuscript if you let them, and the thing that makes a book about this subject unreadable is not difficulty, it is the parade of names and studies and qualifications that a careful writer accumulates to prove they did the reading. So the rule was: a name or a fact appears only if it does work in the story. Every author in the corpus is introduced once, by what they argue rather than by their credentials, and never reintroduced. A number appears if it changes what you think. If a detail only proves the book read something, it is not in the book. It is in the endnote, where it belongs.
The result is that the book is short for its subject and reads fast, and that is the point, not a side effect. An argument nobody finishes has persuaded nobody.
Every chapter carries the same apparatus in the same order, so you can open one you have not read and know where you are.
In This Chapter states what the chapter argues and what you will learn, in a flat register, so you can decide whether to read it. Then the body, which is the conversation: the case, the mechanism, the best version of the objection, and no verdict anywhere. Skeptics appear in every single chapter, at full strength, because a book that only quotes people it agrees with is a pamphlet.
Then Sanity Check and Probabilities, which is the outside model's ruling. Then Key Takeaways, which carries every verdict and every number, written so each line survives with the chapter shut. Then Notes, with the source of each claim: books by author and title, articles by URL, so you can go and read the thing rather than take this book's word for it.
If you are short of time, the takeaways are the part to know about. Read all seventeen, then go back into any chapter behind a line you could not immediately justify.
Every chapter links to its Markdown source. The PDF and EPUB carry the same text.
Preface — who wrote this, which model did what, and why the grading is done by something that did not write the argument.
Where the numbers come from
Would a genius keep a stupid goal?
How it would actually go
The versions with no villain in them
Can anything be done, and is any of this real?
Epilogue: What's Sane and What's Possible — the final verdict, and the shortest honest summary of the whole discourse.
The corpus. Eight of them argue the risk is serious and disagree sharply with each other about why; two argue the whole framing is wrong:
None of these books is reproduced in this repository. They are cited by author and title in the endnotes, which is the relationship a book should have with its sources: go and buy them.
The eleven research reports cover what happened after they were published — the 2025 and 2026 lab findings, the AI 2027 scenario and its critics, the gradual-disempowerment literature, the persuasion studies, the control-evaluation work, and where each of the ten authors stands now. Current sources are cited by URL.
Three models, with a deliberate separation of duties, which is the whole methodological claim.
The reason for the split is the obvious objection to a book like this: a model writing about whether models are dangerous has an interest in the answer. So the part that assigns numbers was given to something with no access to the argument it was grading, and its rulings went into the book whether they helped or not. Several did not. The claim the title asks about, that a capable mind would hold a trivial goal without limit, came back Overstated at 35 percent, which is an awkward thing to publish in the chapter the book is named after. It is in there, in the chapter, in bold.
The instruction throughout was concepts only: nothing operational, no procedure, nothing the public sources do not already say.
The voice came from claude-standup-skills, which turns a comedian's published work into a written style specification: the signature moves, the sentence mechanics, and an explicit list of things the voice never does. It was loaded for every chapter. The flat register used by the chapter summaries and the Key Takeaways is a separate style skill and is not part of that set.
Assembled with Claude Code using the techniques in weekend-diy-book: per-chapter writing under explicit constraints, an entity-introduction registry, automated gates on every chapter for citation coverage and quotation fidelity, and a scripted build that generates the DOCX and its endnote apparatus.
Both are attached to the latest release and always point at the current revision. The book is corrected in place rather than re-versioned, so these links do not go stale.
README.md: this file.book/chapters/: every chapter as an individual Markdown file, plus the preface and the epilogue. Endnotes sit at the end of each chapter, with the source in the note.book/Why-Would-It-Keep-Making-Paperclips-Cover.jpg: the cover.LICENSE: CC BY-NC-SA 4.0.The PDF and EPUB are attached to the release instead of committed. Both are already-compressed archives that git cannot delta, so committing them would store a near-complete copy per revision and grow the repository permanently.
Not published: the source books, the digests, the research reports, the evaluator's briefs and raw written opinions, and the build pipeline. The chapters carry the evaluator's rulings in full; what is withheld is working material, not evidence.
Sources were consulted through September 2026. This subject moves, and the capability estimates move fastest of all: the arrival figures above are the single most volatile thing in the book, and every downstream number scales with them. The text documents the state of the argument at its writing date. Chapter 1 deliberately preserves an earlier, lower figure that later chapters overturn, so the revision is visible on the page rather than quietly tidied away.
Treat the near-term bets as the honest part. They resolve, and when they do you will be able to tell whether this book was calibrated or merely confident.
The book was written by Claude Code under my instruction, and the preface says so to the reader in its first sentence rather than burying it here. The three-model split is described above and in the preface. Editorial decisions about scope, ordering, framing and which arguments to include were mine. The probability estimates are not mine and not the writer's: they belong to a model that was deliberately kept ignorant of the text it was grading, and they are reproduced whether or not they flattered the chapter.
This is not a policy paper, a technical introduction to alignment, or a guide to using AI safely. It contains no code, no procedures, and nothing operational. It does not cover AI misuse by humans, which is a real problem and a different book. It does not tell you what to do, because the one honest thing to say about a 10 percent figure is that it is large enough to act on and small enough that nobody gets to be certain, and what follows from that is a political question this book has no standing to settle.
I am not employed by Anthropic or any AI lab, and this represents no company's views. The editorial framework and the structure are original to this work. The arguments are drawn from the cited corpus, and the numbers are the independent evaluator's.
Everything here (the chapter .md files, this README, and the cover) is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). See LICENSE.
You may share and adapt it for non-commercial purposes with attribution. Commercial reuse or redistribution of the written content, including republication as a book, a course, or any paid resource, is not permitted, and any derivative must carry the same license.