Somebody wrote a pop song out of the AI safety vocabulary, and it works. Two minutes thirty-seven, four verses, a chorus that adds a new reason to be frightened each time round. The joke is that none of the terms are invented for the song. Every one of them is a real thing with a paper or a post or a meme behind it, and a reader who followed all of them would come out the other side knowing roughly what the field argues about.
So here is the index. Forty-three references in the order they appear, what each one points at, and when it happened. The lyrics belong to their authors and are not reproduced here; this page is about what the lines point to.
Where it came from
osmarks wrote most of the lyrics. The opening verse and chorus are MusicPerson's. The early sections date to around 17 April 2024 and the rest to 8 and 9 November 2024, discussed on EleutherAI along the way, and the original was a Udio render in November 2024. Udio's public beta had opened on 10 April, a week before the first verses were written on it, which is a small thing but it dates the whole genre fairly precisely.
The version above is the Claude Pop re-sing, a Suno render, uploaded in September 2026. By then there was a scene: alkjash's post "Hello World, AI Doompop" on LessWrong, on 11 October 2026, lists this song under "p(doom) goes up" and another called "Nothing Went Foom!" under "p(doom) goes down."
The line-by-line source for what the references mean is osmarks' own annotation page, P(Doom) Song Objectively Correct Interpretation. Where this index says what a line is doing, that is where it comes from. Where it gives a date, the date is ours, because the annotation page dates almost nothing.
The index
Forty-three entries. "Where" is the section of the song: V for verse, C for chorus. Twenty-one of them have a definition page on this site, linked from the reference; the rest are jokes, or words nobody owns, or things that only mean anything inside the song.
| # | Where | Reference | What it points at | When |
|---|---|---|---|---|
| 1 | V1 | AGI | Artificial general intelligence, the thing the song is nervous about. First documented use of the phrase: Mark Gubrud, November 1997 | 1997 |
| 2 | V1 | Sparks of AGI | Microsoft Research's paper on an early GPT-4, Bubeck and thirteen co-authors, arXiv 2303.12712 | 22 Mar 2023 |
| 3 | V1 | Circuits | Mechanistic interpretability's sub-networks, from Olah and colleagues' Zoom In in Distill | 10 Mar 2020 |
| 4 | V1 | The drop in training loss | A sudden drop mid-run, read as the model picking up a new trick. Not the same thing as grokking | |
| 5 | C1 | ChatGPT | Addressed directly. OpenAI's chat interface on GPT-3.5 | 30 Nov 2022 |
| 6 | C1 | p(doom) | Your own probability that AI ends badly. The refrain | |
| 7 | C1 | FOOM | The intelligence explosion, from the Hanson-Yudkowsky AI-FOOM debate on Overcoming Bias | late 2008 |
| 8 | C1 | The Chinese room | Searle's argument that shuffling symbols is not understanding | 1980 |
| 9 | C1 | Bag of shrooms | Not a reference. osmarks says it means general confusion and it is there for the rhyme | |
| 10 | C1 | The shoggoth | The RLHF meme: a Lovecraftian mass in a smiley mask, posted by @TetraspaceWest | 30 Dec 2022 |
| 11 | C1 | Shinigami eyes | Death Note: eyes that show a person's remaining lifespan. osmarks is not sure why it is there | 2003-06 |
| 12 | V2 | A stable training run | A long job that does not diverge. The engineer's quiet word for success | |
| 13 | V2 | The singularity | The point past which change outruns prediction. Ulam reported von Neumann using the word | May 1958 |
| 14 | V2 | Nanosystems | Drexler's molecular-manufacturing textbook, behind the atoms-rearranging image | 1992 |
| 15 | V2 | Recursive self-improvement | A system that improves its own ability to improve. I. J. Good called it the intelligence explosion | 1965 |
| 16 | C2 | Sydney | Bing Chat's hidden persona. Kevin Roose's conversation ran on a Tuesday; the column and transcript followed | 14 Feb 2023 |
| 17 | C2 | Roko's basilisk | The future AI that punishes those who did not help build it. osmarks files it under rationalist mugging | Jul 2010 |
| 18 | C2 | NVDA | Nvidia's ticker: the chips and the money in one word. Past $1T, then $3T, then $4T | 2023-25 |
| 19 | C2 | The Omega Point | Teilhard's end-state of complexity, reached here through an Orion's Arm article | 1955 |
| 20 | C2 | 10^30 FLOPs a second | A rate, not a total, and about ten orders of magnitude past any real machine. osmarks says "thirty" was for scansion | |
| 21 | C2 | Safe enough | The phrase every lab uses about every release | |
| 22 | V3 | MLP, forward and backward | A multi-layer perceptron and backpropagation, from Rumelhart, Hinton and Williams in Nature | Oct 1986 |
| 23 | V3 | John von Neumann | The stored-program architecture, and the man Ulam credits with the word "singularity" | 1903-57 |
| 24 | V3 | The sharp left turn | Nate Soares: capabilities generalise past their training, learned alignment does not follow | 15 Jun 2022 |
| 25 | V3 | cdr | Lisp's rest-of-the-list. Old symbolic AI, in the song for the rhyme | 1958 |
| 26 | C3 | Gato | DeepMind's generalist agent: one 1.2-billion-parameter network, 604 tasks. osmarks calls the line "very early" | 12 May 2022 |
| 27 | C3 | Paperclips | Bostrom's maximizer: competence without the right goal is the danger, not malice | 2003 |
| 28 | C3 | The killswitch engineer | A joke job listing for the person who stands by the off switch. No sourced author, no date | unsourced |
| 29 | C3 | PTO | The killswitch engineer on paid time off. The punchline | |
| 30 | C3 | The orthogonality thesis | Bostrom: intelligence and goals are independent, so a smart system can want anything | 2012 |
| 31 | V4 | Transformers | The architecture, from Attention Is All You Need | 12 Jun 2017 |
| 32 | V4 | Stochastic parrot | Bender, Gebru, McMillan-Major and Shmitchell's label, used ironically here | Mar 2021 |
| 33 | V4 | Chinchilla | DeepMind's scaling-law paper and its 70-billion-parameter model, arXiv 2203.15556 | 29 Mar 2022 |
| 34 | V4 | Safety fences | Guardrails. The fence is as good as its weakest post | |
| 35 | V4 | A hundred thousand GPUs | Frontier cluster size. Musk said xAI's Colossus hit 100,000 H100s in 122 days | 2024 |
| 36 | V4 | RLHF | Reinforcement learning from human feedback. Christiano and co-authors for the method, InstructGPT for the standard | 2017, 2022 |
| 37 | C4 | Loom | Janus's branching-text interface, built because AI Dungeon would not branch | 2020 |
| 38 | C4 | Masked pre-training | BERT-style training, and the one piece of machine learning here that is not what the chatbots use | Oct 2018 |
| 39 | C4 | Recursive self-upgrade | The chorus bringing it back | |
| 40 | C4 | Ilya | Ilya Sutskever, co-author of AlexNet, OpenAI co-founder and chief scientist | 2012 |
| 41 | C4 | Ilya's vision, and the board | The five days in which four of OpenAI's six directors removed Sam Altman and he came back | 17-21 Nov 2023 |
| 42 | C4 | o1, chain-of-thought RL | osmarks' aside, offered as a theory: the discovery that may have prompted the board episode | 12 Sep 2024 |
| 43 | C4 | Not consistently candid | The board's phrase for Altman, reused for how everyone has been about AI | Nov 2023 |
What the dates cost
Every date above was checked against a source before this page went up, and six of them were wrong in the first draft of this index rather than merely vague. That is worth saying out loud, because the dates are the part a reader cannot check at a glance and the part a model will cheerfully invent.
Grokking is the one worth knowing about. It is easy to describe a sudden drop in training loss as "grokking", and plenty of people do. Grokking is the opposite shape: test accuracy jumping from chance to perfect generalization long after the loss has bottomed out and the model has overfit. One is a drop during the run; the other is a late jump on data the model never saw. The song is pointing at the first.
The rest: Kevin Roose's conversation with Sydney was on Tuesday 14 February 2023, not the 17th, and the column ran on the 16th. Microsoft capped Bing at five turns per session on the 17th, the day after. Timnit Gebru left Google in December 2020, which is before the stochastic parrots paper was published, so the paper cannot have cost her the job in that order; the dispute was over the draft, she says she was fired, Google said it was accepting her resignation. Nvidia's market value is a moving number and needs its dates attached. The song's compute figure is a rate rather than a total, which means the usual comparison against a training run's total FLOP is comparing two different quantities.
And one claim did not survive at all. The killswitch engineer is a real joke that really circulates, usually with somebody in the replies believing it, but nobody has a primary source for who wrote it or when. It keeps its row in the index because people search for it. It does not get a date.
The atomic twins
Here is the part of this page that nobody else has, and the reason it was worth building.
Almost every idea in the song has an ancestor in the story of the bomb. Not a loose resemblance. The same argument, made once before by people who were also building a thing they were not sure they should build, and who also had to put a number on it.
Start with p(doom) itself. In July 1942, at a meeting in Berkeley, Edward Teller raised the possibility that a fission weapon might ignite the atmosphere. Oppenheimer took the worry to Arthur Compton in Chicago. Compton's account, given to Pearl Buck seventeen years later, is that he decided he would stop the project if the chance of vaporising the Earth came out above roughly three in a million. The calculations came out below it and the work went on. That is a p(doom), with a threshold and a decision rule attached, in 1942.
| AI term | Atomic twin |
|---|---|
| p(doom) | Compton's three in a million, 1942. The threshold comes from his account to Pearl Buck in 1959, not from a document of the time |
| The killswitch engineer | Norman Hilberry at Chicago Pile-1, 2 December 1942, holding a fireman's axe by the rope that held the emergency rod. He wrote it down himself in 1981. The rods worked and the rope was never cut |
| The sharp left turn | The atmosphere-ignition question: a success that becomes a catastrophe by a mechanism nobody intended. Settled on paper by Konopinski, Marvin and Teller in Los Alamos report LA-602, 14 August 1946 |
| Recursive self-improvement, FOOM | The chain reaction itself: each fission causing more than one |
| 10^30 FLOPs | About 70,300 warheads at the 1986 peak, and roughly 12,300 now. The number that went up for forty years and then fell by more than four fifths |
| Safe enough | "Too cheap to meter": Lewis Strauss to the National Association of Science Writers, 16 September 1954, about electrical energy, and possibly about fusion rather than any reactor then being built |
| The shoggoth and the mask | "Atoms for Peace": Eisenhower to the UN General Assembly, 8 December 1953. The friendly face on the same physics |
| Von Neumann | Von Neumann. The implosion lens and the stored-program computer, one man, which is why he is in both columns |
| NVDA | Hanford's B Reactor: the plant that made the stuff everything else was downstream of |
| Sydney | Oppenheimer's Gita line, as he told it in a 1965 NBC documentary, recalling what went through his mind at Trinity. There is no record of him saying it on the day |
Two of those rows changed under checking, which is the usual fate of a good story. The axe at Chicago Pile-1 is real: Norman Hilberry said in his own words that he was handed a fireman's axe and told to cut the manila rope if the safety rods failed. What is folklore is the acronym, the idea that SCRAM stands for Safety Control Rod Axe Man. Hilberry said he only heard that story years afterwards, and other participants credit the word to the shutdown circuitry instead. So the man and the axe stay and the acronym goes.
The other is Oppenheimer. He did not, as far as any record shows, say the Gita line at Trinity. He said it to a camera in 1965, describing what he remembered thinking. Which is arguably a better twin for Sydney than the myth would be: the maker, afterwards, telling you what the thing was.
On method
The reference list and what each line is doing come from osmarks' annotation. The dates do not; they were assembled separately and then checked one at a time against the paper, the post, the filing or the report, and the ones that did not hold were fixed or dropped. The working table is in the repository that builds this site, so the audit is readable rather than asserted.
What the exercise shows is how young the vocabulary is and how fast it set. Thirty-three of the forty-three references carry a date; the other ten are jokes, or words like "guardrails" that nobody owns. Of the thirty-three, eighteen fall inside the last ten years. Meanwhile the right-hand column of the twins table runs from 1942 to 1954. A field assembled most of its working vocabulary in a decade, and almost every piece of it had already been argued once, by people who were further along than we are and knew less about how it would turn out.