# Where Did Cain Get His Wife and Why It Still Matters A student once cornered me after a talk at Imperial College with the look of someone who had been saving this question for exactly the right moment. "If Adam and Eve were the first people," he said, "who did Cain marry?" He wasn't asking because he wanted to know. He was asking because he was certain I didn't have an answer — and that my not having one would prove something larger about the whole enterprise of taking Genesis seriously. I told him it was a genuinely good question. He looked suspicious. I think he was expecting either a confident dismissal or a fumbling retreat. What he wasn't expecting was the suggestion that we sit down with the text and read it slowly together. That, it turned out, was not the rhetorical experience he had come for. ## The Weapon Disguised as a Question The Cain's-wife problem has a longer pedigree than most people realise. Voltaire raised it. So did Thomas Paine. So have countless atheist polemicists since, and so does any number of Reddit threads at three in the morning. The question is genuinely interesting, and Christians have wrestled with it for centuries. But the form in which it usually arrives in public is not the form of curiosity. It is the form of a checkmate. The move goes something like this: present a difficulty the believer probably hasn't thought about, watch them stammer, and conclude that the whole book — and by extension the whole faith — collapses under elementary inspection. It's a debating tactic, not an inquiry. The Cain question works particularly well for this purpose because it has the satisfying feel of internal contradiction: the text seems to refute itself within four chapters of opening. I want to be careful here. I am not saying every person who raises the question is acting in bad faith. I have been asked it sincerely by anxious Christians, by genuinely curious agnostics, and by tired parents whose children have asked them at bedtime. The question itself is fine. What I am saying is that the rhetorical machinery built around the question has, over the centuries, hardened into something that often forecloses rather than opens conversation. To answer it well, we have to dismantle that machinery first. And the way to dismantle it is unglamorous: read the text. ## What Genesis Actually Says (and Doesn't) Genesis 4 narrates Cain's murder of Abel, his exile, and then this, in verse 17: "Cain knew his wife, and she conceived and bore Enoch." That's the whole reference. No introduction. No backstory. No "and where she came from was..." She just appears, like a stagehand walking calmly across a scene the audience is sure is supposed to be empty. A few verses later we get a genealogy. Then in Genesis 5:4 we read this, almost as a throwaway clause about Adam: "The days of Adam after he fathered Seth were eight hundred years; and he had other sons and daughters." Other sons and daughters. The text is explicit. Adam and Eve are not presented as having only the three named sons most Sunday schools mention. The narrative names the ones whose role matters for the story it is telling — Cain the murderer, Abel the victim, Seth the line through which the chosen lineage will run — and lets the rest stand under the general heading of "other sons and daughters." It is selective genealogy, not exhaustive demography. This is not a clever evangelical reading invented to dodge the difficulty. It is what the text says, in the passage immediately after the one that raises the question. The "problem" of where Cain's wife came from is largely created by readers who treat Genesis 4:17 as if Genesis 5:4 did not exist. The text also does not tell us how old Cain was when he married. It does not tell us how many generations had elapsed in the unnamed background. It does not tell us how rapidly the human population was multiplying. It tells us what it wants to tell us, and is rather indifferent to the questions we are anxious about. ## The Sibling Question Nobody Wants to Ask Now, having said all that, the most obvious reading — and the one with the longest history in Jewish and Christian tradition — is the one we tend to flinch at: Cain married a sister. Or possibly a niece, if some time had elapsed. The early human population, on the terms the text itself sets out, would have had no other option. This is where modern readers, including many Christians, get uncomfortable. We have strong incest taboos, and rightly so. We have laws against close-kin marriage. The thought of brother-sister union strikes us as not merely wrong but viscerally repellent. So we either reach for elaborate alternative theories — pre-Adamic peoples, a separate creation of other humans, a gap of millions of years populated by beings who do not count somehow — or we quietly hope nobody brings it up. But the text shows no embarrassment about this whatsoever. The Mosaic prohibitions on incest (Leviticus 18, 20) come thousands of years later in the narrative timeline, and they are framed precisely as new boundaries given to a particular people at a particular time. The patriarchs themselves operate within kinship structures that would horrify a modern registry office: Abraham marries Sarah, who is his half-sister (Genesis 20:12); Isaac marries his cousin; Jacob marries two sisters who are also his cousins. The text is matter-of-fact about all of this. There is also a reasonable biological argument here, which I offer cautiously because I am not a geneticist and the question is not primarily biological. The genetic problems of close-kin reproduction stem from accumulated mutations in the genome. A genetically pristine starting population would not face the same risks, and the prohibitions in Leviticus arrive at precisely the historical moment when, on any reading, those risks would have become serious. I do not raise this to settle the matter. I raise it to note that the embarrassment is ours, not the text's, and that the text's lack of embarrassment is itself a piece of evidence about what kind of literature we are reading. ## What Kind of Literature Is This Anyway This is the deeper question, and it is the one most modern arguments about Genesis crash into without realising. When we ask "where did Cain get his wife?" with the expectation of a forensic answer, we are treating Genesis as if it were a particular kind of book — a comprehensive historical chronicle of the sort a nineteenth-century European might write, with footnotes and demographic tables. It isn't that kind of book. It also isn't a myth in the dismissive sense, a fairy tale wearing theological clothes. It is something stranger and older: a theological history. It makes claims about real events and real people, but it makes them through a literary form shaped by ancient near-eastern conventions, by liturgical use, by the priorities of a covenant community trying to understand who God is and who they are. Genesis tells us that humanity has a single origin, that humanity is made in God's image, that humanity rebelled, that violence entered the world through that rebellion, that God did not abandon the rebels. These are the load-bearing claims. The text is not trying to give us a population census or a complete kinship chart. To demand that of it is to demand it become a different kind of book. This is not a dodge. The same hermeneutic governs our reading of any text. When the Psalmist says "the trees of the field will clap their hands," we do not stage a botanical investigation. When Jesus says he is the door, we do not check for hinges. Different parts of Scripture do different kinds of work, and a faithful reading attends to what each part is doing. Genesis 1-11 is doing something theological and historical at once, and it is doing it in a literary register that pre-modern readers understood better than we do. To put the same point another way: if Genesis were trying to be a genetics textbook, it would be a very bad one. Since it is trying to be something else, criticising it for failing at the thing it never set out to do is a category mistake. ## Augustine Already Worried About This It is worth remembering that Christians have been thinking about the Cain question for a very long time. Augustine, in Book XV of *City of God*, raises it directly. He notes that the early human family must have intermarried among siblings, observes that this was a necessity given the situation, and goes on to argue that the later prohibition of such unions reflects the development of human society and the proper widening of human bonds beyond the immediate family. "The good of the marriage bond," he writes, "is in the union it makes between persons who would otherwise be strangers." That is a fifth-century bishop, well before any of our modern controversies, working through the same question with the same texts, and arriving at substantially the same answer the tradition has held ever since. He is not panicked. He is not embarrassed. He is doing theology. This matters because there is a popular narrative — pressed by both aggressive secularists and certain types of fundamentalist — that any honest engagement with difficulties in Scripture is a recent concession, a kind of soft surrender to modern scepticism. It isn't. The tradition has always known these questions and has always been willing to think about them. The pretence that the church only started noticing problems in Genesis after Darwin is historically illiterate. Augustine noticed. Origen noticed. The rabbis noticed. They wrote about it. So when a student at Imperial corners me with a question Voltaire thought was devastating, I am not faced with a new crisis. I am faced with a very old conversation, and I have a great deal of company in it. ## The Real Question Cain's Story Is Asking Here is what strikes me most when I read Genesis 4 carefully: the wife is mentioned in passing in a single half-verse. The story is about something else entirely. It is about a man who killed his brother because his brother's worship was accepted and his was not, who lied to God's face about it ("Am I my brother's keeper?"), who was sent into exile, who feared he would be killed in turn, and who received from God, astonishingly, a mark of protection. Then he went off and built a city. That is what Genesis 4 is about. It is about the first murder, the corrupted worship that preceded it, the divine confrontation, the unexpected mercy, and the founding of urban civilisation by a man whose hands were still stained. It is, among other things, a chillingly sober account of where cities come from. Cain, restless, marked, afraid, builds Enoch. The first urbanist in Scripture is a fratricide. I think about that quite often, living in London. To get fixated on the demographic puzzle of his wife is, in a quite precise sense, to miss what the text is shouting at us. The text is asking: why do we kill our brothers? What does God do with murderers? Why are our cities founded by fugitives? How does mercy operate in a world this broken? Those are the questions Genesis 4 wants us to be sitting with. The wife is a footnote. We have made her the headline because the headline is more uncomfortable than the footnote, and we will do almost anything to avoid the headline. The Cain question, when used as a gotcha, is often a way of changing the subject. The subject is human violence and divine grace. The subject is that we are all, in some sense, descendants of Cain, building our cities under a mark we did not earn. Asking about his wife lets us off that hook. ## Honest Uncertainty as a Theological Virtue I want to make a pastoral point now, because the rest of this has been mostly intellectual and the intellectual case is not the most important case. The most important case is what this kind of question does to actual people in actual churches. I have watched bright young Christians lose their faith because they were taught, implicitly, that the Bible has a tidy answer to every question and that any admission of uncertainty is a step toward unbelief. So when they hit a question the tidy answers don't cover, and they always do, they conclude the whole thing was a con. The brittleness of the framework they were given becomes the cause of its collapse. This is a failure of teaching, not a failure of Scripture. Scripture itself is remarkably comfortable with what it does not tell us. The book of Job ends with God essentially refusing to answer Job's question and yet meeting him anyway. Paul tells the Corinthians that "now we see in a mirror, dimly" and that our knowledge is partial. Jesus tells the disciples there are things they cannot yet bear to hear. The biblical writers operate within a confident humility, confident about what God has revealed, humble about what he has not. A church that pretends to have tidy answers to every question will lose precisely the people who most need honest engagement. The student at Imperial does not need me to bluff. He needs me to tell him the truth: here is what the text says, here is what it doesn't say, here are the options the tradition has explored, here is what I think is most likely, and here is the larger thing the text is actually doing. If I bluff, I have not defended Scripture. I have betrayed it. Admitting uncertainty about secondary matters is not a weakness. It is what allows us to speak with conviction about the primary ones. ## What We Do Know, and Why It Is Enough So what do we actually know from Cain's story and the chapters around it? We know that humanity has a single origin, which is, incidentally, one of the most morally significant claims any book has ever made, and one that modern genetics has done more to support than to undermine. We know that human beings are made in God's image and that this image is not erased by sin, which is why even Cain, even the murderer, even the fugitive, bears a mark of divine protection. We know that violence entered the human story very early and has never left it. We know that grace entered the human story even earlier and has not left it either. We know that God speaks to murderers. We know he does not give up on the cities they build. We know that the line of promise runs not through the obvious heroes but through quieter figures, Seth, then Enosh, then forward toward a covenant family and eventually toward a particular Jewish carpenter who would also be killed by his brothers, and who would respond not with a city but with a kingdom. These are the things Genesis is telling us. They are more than enough. They are, in fact, a great deal more than we know what to do with. I never saw the student from Imperial again. I hope he found someone willing to sit with the actual text rather than the caricature. I hope, if he is still asking the question, that he is asking it now with more curiosity and less ammunition. And I hope, for him and for the rest of us, that we can recover the kind of reading that lets the strange, ancient, theologically dense literature of Genesis ask its own questions back to us, rather than answering only the questions we thought we already had. "He has shown you, O man, what is good; and what does the Lord require of you but to do justice, and to love kindness, and to walk humbly with your God?" (Micah 6:8) That includes, I think, walking humbly with the text.