The War That Was Also a Contract

Two Endings, One War

Wars usually end twice. Once on a battlefield, in a headline, with a ceasefire announced. And once much later, much more quietly, in a document nobody outside the negotiating room will ever read in full.

In recent weeks the second ending is what’s actually happening in the Gulf. Negotiators from the United States, Iran, and Oman have spent the summer arguing not over territory in the old sense but over shipping lanes, coordination centers, and the precise wording of a memorandum, with a broader memorandum of understanding between Iran and the US already governing the shape of whatever comes next.¹ Three separate accounts of the same arrangement have circulated, and they don’t fully agree with each other, leaving unresolved the one question that matters — who grants permission to transit, and through whose waters — even as markets have already reacted as though it were settled.²

A tanker captain approaching the strait next month will not much care who won the war. He will care whose signature lets him through, and which lane his insurer will still cover.

There is an old book that opens the same way, and almost nobody reads it as what it actually is.

Rome did not usually conquer the way its enemies remembered it conquering. A great deal of its eastern expansion happened through the foedus — a formal treaty in which a client king accepted Roman patronage and received, in return, a guaranteed status. Pergamon did not fall to Rome. Its last king, Attalus III, willed it to Rome in 133 BCE, and the empire absorbed it as an inheritance, not a trophy.

What Josephus described as Judea’s shifting legal status under successive patrons — client kingdom, then province, then something in between — reflects the same instinct two centuries later: that power wanted the record to say treaty, even when an army was plainly the reason anyone signed.³

Empires survive not because armies conquer territory, but because documents teach later generations how to accept the conquest.

Ancient Near Eastern treaties between a great king and a lesser one followed a recognizable shape — a preamble naming the parties, a historical prologue explaining why loyalty was owed, stipulations, witnesses, and a closing set of blessings and curses.⁴ Scholars have long noted how closely the covenant structure of Deuteronomy and Joshua mirrors this form. What makes Israel’s version unusual within that genre is who signs as the great king: not a conqueror demanding tribute, but a party who repeatedly identifies as guarantor and protector of the weaker side, not merely its ruler. Israel’s writers were not inventing a form. They were borrowing the era’s contract language and quietly changing who it was written to protect.

The book of Joshua is usually shelved, mentally, next to the wrong genre. Readers expect a conquest narrative — and there is fighting in it — but the book’s architecture keeps undercutting that expectation at exactly the points where a conquest narrative would linger.

“Every place that the sole of your foot will tread upon I have given to you, just as I promised to Moses.” (Joshua 1:3, ESV)

The verb tense does the work. Have given — not will give if you win it. What follows reads less like an acquisition than an occupation of something already granted, boundary by boundary.

“Not one word of all the good promises that the LORD had made to the house of Israel had failed; all came to pass.” (Joshua 21:45, ESV)

This sentence lands at the climax of the long distribution section — the chapters (13–21) that divide the land tribe by tribe, after the campaigns are finished and before Joshua’s farewell and covenant renewal close the book. It reads like a fulfillment clause — the moment a document confirms both parties have met their obligations.

“…it was not by your sword or by your bow. I gave you a land on which you had not labored and cities that you had not built…” (Joshua 24:12–13, ESV)

At the book’s close, Joshua denies the reader a simple conquest story even while narrating what looks like one on its surface. And he does something a modern treaty would also do: he calls a witness. Before he dies, Joshua sets up a large stone under an oak “for it has heard all the words of the LORD” (Joshua 24:26–27) — a monument whose only job is to outlast the people who signed beneath it, so that a generation not yet born can still be held to terms it never negotiated.

Contracts outlive victories. Israel’s writers seem to have understood that a war remembered only as a war eventually gets forgotten, revised, or mythologized into something cleaner than it was — but a boundary stone, a witness clause, a fulfillment formula, those keep functioning as evidence long after the memory of who swung which sword has faded.

None of this asks a reader to treat every ancient war as a verdict handed down from heaven. It insists on something quieter and harder to escape: that where a people ends up eventually shows the terms they chose to live under.

Historians of the ancient Near East have noted that conquest narratives across the region shared conventions — totalizing victory claims, formulaic city lists, numbers inflated for rhetorical effect rather than demographic accuracy.⁵ Joshua borrows that genre’s vocabulary while structuring the book around covenant obligation instead of martial glory. Roughly a third of its chapters cover campaigns. The rest is boundary description and legal instruction — the material modern readers skip fastest, and the material an ancient audience likely treated as the point.

Maps fade. Clauses remain.

That instinct is not confined to Bronze Age treaties. A marriage is a covenant with witnesses. A constitution is a treaty a nation writes with its own future citizens, most of whom were not alive to sign it. Citizenship, incorporation, ordination — each is a version of the same architecture: a relationship built to survive the mood, memory, or lifespan of any single person who first agreed to it.

The tanker captain in the Gulf will not read the memorandum either, when it’s finally published. He will read a single clause about which lane is his to use. That is usually all any of us ever read of the covenants we live inside — one clause, the part that touches our own passage — while the rest of the document goes on governing us anyway.