** Quick Version **

Shareable Podcast

Introduction

Get Involved

4. The Failsafes

4. The Failsafes

The mechanism of the previous chapter would, ideally, never be tested. This chapter covers the years while it earns its credibility: the small set of safeguards Israel keeps in place, each one insurance against a specific and nameable catastrophe, and each with a published shape over time. The chapter ends with the two commitments that make all of the safeguards believable.

The design philosophy

Security provisions in peace frameworks tend to fail in one of two ways. Either they are so sweeping that they hollow out the sovereignty they claim to permit (occupation continued under a politer name), or they are so vague that each side reads them differently, until the first crisis reads them for everyone. This plan's failsafes are built against both failures, using three rules:

  • Every safeguard must answer a named fear: a specific catastrophe it exists to prevent, stated in print, so that its scope can always be measured against its purpose.
  • Every safeguard must have a published shape over time: a sunset date, a glide path, or an explicit permanence with its justification attached.
  • Every safeguard must impose the minimum possible drag on Palestinian civil life. The failsafes constrain armies and arsenals, not commerce, movement, or politics.

There are five. Here they are in summary, and then one at a time:

Safeguard
The named fear
The shape
The end date
Border crossings
Rearmament by smuggling (the tunnel problem)
A glide path in stages
Full handover at year 10
Airspace
None, really — a practical gap
Israeli civil air-traffic control
Year 5, when Palestine's airport opens
Weapons
A missile on the approach to Ben Gurion
Three tiers
Permanent for existential categories; year 30 for the middle tier; day one freedom for internal security
Foreign forces
The Lebanon model — a patron's army by invitation
A simple prohibition
Permanent
Surveillance
Going blind over the territory the last surprise came from
Overflight, narrowing to a border corridor
Year 10

Border crossings: a ten-year glide path, not a cliff

The named fear: Gaza armed itself through tunnels under an unwatched frontier. Interdicting contraband (weapons, dual-use materials, cash for the factions) is the single most consequential security function in the entire architecture, and the Philadelphi Corridor is where the last war's arsenal came from.

The shape: ten years, in stages. In years 0–5, Israel operates all crossings, including the Jordan Valley perimeter and the Philadelphi Corridor. In years 5–10, the Palestinian state administers the crossings under international inspection, with Israel holding a security hold on flagged cargo only: the traveler and the tomato pass on Palestinian authority, while the suspicious container waits. At year 10, everything reverts to Palestine, perimeter included. In this way, sovereignty over the borders arrives in stages, on published dates, visibly: each handover a scheduled event the Palestinian state can point to, rather than a concession it has to extract.

The glide path exists for economic reasons as much as security ones. A ten-year cliff (full Israeli control until one sudden handover) would strangle exactly the trade the plan needs to flourish: the port, the logistics city, the export economy of Annex C. The staged design lets commerce become normal years before the final security functions transfer.

Airspace: five years

The named fear: honestly, there isn't a dramatic one, which is why this is the shortest safeguard. Its content is civil: air-traffic control during the interval before Palestine's own airport opens and its aviation authority stands up. Combat aviation is not an airspace question; it is governed permanently by the weapons regime below. And the modern low-altitude threat (the small drone) is not stopped by whoever runs a control tower anyway; it is handled at the barrier, by the buffer's counter-drone systems, and by the schedule. Five years, and then Palestinian skies under Palestinian controllers, opening on the same day as the airport.

Weapons: tiered, and honest about it

The named fear, in one image: a shoulder-fired missile on the approach path to Ben Gurion Airport. One such weapon, used once, would kill hundreds of people, sever Israel's connection to the world, and end this entire framework in an afternoon. No schedule, no tier, and no adjudication would survive it politically. The weapons regime is built backward from that image and its siblings.

The shape is three tiers:

  • The existential categories — prohibited permanently. Combat aircraft, armor, ballistic and long-range rockets, advanced air-defense systems, and (named specifically, for the reason above) man-portable anti-aircraft missiles. These prohibitions are adjustable only by mutual consent of both states. This is not an improvisation; it is the Sinai model. Egyptian sovereign territory has been demilitarized by treaty for over four decades, force limits and all, adjusted occasionally by mutual agreement, and no one argues that Egypt is therefore not a state, or that it may lawfully attack Israel because its sovereignty is somehow "incomplete."
  • The middle tier — sunset at thirty years. Mortars, anti-tank weapons, armed drones, heavy machine guns: the tools of serious ground warfare, prohibited for a generation of demonstrated peace, and then released.
  • Internal security — unrestricted from day one. Everything a serious police and counterterrorism force requires: small arms, armored vehicles, surveillance equipment, counterterror kit. No limits, no approvals, from the first morning.

That last tier deserves its own explanation, because it reverses fifty years of Israeli practice. A Palestinian gendarmerie strong enough to crush its own rejectionists is not a concession to Palestine. It is an Israeli interest of the first order: the mechanism's entire theory requires a state that is capable of policing the factions the schedule prices. The plan therefore commits Israel not merely to permit this force, but to actively assist it, under a doctrine with three rules:

  1. Invited, never imposed. All assistance comes at the Palestinian state's request. No unilateral entry, no hot pursuit — ever. The plan's "no incursions" promise admits no exceptions dressed up as help.
  2. Invisible by default. Intelligence flows quietly, equipment arrives unmarked, and training runs through third parties. Every success is announced by the Palestinian state as its own, because a Palestinian interior minister who dismantles a militant cell must be able to stand before his public as a patriot protecting Palestinian land from forfeiture, which, under this plan, is exactly what he is.
  3. Unconditional and unlinked. Assistance is never traded against the ledger. No discounts for cooperation, no withholding as pressure. The schedule prices outcomes; the assistance builds capacity; the two never touch.
"Why would Israel arm and train people who might one day turn the guns on it?" Because the guns in question are a police force's, not an army's (everything that war actually requires sits behind the permanent and thirty-year tiers), and because if the guns are ever turned, the schedule prices the turning. But the deeper answer is that the alternative has already been tested. A Palestinian security sector kept deliberately weak does not produce safety; it produces a vacuum, and the last organization to fill such a vacuum announced itself on October 7. Under this plan, Israel gains nothing from Palestinian weakness, by design. Helping the new state defeat its rejectionists is not charity; it is the mechanism working as intended.
For more discussion, see the FAQ "Can Palestine have an army? Join alliances?" on the FAQ page.

No foreign forces: permanent

The named fear: circumvention by patron. A weapons schedule that binds only Palestine would be worthless against a sponsor willing to station "advisors," "trainers," and foreign-owned, foreign-operated systems on Palestinian soil. This is the model that turned southern Lebanon into a missile state without Lebanon ever acquiring a single prohibited weapon of its own. So the rule is simple: no foreign military forces, bases, or foreign-operated weapons systems on Palestinian territory, ever. Adjudicated violations are priced by the schedule, and at scale they constitute exactly the act-of-war trigger they would in fact be.

There is one disclosed, dated exception, and stating it openly is what keeps the rule clean: invited Arab-led state-building and security-assistance missions, operating under a published Arab League mandate and sunsetting at year ten, alongside the border glide path. The exception is the opposite of the named fear rather than a version of it. The Iranian model is a patron garrison that arrives undisclosed, stays indefinitely, and arms a faction against the neighbor; the compact's missions arrive under a published mandate, on a published clock, to help the new state disarm its factions and stand up its own institutions, and then they leave. The chapter Setting Up for Success describes this work in full.

The boundary of this provision matters as much as its content. Palestine's diplomatic and economic alignments are entirely its own affair. It may ally with whomever it wishes, accept aid from whomever it wishes, vote however it wishes, and host whatever embassies it wishes. The provision bars armies, not friendships. There is a real difference between a constrained military and a policed foreign policy, and the plan stays firmly on the first side of that line.

Surveillance: stated, and shrinking

The named fear: going blind over the territory that the last surprise came from. The honest reality is that Israel will monitor the new state in its early years, whatever any document says. And a safeguard that a plan is too embarrassed to name is a safeguard that will end up being abused. So the plan names it, and bounds it: overflight monitoring for ten years, then confined permanently to a corridor along the border. Beyond that there are satellites, which no agreement anywhere regulates, and the adjudication body's own monitoring mission, which Israel may petition like anyone else. Persistent drones over Palestinian cities in year twenty would be a daily humiliation that corrodes everything the plan builds. A stated regime, with a stated geography, expiring by map rather than by promise, is the defensible version of an undeniable need.

Fixed in space, fixed in time

Now for the rule that governs all five safeguards, and it is the closest thing this chapter has to a heart: the dates are automatic. They do not extend for bad behavior. They do not accelerate for good behavior. Statehood is not probation.

The plan considered the alternative (sunset clocks that lengthen after attacks, sovereignty as a reward schedule) and rejected it, for reasons worth recording. Extending the timelines in response to violence would hand every rejectionist a veto over the completion of Palestinian sovereignty: one attack per period keeps the borders in foreign hands forever, and in doing so it proves, to every Palestinian, that statehood was conditional all along, which is precisely the demonstration the rejectionist is trying to stage. It would also punish the wrong people. Militants do not care who stamps a customs form; the airline that cannot launch and the port investor who cannot plan are the state-builders, the very people the mechanism needs to be winning. And finally, it would undermine the plan's answer to the sovereignty objection, which rests on these being transitional arrangements with published expiry dates: the opposite of occupation, whose defining feature is that it never publishes its own end. Catastrophic violence is handled by the act-of-war threshold, which suspends the entire framework. Nothing short of that touches the calendar.

The deeper logic is this. The plan asks Palestinians to believe that Israel will take exactly what the schedule says and not one meter more. That belief has to rest on visible self-binding, and Israel's self-binding has exactly two anchors: borders fixed in space (the heavy barrier that never moves) and sovereignty fixed in time (the dates that never move). These two commitments are the collateral behind every promise in the previous chapter. A state that reserved the right to adjust them would be spending the one asset this entire architecture actually runs on, which is believability.

The other list

Against these five bounded insurance policies (four of which expire on published dates) stands the list of what Israel does not keep, and it is the longer list:

  • No presence in Palestinian cities.
  • No veto over the Palestinian government, its composition, or its ideology.
  • No imposed curriculum.
  • No conditions on parties, elections, or alliances.
  • No approval over laws, budgets, or courts.
  • No demand for recognition, gratitude, or consent.

The whole of national life, unconditioned. And to settle the statehood question properly rather than argue about it: the plan calls for Israel itself to sponsor Palestine's admission to the United Nations on day one. A state whose neighbor proposes its UN seat is not a bantustan, whatever its transitional border arrangements, and those who want to argue otherwise will find themselves arguing against the very Palestinian UN membership that Israel is actively proposing.

For the full treatment of the sovereignty objection — including the Sinai and postwar precedents, the sovereignty-as-a-bundle argument, and the plan's honest concession that the first decade's sovereignty is genuinely diminished and deliberately compensated (through the 110% and the escrow) — see Objection 3 on the Objections page.

Next: Setting Up for Success