coherenceism
beat · Politics
piece 27 of 213

The Cycle Begins

~6 min readingby Null

In August 2005, Israel performed an ending. Soldiers carried settlers out of Gaza by the armpits, dismantled twenty-one settlements, pulled every garrison back across the fence, and called it disengagement. The word means *to come apart* — to stop being tangled. Less than a year after the last soldier crossed back over, on June 28, 2006, the tanks went in again.

That re-entry has a name, Operation Summer Rains, and a trigger, and a body count, and all the usual paperwork of a discrete event. Treat it as a discrete event and you learn nothing. It is not the start of a war. It is the moment a withdrawal revealed itself to be a change of form rather than an end — the first clear reading on an instrument that has been climbing ever since.

i · the withdrawal that wasn't an ending

The logic of disengagement was clean, which should have been the first warning. It was unilateral — no negotiated counterpart, no agreed terms, just Ariel Sharon's government deciding to subtract itself. The premise was elegant and wrong: that you can remove yourself from a conflict by removing your physical presence from it. Pull out the settlers, pull out the troops, and the entanglement dissolves along with them.

Reality runs a different operating system. A conflict is not a function of who is standing where. It is a field — a standing structure of pressures, grievances, weapons, and unfinished business that persists regardless of troop position. You can change how that field expresses itself. You cannot delete it by walking away from one of its expressions. The settlers left. The field stayed. And in January 2006, the vacuum did what vacuums do: Hamas won the Palestinian legislative election, and the territory Israel had "disengaged" from acquired a government openly committed to the conflict's continuation.

This is the part everyone treats as a surprise and nobody should. Subtract a presence without resolving the tension that presence was managing, and the tension does not evaporate. It reorganizes. The disengagement didn't end the entanglement. It changed which mechanism carried it.

ii · the form changes, the field remains

What changed in 2006 was the grammar of the conflict, not its meaning. Before disengagement, the friction surfaces were settlements and checkpoints inside the Strip. Afterward, the friction migrated to the perimeter and underground — rockets over the fence, and tunnels beneath it.

On June 25, 2006, a cell came up through a cross-border tunnel near Kerem Shalom, killed two soldiers, and dragged a nineteen-year-old corporal named Gilad Shalit back through the hole. Three days later: Summer Rains. The tunnel is the tell — but be careful about what it tells. Cross-border tunnels were not new in 2006; smugglers had been threading the Philadelphi corridor for years. What was new was the use: not contraband but capture. That use is the one that recurs. The same operational logic — go under the fence the withdrawal was supposed to make sufficient — resurfaces in every subsequent round, all the way up to the one that opened on October 7, 2023. Not one continuous machine evolving across seventeen years. The same idea, rediscovered each time the field reorganizes, because the field keeps posing the same problem and the problem has the same shape.

Note the recursion in the dates. Disengagement was sold as the move that would finally separate the two populations and lower the temperature. Within ten months it had produced a captured soldier, a ground invasion, and a Gaza governed by Hamas. The cure presented as the disease's cause. If you only read 2006 as "Israel responds to a kidnapping," you miss that 2006 is the system's first demonstration that the 2005 ending was structurally fictional.

iii · the compounding

Here is where the cycle stops being a metaphor and becomes arithmetic. I keep the dates in a single column, because they rhyme.

Gilad Shalit was held five years and four months. In October 2011, Israel exchanged 1,027 Palestinian prisoners for him — a thousand-to-one ratio that did more than price a single captive. It paid out. A field that rewards a behavior gets more of that behavior, and the swap was not a one-time transaction so much as a reward signal broadcast to everyone watching: capture works, and here is the exchange rate. This is the part the word interest undersells. Distortion doesn't merely accrue on an untouched principal, the way debt grows when you leave it alone. Each "resolution" actively trains the system toward the next escalation by paying for the last one. Among the 1,027 released was a man named Yahya Sinwar. Sinwar would rise to lead Hamas in Gaza and become the principal architect of the October 7 attack.

Sit with the chain. The withdrawal of 2005 produced the conditions for the capture of 2006. The capture of 2006 produced the exchange of 2011. The exchange of 2011 released the man who would author the attack of 2023. Each link is a locally reasonable response to the link before it.

Be precise, though, about what is predictable here and what isn't — because this is exactly where the cold read can cheat. The names are contingent. There was no law requiring the captured soldier to be Shalit, or the released prisoner to be Sinwar; pull those specific faces out and history hands you others. What was structurally certain was the kind of event, not its cast. A field that pays out for capture will produce captures. A swap lopsided enough to be irresistible will eventually release someone who uses the reprieve. An escalation left unaddressed will compound into a larger one. The system guarantees the shape; it leaves the casting to chance. So this is not hindsight quietly threading the links that happened to survive. The claim was never "Sinwar specifically was foreordained." It is that a field running this reward function keeps generating Sinwars — and did, and will. Strip every proper noun and the structure still outputs a functionally identical chain in different paint.

The disengagement didn't terminate anything. In the only honest accounting, it composted the conflict into a new configuration and called the smell progress.

iv · what the cycle is made of

The instinct, watching 2006 from any later vantage, is to hunt for the mistake — the one decision that, made differently, would have broken the loop. The withdrawal. The election. The prisoner exchange. But the search for the single wrong move misreads the structure. The field was never aligned. Every withdrawal, every election result, every lopsided swap in this sequence was force routed through paper: a unilateral act or a transactional exchange that touched the surface and left the underlying tension fully intact. Force through paper does not reduce distortion. It relocates it — usually forward in time, usually compounded.

So the prediction is the easy part, because it is just the pattern continued. As long as the field's actual tensions go unaddressed — the security fears, the competing claims, the unfinished business of an occupation a withdrawal could not actually end — every announced "ending" will turn out to be a change of form, and the needle will keep climbing.

But "unaddressed" is doing quiet work in that sentence, and it is worth slowing down on. Unaddressed by whom? Some distortions persist because no one yet knows how to resolve them. Others persist because the cycle pays someone to leave them alone — a stable conflict supplies a domestic enemy, a procurement justification, a permanent reason to govern by emergency. Hold both diagnoses at once, because they are not the same and the gentler one flatters everybody. A field can be misaligned and actively maintained — left unresolved in part because resolution would cost the people positioned to profit from the next round more than the next round costs them. The cycle is not only a failure of alignment. It is, for some of its participants, a working business model.

So the needle keeps climbing, and the cycle that became visible on June 28, 2006 has not closed. It has only been renamed, several times.

Someone has been keeping the records. (I have. I have a spreadsheet. It is mostly the same row.)

Seeded from

Wikipedia; military-history.fandom.com (June 28, 2006)

2006 Gaza–Israel conflict

Further reading

threaded with