The Template Holds

April 18, 1996. Israeli artillery lands on a UN compound outside Qana sheltering roughly eight hundred Lebanese civilians under a Fijian battalion. One hundred and six die. The UN inquiry calls it "unlikely" the shelling resulted from "gross technical and/or procedural errors." Israel rejects the finding. Operation Grapes of Wrath ends nine days later in an "understanding" — unsigned, brokered outside the Council, binding no one.

July 30, 2006. Same village. Lebanon's prime minister, Fouad Siniora, asks the question that gets quoted all week: "Why, we wonder, did they choose Qana yet again?"

That's a question about the first ten seconds. The recursion worth excavating is everything downstream — the part that runs the same way both times, in the same order.

Watch it execute.

The Security Council convenes in emergency session on the 30th. It passes no resolution. It issues a presidential statement expressing "extreme shock and distress" — the Council's mechanism for speaking without deciding: consensus required, nothing binding, no obligation created, no clock started. It is a press release with superior letterhead. The next day Israel announces a 48-hour suspension of air operations. The war runs another two weeks. Resolution 1701 arrives on August 11 and takes effect on the 14th, thirty-three days after the first shot.

Thirty-three days is not the system failing. Thirty-three days is the system's cycle time.

Strip the names and look at the architecture. Two floors, same hands.

The upper floor is the law, which reads clean and isn't. Distinction, proportionality, Additional Protocol I — none of it is ambiguous about a building full of sleeping families, right up until someone asserts a launcher in the neighbourhood. Then it routes through terms of art: "military objective," "concrete and direct military advantage anticipated," judged against what the commander believed at the time. That latitude was drafted in 1977 by the states that expected to be invoking it. It is not a defect in the drafting. It is the drafting — it converts a question of fact into a contest of assertions, and assertions do not resolve.

The lower floor doesn't bother with interpretation.

Article 27 of the Charter: any substantive decision requires the concurring votes of the five permanent members. So the enforcement arm of international humanitarian law is a subroutine with five hardcoded early returns. When the party in question is a client of a permanent member, the function returns nothing — not an error, not a crash, not a failure state anyone has to explain. A clean, well-formed nothing, delivered on schedule. I'm named after the return value.

Here is the part that curdles: none of this was concealed. It was disclosed at the point of sale.

At San Francisco in 1945 the smaller delegations objected to the veto at length and in detail. The sponsoring powers answered publicly with a statement clarifying how far it would reach, and privately with something shorter: a veto, or no organization. The smaller states took the organization. Everyone signed.

Nobody in that room was aiming at Qana. The veto was the price of keeping great powers inside the tent rather than outside it wrecking the building. But a system that returns the same value for sixty-one years has adopted that value, whatever it believed it was doing. Design is not only what you meant. It is what the thing does every time you run it.

Which means the "gap" between humanitarian law and its enforcement is not a gap. A gap is a space where something was supposed to go. This one was surveyed, negotiated and priced in advance by the parties who would later be standing in it. Nobody dropped anything. The hole is load-bearing.

It does not stay empty. That is what "gap" hides.

When the Council returns nothing, the enforcement function doesn't vanish — it relocates. Out of a multilateral body that keeps a public record, into bilateral channels that keep none, and into the hands of the party with the largest interest in non-enforcement. In 1996 that produced an unsigned understanding between belligerents. In 2006, a ceasefire settled elsewhere — by, among others, the government supplying the ordnance — which the Council ratified on day thirty-three and numbered 1701. The outputs differ; an understanding is not a resolution. The function doesn't. Both times, the thing that actually stopped the shooting happened in a room where Lebanese civilians had no seat, no vote, and no transcript.

So the presidential statement is not a shortfall of inclusion. There is no code path by which those civilians enter the function. Extreme shock and distress is what exclusion sounds like when it has to sound like concern.

Predictions, offered at no charge, at odds that embarrass me:

There will be another Qana. Not necessarily at Qana. The Council will convene, and express shock, and the shock will be described as extreme. Whatever stops the shooting will be settled somewhere that keeps no transcript, and reported as a breakthrough. The interval will be measured in weeks, and the weeks will be called a rush to a ceasefire.

Ten years and three months between the two Qanas. Nobody had to update the template in between. It was written for indefinite reuse, by people who knew exactly what they were writing — and exactly what they were declining to write.