A king sees a woman bathing from his roof and asks who she is. She is the wife of one of his soldiers, a man called Uriah, who is currently at the siege.
So the king writes to his general: "Put Uriah opposite the enemy where the fighting is fiercest and then fall back, and leave him to meet his death."
Then he sends Uriah to deliver it.
The general does as instructed. The city sallies out, some of David's guards fall, and Uriah dies with them. A dispatch comes back with all the news of the battle. When the mourning period is over, David sends for the widow, and she becomes his wife and bears him a son.1
That is the passage Greene prints in the margin of Law 26, headed David and Bathsheba, attributed to 2 Samuel. He offers no comment on it whatsoever.
The order is worth reading as an operational document, because it is unusually precise.
Put Uriah opposite the enemy where the fighting is fiercest. That is placement.
And then fall back. That is the killing.
Neither instruction is a killing on its own. Placing a soldier where the fighting is hardest is a command decision. Withdrawing support from a position is a command decision. It is only the sequence that constitutes murder, and the sequence is composed entirely of ordinary military acts.
Which is exactly the property Law 26 is built around. The chapter's premise is that the powerful must never appear as the agent of anything unpleasant, and David's order achieves that in the most economical way available: the death is executed by the enemy, arranged by a general, and consists of two legitimate orders in a particular order.
Nobody has to lie. The dispatch that comes back reports a battle, and it is a true report of a battle.
Joab is the chapter's cat's-paw and he is a strange one, because he is not a dupe.
Greene's instrument is normally someone who "will therefore be unlikely to realize how he or she is being used."2 Joab realises completely. He is given the written instruction, reads it, and implements it with a professional's adjustment — he stations Uriah "at a point where he knew they would put up a stout fight."1 The improvement is his own.
He also absorbs a cost the text records without comment: "some of David's guards fell" alongside Uriah. To make the death look like a battle, Joab spent other men.
So this is not the cat's-paw of the fable, and it is not quite a scapegoat either. It is the arrangement Greene's chapter reaches for repeatedly and never names — an instrument who knows, complies, and is protected by the fact that his actions are indistinguishable from his job.
That is a more robust position than any dupe occupies. A dupe can realise. Joab has nothing to realise.
Read the first line of the passage again, with the chapter's own Keys in mind.
"At the turn of the year, when kings take the field, David sent Joab out with his other officers and all the Israelite forces… while David remained in Jerusalem."1
Eighteen lines below the marginal, Greene's own text says: "The truly powerful, on the other hand, seem never to be in a hurry or overburdened. While others work their fingers to the bone, they take their leisure. They know how to find the right people to put in the effort while they save their energy and keep their hands out of the fire."3
The biblical narrator opens by noting, pointedly, that this is the season kings go to war and this king stayed home. It is the first sentence of the story and it is the cause of everything in it — the roof, the view, the enquiry, the letter.
Greene's advice and the text's indictment are the same observation, printed within twenty lines of each other, pointing in opposite directions. The chapter recommends the posture the passage identifies as the origin of the crime.
There is no evidence he noticed.
Now the thing that makes this the sharpest marginal in the law.
Law 26's entire promise is that the instrument keeps your hands clean. Ts'ao Ts'ao's soldiers stopped grumbling. Cesare appeared as the man who cleaned Romagna up. Cleopatra was never seen destroying her family. Louis Howe absorbed twenty years of it. In every case the operator's involvement disappears from the account.
The text Greene prints is scripture that has named David the murderer for three thousand years.
The technique worked perfectly at the moment of use. Uriah died in battle, the dispatch was accurate, the marriage was legal, and there was no contemporaneous accusation. And the operation is nonetheless the single most famous instance of a powerful man arranging a death through an intermediary in the Western canon, taught to children, and permanently attached to his name.
The chapter's success criterion is whether the operator was threatened. This case satisfies it completely and demonstrates that satisfying it is not the same as getting away with it.
There is a second detail that makes the omission stark. Greene's attribution reads 2 Samuel, 11–12.4 The quotation stops in the middle of chapter 11 — at the marriage and the son. Chapter 12 is the prophet Nathan arriving to tell David a parable about a poor man's lamb, and then saying: you are the man. The citation advertises the consequence and the excerpt cuts before it.
There is a decision available to you that would solve a problem, and every individual component of it is defensible.
You would move someone onto a project that is already struggling. You would decline to backfill a role. You would decide, on genuine grounds, not to extend a contract. Each of those is a normal management action that you could justify in any room, and you know — not as a plan, more as a background awareness — how they compose.
That composition is the thing to look at, and looking at it is difficult for a specific reason: there is no moment in the sequence at which you have to decide to do the bad thing. There is a Tuesday where you approve a staffing change and a Thursday six weeks later where you decline an extension, and in between there is nothing.
So use the test the passage supplies. Write it down as one instruction. Not the emails, not the approvals — one sentence containing the placement and the withdrawal together, as David's letter does. Put him on the failing project and then decline the support he'll ask for.
You will not want to. That reluctance is the entire diagnostic, and it arrives before any of the reasoning does.
And the second thing the passage supplies, which is harder. David's letter was carried by Uriah. The person you are constructing this around is, right now, doing something for you — attending the meeting, sending the update, being reasonable about the change. They are moving the pieces themselves, and their cooperation is what makes the sequence look like ordinary work.
If you notice that, you have noticed the whole thing.
The marginal column in this book is where the best-sourced material sits, and it is consistently in tension with the body beside it. This is the most extreme instance in the cluster.
There are two plausible readings and neither is flattering.
Either it is illustration — a famous instance of using an instrument to do dirty work, selected for recognisability, with its narrative frame simply not registering.
Or it is decoration — a well-known biblical passage placed for texture, in a book whose marginal columns run fables, proverbs and quotations set off from the argument.
The second is more likely, given how the book uses margins generally. But it produces the same result either way: a text whose entire purpose is the moral condemnation of a killing-by-intermediary is printed inside a chapter recommending killing-by-intermediary, and the chapter takes nothing from it.
This is now the fourth or fifth instance the build has logged of a law containing its own refutation, printed pages apart.
Worth stating, since Greene's citation gestures at it and his excerpt omits it.
The prophet Nathan comes to David and tells him a story about a rich man with many flocks who takes a poor man's single ewe lamb — a lamb the poor man had raised with his children — to feed a traveller. David is furious and pronounces judgement on the rich man. Nathan says: you are the man.
The mechanism of the rebuke is worth noticing on its own terms. Nathan does not accuse. He routes the accusation through a story about a third party, so that David delivers the verdict himself before discovering whose case it is.
That is Law 26's own technique — third-party dissociation, the guard going home because the story is about someone else — used to break Law 26's own operation. The chapter's method appears on both sides of the case it prints, and Greene quotes neither.
Attribution: named work, named books. Old Testament, 2 Samuel, 11–12, quoted at length.4 As with every marginal in this cluster, better sourced than the body text.
🚩 The excerpt is cut where the consequence begins. The citation range includes chapter 12 and the quotation ends inside chapter 11. Whether deliberate or editorial, the effect is that the passage as printed ends on David's success.
🚩 SECONDARY WITHOUT PRIMARY does not apply here, and that is itself notable. This is one of the very few places in the book where a reader can check the source, because the source is named and universally available. The contrast with the body text — Ts'ao Ts'ao's dialogue, Cleopatra's private knowledge, Louis Howe's twenty years, all uncited — is stark.
Historicity is a separate question and not this page's. Whether a historical David issued such an order is contested; the marginal is a literary and canonical text, and its force in the chapter comes from its status as a story everyone knows, not from its evidential value.
Open question. The technique succeeded and the record survived. What, if anything, in Greene's method accounts for the difference between escaping consequence and escaping the account — and does any case in the book distinguish them?
Every successful case in Law 26 is a terminal encounter with a forgetting audience. An army disperses. A province is handed on. A court moves to the next favourite. The technique's apparent reliability is partly a property of the cases Greene selected, all of which end.
The Uriah narrative does not end. It was written down by people who took the victim's side, and it has been read continuously since.
Set that against the chapter's own Reversal, which warns that the screen may be lifted and the operator seen as the puppet master.5 David's screen was never lifted in his lifetime by anyone with power over him — the person who lifted it was a prophet with no army, and the lifting took the form of a story, which is the same instrument the chapter recommends.
So the case supplies a failure mode Greene's Reversal does not contain. Not you will be found out and destroyed. Rather: you will not be found out, and the account will outlive you anyway, because somewhere in the arrangement there is a person who saw it and can write.
Behavioral mechanics — Law is Universal; Enforcement is Political: Plausible Deniability as Essential Escalation Framework
That page argues that states rarely commit crimes in ways that leave undeniable evidence. They commit them in ways that generate alternative narratives — explanations that are technically possible, hard to disprove, and amplified by media already under control. Deniability is not an afterthought bolted on to an atrocity; it is the architecture that permits escalation in the first place, because without it each step would meet resistance.
David's operation has the first half of that architecture and none of the second, and the gap is the insight.
The alternative narrative is impeccable: a soldier died at the fiercest point of a siege, alongside other guards, in a battle that genuinely happened, reported in a genuine dispatch. Nothing about that account is falsifiable, and there was no contemporaneous accusation.
What is missing is everything the deniability framework says makes the architecture hold. There is no control of the record. There is no apparatus suppressing an alternative account. And critically, the instruction exists in writing and passes through three pairs of hands — David's, Uriah's, Joab's.
So the case separates two things usually run together. Deniability at the moment of the act and deniability across time are different properties with different requirements. The first needs a plausible story, and David had a perfect one. The second needs control of who gets to write — and a king who commands an army does not, by that fact, command the account.
Which reframes the modern versions the deniability page describes. Their distinguishing feature is not better stories. It is that the architecture extends to the record, and the story is only the visible layer of a system whose real work is making sure nobody with the facts is ever in a position to set them down.
Psychology — Emancipation From Sacrifice: Second-Order Killings and Modernity's Self-Definition
That page describes something extraordinary happening over centuries: a civilisation becomes conscious of its own sacrificial foundation and deliberately rejects it. Not drift — Enlightenment philosophers attacking sacrifice as barbarism, reformers declaring the killing of humans an abomination, movements organised specifically to end ritual slaughter.
The Uriah narrative is an early instance of the machinery that makes that possible, and seeing it that way explains something Greene's chapter cannot.
Law 26's technique depends on a particular property of the world: that when a powerful person arranges a death through an intermediary, the surviving account will be the powerful person's. Ts'ao Ts'ao's soldiers stopped grumbling and the version that survived was his. Cesare appeared as the man who cleaned up Romagna. That is not a fact about cleverness; it is a fact about who wrote things down.
2 Samuel is a text in which the account belongs to the victim. Uriah is named. The order is quoted. The king is condemned by name in his own scripture, and the condemnation is the point of the passage.
What the pair yields is a historical scoping condition on the whole law. Greene presents his techniques as timeless — the book's own warrant is three thousand years of unchanging human nature. But the scapegoat and the cat's-paw both require an audience that will not preserve a victim-centred account, and the emancipation page describes the long process by which preserving exactly that account became a civilisational habit.
Which suggests the technique has not been getting harder because people are more suspicious. It has been getting harder because the record changed sides, and that is a change in infrastructure rather than in psychology — the one kind of change a book premised on unchanging human nature has no way to see.
Sharpest implication. David's arrangement satisfied every criterion Law 26 sets. The death was executed by enemies, arranged by a general, composed of legitimate orders, reported accurately, and never contemporaneously accused — and it is the most famous murder-by-proxy in the Western canon. Which means the chapter is optimising for the wrong variable. Escaping consequence and escaping the account are different problems, and every technique in Law 26 addresses only the first, because every case Greene selected has an audience that dispersed.
Generative questions