The history behind the conquest, read cold — before anyone asks whether it was just.
Before asking whether the conquest of Canaan was just, this study lays out — deliberately cold — the long road that runs up to it: the curse marked on Canaan's line, the genealogy that names the peoples Israel will face, a judgment deferred four hundred years, the wall built around one family, and a nation slowly formed in the wilderness. It then lets archaeology speak, where the mainstream finds no swift external conquest as Joshua narrates it but an Israel emerging largely from within Canaan. The piece sets the stage and weighs nothing — and says plainly that the moral question it raises is left open for its companion, so you should finish it still uneasy.
This study goes in cold. It lays out the history that runs up to the conquest of Canaan — the curse, the genealogy, the four-hundred-year delay, the wall built around one family, the long formation in the wilderness — and it does so without yet asking whether God comes out of it good.
That question is real, and it is the whole work of the companion piece. Here the warm reading is deliberately withheld. What you are reading is closer to a timeline than a verdict: what the text says happened, in order, plus what archaeology says about whether it happened that way at all. We read this as Scripture and within the orthodox frame — but the evaluation waits. You should finish this piece still uneasy. That is the point.
Most arguments about the Canaanite conquest begin at the worst verse and stay there. That is fair as moral reaction, but it is poor as reading, because the text does not begin there. By the time Israel crosses the Jordan, the narrative has been building toward that land — and away from those nations — for eleven chapters of Genesis and four books of law. The slaughter does not fall out of a clear sky. It falls at the end of a road.
Laying out that road is not a defense. A long backstory can make an act more comprehensible without making it more excusable — and we will not pretend otherwise. The purpose here is narrower and more honest: to put on the table everything the next piece will have to reckon with, so that when the hard verses come, they come with their full context attached rather than stripped of it. Nothing in this part resolves anything. It only sets the stage.
The thread begins not with a nation but with a name. After the flood, Noah plants a vineyard, becomes drunk, and lies uncovered in his tent. His son Ham "saw the nakedness of his father, and told his two brothers"; Shem and Japheth cover Noah without looking. When Noah wakes and "knew what his youngest son had done to him," he pronounces a curse — and the curse falls not on Ham but on Ham's son:
"Cursed be Canaan; lowest of slaves shall he be to his brothers."
Genesis 9:25 · NRSVue
The text has already told us, twice, that "Ham was the father of Canaan" (Gen 9:18, 22). It is one of those tags Scripture repeats when it wants you to hold two things together. Whatever happened in that tent, the consequence is routed deliberately onto the Canaan line — the very people Israel will later be sent to dispossess. The conquest narrative is, in part, the long unwinding of this sentence.
Why Canaan and not Ham? The text does not say. That silence is worth sitting in rather than filling. Several readings have been offered, and none is stated in the verse itself: that the curse is the narrator's etiology, explaining from Israel's later vantage why the Canaanites are subjugated; that an offense by Ham against his father is fittingly answered in Ham's own son; or that the act behind "saw his nakedness" was graver than the words admit. The text gives no verdict, and this study will not invent one.
For the road ahead, the disputed details matter less than the fixed point: the curse marks the Canaan line, and the narrative will keep that line in view from here to the conquest.
The next chapter draws the map. Canaan, the text says, "became the father of Sidon his firstborn, and Heth, and the Jebusites, the Amorites, the Girgashites, the Hivites" and the coastal peoples north to Hamath (Gen 10:15–18). Set that list beside the recurring conquest formula — "the Canaanite, the Hittite, the Amorite, the Perizzite, the Hivite, the Jebusite, the Girgashite" — which appears roughly twenty times across the Torah and Joshua, and the overlap is plain. The nations Israel is later sent against are, in large part, the descendants the genealogy has just named from the cursed son.
The overlap is real but not total. The Perizzites and the Rephaim and Kenites of the fuller list in Genesis 15:19–21 do not appear in the Genesis 10 Canaan genealogy. The "Canaanite nations" of the conquest and the Canaan line of Genesis 10 intersect; they are not identical sets. The trace is genuine, but it is a family resemblance, not a closed syllogism.
This is the first place a reader should feel the moral nerve, not relief. A genealogy that runs "cursed ancestor → these specific peoples → the targets of holy war" can read as careful history. It can also read as exactly the kind of after-the-fact justification by ancestry that the conquest's critics find most damning. Both readings are available, and this piece does not choose between them. It only notes that the text itself keeps the lineage intact and in view.
Long before the conquest, in a night-vision given to Abram, the whole arc is foretold — and given a reason for its timing:
"Know this for certain, that your offspring shall be aliens in a land that is not theirs, and shall be slaves there, and they shall be oppressed for four hundred years… And they shall come back here in the fourth generation, for the iniquity of the Amorites is not yet complete."
Genesis 15:13–16 · NRSVue
Two things are doing work in that last clause, and they pull in opposite directions. On one hand, the conquest is explicitly framed as judgment delayed, not judgment rushed: the land's peoples are given four centuries before the reckoning, because their "iniquity is not yet complete." On the other hand, the same sentence calmly forecasts four hundred years of slavery for Abram's own descendants as the price of that delay. The clock that spares Canaan for a time is the same clock that runs out slowly on Israel in Egypt. The text offers a reason for the timing; it does not offer a comfort for those living inside it.
This is the hinge that ties the two hard texts together — Egypt's long oppression and Canaan's eventual destruction are timed to one another in a single verse. The companion piece will have to hold both. Here we only mark the mechanism: a deferral, stated as deliberate, with a cost attached to the deferral itself.
Between the promise and the conquest, the narrative builds a wall. Abraham makes his servant swear not to take a wife for Isaac "from the daughters of the Canaanites" (Gen 24:3); Isaac charges Jacob the same way (Gen 28:1–2). In Genesis the reason is mostly implied — kindred, not Canaan. The explicit rationale comes later, in Deuteronomy, and it is protective rather than ethnic:
"Do not intermarry with them… for that would turn away your children from following me, to serve other gods."
Deuteronomy 7:3–4 · NRSVue
Be careful not to read Deuteronomy's stated reason back into the Genesis oaths as though Genesis said it. The nearest Genesis gives is God's foreknowing intent that Abraham "charge his children… to keep the way of the LORD" (Gen 18:19). The "lest they fall away" logic is explicit only later. Keeping that straight matters for honesty about what each text actually claims.
But the rupture in this family is older than any of Esau's choices. The narrator dates it to the womb. When Rebekah's twins "struggled together within her," she is given an oracle that reads the unborn children as peoples before either has drawn a breath:
"Two nations are in your womb, and two peoples born of you shall be divided; the one shall be stronger than the other; the elder shall serve the younger."
Genesis 25:23 · NRSVue
The point is not which brother is righteous — the narrative is at pains to make neither one a hero. Jacob is named for the grab: he is born "gripping Esau's heel," and the name itself means he supplants (Gen 25:26). He trades bread for a famished brother's birthright, then steals the blessing meant for Esau by outright deception (Gen 27), and Esau's grief and rage are recorded as wrongs really done to him. What the text fixes is not a verdict but a structure: two peoples set at odds from before birth, the division foretold and then lived out for the whole length of the story — Edom barring Israel's road (Num 20:14–21), the bitter oracles against Edom (Obadiah; Mal 1:2–3, which Paul later reads for election, Rom 9:10–13), and the line surviving as the Idumeans of Herod in the Gospels.
The two registers diverge here just as they will at the conquest (§VI). The individual twins of Genesis leave no direct archaeological trace; the patriarchal narratives are not recoverable from the spade. But Edom and Israel as peoples are firmly attested, and so is their long hostility — a distinct Edomite kingdom to Israel's southeast, recurring war and subjugation across Samuel, Kings, and the prophets, the line persisting as Idumea into the Roman period. The womb-oracle is the narrator's etiology of a rivalry the later record, biblical and extra-biblical, treats as real and durable. Whether a struggle is caused by being foretold, or the foretelling is written from its known outcome, the text does not say — and this study will not decide it.
One son steps over the wall. Esau "married into the land" — Hittite wives who "made life bitter for Isaac and Rebekah" (Gen 26:34–35). The text presents his line as the one that did not keep separate, and within two generations that line produces a name: Amalek, Esau's grandson (Gen 36:12), who becomes Israel's perennial enemy — the people who, in Deuteronomy's indictment, "attacked you on the way… and struck down all who lagged behind," preying on the weak and the tired (Deut 25:17–18). Whether crossing the wall is the cause of that enmity is interpretation, not the text's stated claim. What the text states plainly is the genealogy and the recurring hostility, intact from Genesis all the way to Haman the Agagite in the book of Esther.
Following a bloodline from a curse to an enemy people is precisely the move that can curdle into justifying violence by ancestry — the moral charge the conquest's critics press hardest. This study reports the lineage because the text foregrounds it; it does not endorse the inference that descent determines guilt. The trace contextualizes. It does not, and cannot, license.
The middle of the Torah reads, structurally, like preparation for something. Exodus ends with the tabernacle — God moving in to dwell among the rescued people (Exod 25–40). Leviticus is consumed with consecration, climaxing in the Holiness Code and its refrain, "You shall be holy, for I the LORD your God am holy" (Lev 19:2). Numbers opens with a census taken expressly for war (Num 1), orders the camp, and turns the people toward the land.
Read as a sequence, it is the formation of a nation meant to bear a particular character and to live next to a holy presence — "a priestly kingdom and a holy nation" (Exod 19:6). The "preparing them for something" is not a guess; the text names the goal. But the preparation is not tidy. The same book of Numbers that marches toward the land is also the book of the hardest in-house judgments — the rebellion of Korah, the plagues, a generation that does not enter. Formation and failure run together the whole way. A reader looking for a clean upward arc will not find one here.
So far this is the text's own account. Historical-criticism and archaeology pose a separate, blunt question: is there a swift, total external conquest in the dirt at all? Largely, the answer from mainstream archaeology is no — not as narrated. This belongs in the backdrop because reading "cold" means letting the ground speak as plainly as the page.
The earliest mention of "Israel" outside the Bible, the Merneptah Stele (c. 1207 BCE), already places an entity called Israel inside Canaan — as a people, not an invading army on its way. In the same period, surveys find more than two hundred new highland villages appearing in the central hill country between roughly 1200 and 1000 BCE, but with material culture largely continuous with their Canaanite neighbors — similar pottery and architecture, no signature of a mass migration from outside.
On this reading (associated with Israel Finkelstein and others), early Israel emerged from within Canaanite society — pastoralists and displaced villagers coalescing in the highlands after the Late Bronze collapse — rather than arriving as a unified force that destroyed the cities. The conquest as a rapid military campaign is, on this view, largely later theological narrative rather than remembered event.
A minority of scholars (e.g., Bryant Wood) argue for re-dating Jericho's destruction to around 1400 BCE to fit an early conquest. The mainstream judgment, following Kathleen Kenyon's excavations, is that Jericho's last major destruction belongs to the Middle Bronze Age (c. 1550 BCE) and that the site was essentially unoccupied at the conquest's traditional date — and most specialists reject Wood's re-dating. The site of Ai (et-Tell) shows a similar gap. The destruction layer at Hazor is the strongest single piece of physical evidence sometimes read in the conquest's favor, but it does not establish the campaign as a whole.
This cuts in a direction worth stating carefully. If the conquest did not happen as a sweeping historical genocide, the moral weight does not simply vanish — it relocates. A text that commands and commends the slaughter as the will of God is a theological difficulty whether or not the swords ever fell that way. The archaeology can relieve the historical horror; it cannot, by itself, relieve the textual one. That is a problem for the next piece. Here it is enough to have let the ground complicate the page.
"They shall come back here in the fourth generation — for the iniquity of the Amorites is not yet complete."
Genesis 15:16 · the clock that times both hard textsThat is the road. A marked line, a mapped people, a deferred judgment with a cost, a wall and the one who crossed it, a nation slowly formed — and a serious question about whether the campaign happened as written at all. None of it has yet been weighed. The weighing — the commands themselves, read at full strength, and the question of whether the God of the warm portrait survives contact with them — is the work of Part 2.
Sources
The Holy Bible, New Revised Standard Version, Updated Edition (NRSVue), 2021.
Position: Mainline Protestant translation committee; ecumenical, critically based text.
Finkelstein, I., & Silberman, N. A. (2001). The Bible Unearthed. Free Press.
Position: Historical-critical / archaeological — early Israel emerged from within Canaan; conquest largely non-historical as narrated.
Kenyon, K. (1957). Digging Up Jericho; and subsequent dating discussions.
Position: Archaeological — Jericho's major destruction dated to Middle Bronze; occupation gap at the traditional conquest date.
Wood, B. G. (1990). "Did the Israelites Conquer Jericho?" Biblical Archaeology Review.
Position: Conservative evangelical — argues for re-dating Jericho to c. 1400 BCE; a contested minority view.
The Merneptah Stele (c. 1207 BCE), Egyptian Museum, Cairo.
Position: Primary artifact — earliest extra-biblical mention of "Israel," located in Canaan.