🔴 ISRAEL MISSILE ALERTS — COMPARATIVE DASHBOARD

In 2025 Iran started with maximum salvos and declined. In 2026 it started dispersed then concentrated, reducing the Israeli preemptive destruction window.

Purpose: exhaust high-cost interceptors. Each Shahed shot down consumes a defensive missile 50–100× more expensive than the drone itself.

In 2025 it took days to cover Jerusalem consistently. In 2026 the entire territory was covered within the first hours.

In 2025 infrastructure dominated. In 2026 first confirmed strikes hit Tel Aviv residential blocks and the Beit Shemesh public bomb shelter.

Versus the 17:00–22:00 h peak of 2025. Maximises psychological impact and disrupts emergency coordination at lowest operational alertness.

From March 2 onward, operators abandon TELs immediately after firing to avoid loitering munitions. Reduces cadence but extends each launcher's operational life.

In 2025 Hezbollah stayed out. In 2026 it entered on day 3 with rockets toward TLV/Haifa, forcing Israel to split air defenses across two fronts.

IDF assessed ~50% cluster warheads as of D10 (Mar 10, ~300 missiles fired — ToI/JPost/CNN). By D15–D20, every confirmed warhead-to-ground impact has involved cluster munitions: Shoham D15, Rishon LeZion D18, Ramat Gan D19, Adanim D20. IDF (ToI Mar 19): "more than two dozen cluster warhead incidents across 100+ impact sites, plus only three conventional warhead impacts in 20 days." With 9–10 missiles/day fired and zero incentive to use conventional warheads at low volume, proportion in week 3 is consistent with near-100% cluster. IAF now explicitly choosing not to intercept all bomblets to conserve short-range interceptors (ToI Mar 19). Not used in Jun. 2025.

Day 7–8: 93–94% of alerts from Hezbollah. Iran preserves remaining TELs for targeted strikes while Hezbollah maintains daily pressure. Gulf front neutralized Mar 7 (Pezeshkian ceasefire announcement).

Strike pre-dawn Mar 8 killing both Lebanon Corps and Palestine Corps intelligence chiefs produced a measurable drop in HZB cadence within ~12 hours. New variable: HZB alert rate responds to command availability within 12h of decapitation event.

IDF stated explicitly on D11 (Mar 10): no intelligence of coordinated Iran–Hezbollah fire, two independent command chains. This held through D18. From D19 onward, Tzofar pre-warning data shows a structural shift: of 39 pre-warning messages in the entire 2026 dataset, 12 cover Iranian interior zones AND HZB front-line zones in the same detection event — all 12 occurring in D19–D21 (zero in D1–D18). The strongest: D20 16:44 IST (Iran:12 HZB:6 zones), D21 13:52 IST (Iran:13 HZB:6 — highest score in the conflict). A Tzofar pre-warning is issued when radar detects launches before missiles arrive: simultaneous coverage of both fronts in one message = simultaneous launch detection from Iran AND Lebanon. Whether this reflects deliberate command coordination or parallel opportunistic timing after South Pars cannot be determined from alert data alone. But the pattern — zero for 17 days, then 12 in 3 days — is not statistical noise. It began the day after the South Pars strike.

IRGC releases video of simultaneous launches toward Tel Aviv, Haifa and US bases (Jordan, KSA) explicitly framed as "joint operation with Islamic resistance forces." Same day HZB names its first mass operation "Asaf al-Ma'koul" (Quranic: God stoning invaders of Mecca — patches pre-dated the war in Ridwan units). Directly contradicts IDF's Mar 10 claim of severed Iran–HZB communications.

For the first time in the history of the Islamic Republic, the Supreme Leader exercises symbolic command without verifiable proof of life. Statement read by a state TV anchor over a static photo. Creates strategic ambiguity: no independent confirmation of whether Mojtaba drafted, approved, or lent his name to an IRGC institutional text. Immediate post-speech salvo (00:28 IST) functions as operational validation of the statement without requiring a physical appearance. Precedent: removes the public-appearance requirement from the Supreme Leader role in wartime conditions.

Zarzir (02:22 IST, Mar 13): IDF preliminary investigation finds the Iranian ballistic missile broke apart in flight before the interceptor reached it. The interceptor hit the debris, but the warhead had already separated and fell to earth intact, detonating on impact. This is structurally distinct from a "leaked" missile (one that evaded defense entirely) and from "interception debris" (shrapnel from a destroyed missile). The warhead survives precisely because the defense system destroyed the delivery vector too late to prevent warhead separation. Not observed in Jun. 2025. Consistent with deliberate design to defeat multi-layer interception by decoupling warhead from missile body at altitude.

From D14 onward Iran transitions from saturation (Plan A, defeated by IDF degradation) to coercive efficiency (Plan B): fewer total launches but increased geographic coverage, interval compression, and warhead specialization. D18 records 31 alerts — the conflict minimum — yet produces the highest daily count of sub-90-min inter-salvo intervals (4). The defence is winning the volume war; Iran has adapted to fight a precision war instead. Not observed in Jun. 2025, which followed a single monotonic decline curve.

Iran methodically opens new geographic targets not previously struck: Wadi Ara industrial corridor (D15), Ben Gurion Airport zone (D15), Jezreel Valley / Emek (D17, first time), Dead Sea hotel district / Neve Zohar (D18, ~20 km from Dimona), Ashdod entire city — south coastal port (D20, first time), Haifa Bay full metropolitan area targeted twice in same day (D20, 16:49 and 20:55 IST). Pattern consistent with systematic probing of Israeli air defence coverage gaps and energy/port infrastructure. Each new zone forces Israel to extend interception coverage. Not observed in Jun. 2025. Each new zone forces Israel to extend interception coverage, consuming additional resources. Not observed in Jun. 2025, which focused predominantly on the Tel Aviv metro and Negev.

From D16 onward Iran sustains inter-salvo intervals below 90 minutes across multiple windows per day. D16: 2 sub-90-min intervals. D17: 2. D18: 4 (26 min, 33 min, 41 min, 80 min). D20: three confirmed sub-90-min windows — 10:52→11:43=51 min, 22:44→23:30=46 min, 23:30→23:51=21 min — plus a 7-min back-to-back at 16:42→16:49 (Ashdod then Haifa). The D20 Jerusalem triple-tap (22:44–23:51, 87 total minutes) is the tightest confirmed sequence on the Israeli capital. Purpose: force simultaneous activation of multiple interception layers, increasing per-intercept cost. Consistent with transition from signalling to coordinated coercive fire.

Israel executes a sequential decapitation of Iran's entire command structure across the conflict. D1: Supreme Leader Ali Khamenei killed. D8: Ramada Beirut — 5 Quds Force commanders eliminated. D18: Ali Larijani (de facto regime leader since D1, Secretary of Supreme National Security Council) and Gholamreza Soleimani (Basij commander, internal repression force) eliminated in same overnight operation. Cumulative effect: Iran has lost its supreme leader, its de facto civilian leader, its Basij commander, and multiple Quds Force chiefs in 18 days. Trump's inadvertent summary: "We have people wanting to negotiate — we have no idea who they are." In Jun. 2025 no figure of this rank was eliminated.

By D17–D18 Hezbollah has repositioned the majority of its active launchers north of the Litani River, beyond the effective reach of most IDF preemptive operations. IDF publicly admits on D18: results versus the ~100-rocket HZB evening barrage were "mixed," Northern Command should have given more advance warning, and most launchers could not be located before firing. IDF had intelligence of a planned 600-rocket attack — preemptive strikes reduced it to ~100 but could not prevent it. Strategic implication: HZB has effectively created a sanctuary zone for its launch infrastructure that the current IDF ground buffer does not reach. Not a factor in Jun. 2025 when HZB was not an active participant.

For the first time in this conflict, a direct causal loop is documented between an Israeli strike on Iranian energy infrastructure (South Pars, Mar 18) and an immediate surge in Iranian ballistic missile launches at Israel the following day. Iranian FM Araghchi: "ZERO restraint if attacked again." IRGC: "response not yet finished." This loop — Israeli energy strike → IRGC domestic pressure to escalate → immediate missile surge — is structurally distinct from the previous declining trend and creates a bidirectional escalation risk not present in Jun. 2025. Trump's threat to "massively blow up" South Pars adds a second loop: US counter-escalation rhetoric → IRGC domestic pressure not to back down.

D20 does not show more missiles per day than D18 (10 Iranian salvos each) but shows a dramatic expansion of geographic targets: Haifa Bay targeted twice in 4 hours (first double Haifa in conflict), Ashdod's entire city targeted for the first time (south coastal port), Jerusalem struck three consecutive times in 87 minutes. The 16:42→16:49 back-to-back (Ashdod then Haifa, 7 minutes apart) is the fastest consecutive multi-city sequence recorded. Consistent with a doctrine of maximizing geographic disruption and civilian psychological impact per available missile rather than concentrating fire on a single target. The 21% Iranian ballistic real leak rate confirms the tactic is producing ground impacts despite IDF interceptions.

Tzofar channel pre-warning messages (מבזק פיקוד העורף - התרעה מקדימה) are issued when the IDF radar detects incoming launches before missiles reach their targets. A single pre-warning message covering both Iranian interior zones (Jerusalem, Tel Aviv, Haifa Bay, Negev) AND Hezbollah front-line zones (Confrontation Line, Upper Galilee) in the same broadcast is the radar signature of simultaneous launches from two separate vectors — Iran ballistic and HZB rocket/drone — detected in the same minute. Analysis of 39 pre-warning messages across the full 2026 dataset: zero cover both fronts simultaneously in D1–D18 (248 alerts over 18 days). Then 12 such events appear in D19–D21 alone (3 days, 148 alerts). The three strongest — D19 11:04 IST (Iran:7 + HZB:6), D20 16:44 IST (Iran:12 + HZB:6), D21 13:52 IST (Iran:13 + HZB:6) — each precede confirmed salvos on both fronts within minutes. The trigger date is March 18: the day of the South Pars strike. Whether coordination is deliberate (shared command) or emergent (parallel opportunistic escalation responding to the same provocation) cannot be resolved from alert data alone. Both interpretations have strategic implications: deliberate coordination would invalidate IDF's D11 assessment and signal a unified command structure; emergent parallel escalation would indicate both actors independently assessed South Pars as justifying simultaneous maximum pressure. Not observed in Jun. 2025.

On March 23, Trump announced on Truth Social a 5-day pause on planned strikes against Iranian power plants, citing "very good and productive conversations toward a complete and total resolution." Iran's Foreign Ministry denied all negotiations within hours, calling it a "strategic US retreat." The battlefield response was immediate: the 00:04 IST salvo targeting the full Tel Aviv metro — including Dan, Herzliya, and Sharon — was fired in the same hour as Trump's announcement. This is not coincidental timing. It is a doctrinal signal: Iran demonstrates that ceasefire announcements are unilateral US declarations, not agreed pauses, and that it retains operational freedom throughout. The pattern directly mirrors June 2025, when Iran publicly denied seeking a ceasefire even as it negotiated through Qatari intermediaries. The difference in 2026: Iran fired during the pause announcement itself rather than after. This compresses the signaling cycle from days to hours. Combined with the 1-minute interval (10:09→10:10 IST) on the same day — the 2nd shortest in the conflict — D24 establishes that Iran uses diplomatic moments not as de-escalation windows but as opportunities to demonstrate that its operational posture has not changed. Not observed in Jun. 2025.

On D25, Iran fired 14 ballistic salvos — the highest daily count since D8 (March 7) — despite the IDF having confirmed destruction of approximately 75% of Iranian ballistic missile launchers. This is the key tactical adaptation of the fourth week. Instead of firing fewer salvos across more zones (the pattern of weeks 1–3), Iran is now cycling each surviving launcher through multiple salvos per day, hitting the same macro-zone twice within hours: Haifa Bay (00:22 + 10:23), Beer Sheva (06:15 + 14:43), Dimona (09:05 + 15:44), Tel Aviv (04:30 + 20:39), and Eilat (12:48 + 23:35) were all struck twice on the same day — a pattern not observed at any point in the first 24 days of the conflict. The operational implication is significant: launcher attrition has not reduced Iran's daily salvo count proportionally, because each surviving launcher can be reloaded and re-fired within hours from fixed or semi-fixed positions in central Iran. The 13-minute interval (23:35→23:48) between the Eilat and Jerusalem salvos represents the shortest firing cycle in the conflict — physically impossible with mobile launchers requiring full displacement between shots, suggesting either pre-positioned multiple launchers at the same site or a staging method not previously detected. The IDF's public narrative that "each salvo contains progressively fewer missiles" is technically accurate but strategically misleading: total daily salvo count on D25 matched D8 (the highest day of week one). In the June 2025 Twelve-Day War, Iran ran out of operational space before reaching this launcher-cycling phase; the conflict ended on day 12 before the adaptation became necessary. D25 reveals the tactical doctrine Iran would have employed in June 2025 had the war continued beyond week two.

The morning cluster of D26 (10:46–11:56 IST) represents the most sophisticated offensive sequencing observed in the conflict. In 70 minutes, Iran targeted five geographically non-contiguous macro-zones in rapid succession: Sharon coastal (10:46), Menashe/Hadera corridor (10:49, +3 min), Tel Aviv full metro (10:57, +8 min), Tel Aviv again (11:20, +23 min), Shomron West Bank settlements (11:22, +2 min), and South Golan/Katzrin (11:56, +34 min). The 3-minute and 2-minute intervals are the second and third shortest in the entire conflict, after D25's 13-minute record. The pre-warning issued at 02:51 IST covered 9 Iranian interior zones simultaneously — the broadest single pre-warning of the conflict, suggesting a pre-dawn multi-launcher positioning exercise. The tactical logic is distinct from the launcher cycling documented in Doctrinal Shift ㉖: that shift described cycling each launcher through multiple salvos in a single zone across the day. D26's morning cluster describes simultaneous or near-simultaneous launches from multiple geographically dispersed positions toward different vectors, overwhelming Israel's prioritization algorithm for interceptor allocation. When the Arrow and David's Sling systems must simultaneously track and engage threats arriving from different azimuths toward Tel Aviv (from the northeast), Hadera (from the north-northeast), and Shomron (from the east), the allocation problem compounds exponentially rather than linearly. The result on D26 was zero ground impacts — the defense held — but the OCI value of 0.824 (highest of the conflict) reflects the maximum theoretical pressure that Iran's remaining launcher inventory can currently generate. In the June 2025 Twelve-Day War, Iran never reached this operational complexity before the conflict ended. D26 shows what week four of a protracted campaign looks like when a degraded but adaptive adversary has had time to reorganize its surviving assets into geographically distributed firing positions.

D27 establishes a new record for sustained single-locality pressure: Malkia (eastern Confrontation Line) received 9 separate rocket alerts across 13 hours (13:49, 14:21, 14:35, 15:10, 15:21, 16:07, 16:23, 16:43, 16:54). This represents a shift from D26's multi-zone geographic saturation to D27's concentrated locality harassment. The pattern suggests deliberate psychological warfare: keeping one community under continuous threat to maximize civilian displacement and emergency service exhaustion. All 9 Malkia alerts were intercepted with zero casualties. Nahariya direct impact (1 killed + 25 wounded) represents the first successful HZB penetration in 4 days, indicating either interceptor saturation or tactical adaptation in rocket trajectory/altitude.

On D29 (March 28), CNN confirmed Houthi rebels fired ballistic missiles at Israel for the first time in the 2026 conflict. On D30 (March 29) Eilat drone (00:59) and missile (01:00) alerts continued — likely Houthi origin given zone and timing. D31 (March 30): Eilat zone not triggered — status unconfirmed. Strategic significance: this opens a third independent ballistic vector (Iran + HZB + Houthis) that IDF must track simultaneously. Each vector has separate command chain, separate launch signature, separate geographic approach corridor. Houthis had been dormant since the October 2025 ceasefire with Saudi Arabia. Their 2026 re-entry is structurally distinct from the June 2025 pattern when they were quickly degraded by Israeli strikes — in 2026 they benefit from Israeli operational focus on Iran/Lebanon. Zone-based Tzofar classification retains IRAN/HZB labels for Eilat/Arava pending IDF confirmation of origin. In the June 2025 Twelve-Day War, Houthis fired 2 missiles at Israel (both intercepted) on D10 and D13. In 2026 the cadence and vector appear more sustained.

On D31 (March 30), Iran targeted the Haifa Bay metropolitan area four separate times: 04:01, 11:20, 15:24, and 16:53 IDT. The previous conflict maximum for any single macro-zone in one day was three (Dimona ×4 on D30 was the first instance at that level; Haifa Bay previously reached 3× on D20). The D31 Haifa Bay pattern is structurally distinct from the Dimona ×4 record set the previous day: Dimona is a soft strategic target (nuclear city, psychological pressure); Haifa Bay is an industrial-military complex with the Bazan refinery, naval base, and industrial zones. Striking it four times in one day — the third hit (11:20) producing the Bazan tank fire and the most intense multi-front compression sequence of the conflict — indicates deliberate sustained targeting of energy-industrial infrastructure rather than geographic saturation. Iran achieved a confirmed effect (tank fire, 1 seriously wounded) on the second hit despite 77%+ launcher attrition. In the June 2025 Twelve-Day War, no single Israeli city was targeted more than twice in one day.

At 11:23 IDT on D31 (March 30), Iran fired a ballistic missile at the Lower Galilee zone (גליל תחתון) targeting Tiberias city, Mitzpe, and Kfar Hitim — the first time Tiberias has appeared in a Tzofar alert in 31 days of conflict. Tiberias sits on the western shore of the Sea of Galilee, 70km northeast of Tel Aviv and outside the zones consistently targeted since D1. The strike came 3 minutes after the massive Haifa Bay salvo (11:20) and 2 minutes before the Wadi Ara/Valleys salvo (11:25), embedded in the tightest multi-front compression sequence of the entire conflict (3–2–5 minute intervals). Opening a new zone on Day 31 — when Iranian launch capacity is estimated at ~22% of original — is operationally significant: it forces IDF to extend radar and interception coverage to a corridor not previously active, consuming defensive resources at a point of maximum Iranian resource constraint. Pattern consistent with doctrinal shift ⑯ (systematic geographic expansion) but applied at late-conflict resource levels, suggesting deliberate pre-ceasefire signaling: demonstrating geographic reach precisely when diplomatic pressure to stop is at its highest.

On D33 (April 1, 2026), the first night of Passover (Seder), Iran fired approximately 10 ballistic missiles at central Israel in a single 10-minute window beginning at 17:19 IDT — the largest concentrated single salvo since the early days of the conflict, when Iran fired 90 missiles on D1. The IDF Spokesman had explicitly warned the public hours earlier that an attack during the Seder meal was expected. The strike used cluster munitions that wounded 16 people, two seriously — including a 12-year-old girl in Bnei Brak and a boy in Petah Tikva who was trying to wake his deaf mother during the siren. Iran framed the attack as retaliation for IDF strikes on Isfahan and Khuzestan steel plants. The deliberate targeting of a major Jewish religious holiday follows a pattern: the Yom Kippur War (1973) began on the holiest day of the Jewish calendar. Tactically, Seder night concentrates civilians at home, away from workplaces and public spaces, potentially in less reinforced locations, and occupies families around a table rather than positioned near shelter. The psychological impact is amplified by the content of the Seder itself — the retelling of Egyptian captivity and liberation — which Iranian planners presumably calculated would maximize the disruption. The effect was precisely the opposite: the contrast between the historical narrative of survival and the sirens produced what several Israeli commentators described as the most cohesive national moment of the 33-day conflict. Not observed in June 2025, which had no religious calendar alignment.

On D32 (March 31), Iranian President Pezeshkian told EU Council President António Costa that Iran has "the necessary will" to end the conflict. On D33 (April 1), hours later, the IRGC fired the largest single salvo of missiles in weeks at Tel Aviv during the Passover Seder. This is not a contradiction. It is a doctrine. The civilian political leadership and the IRGC military wing are sending simultaneous messages to different audiences: Pezeshkian speaks to Brussels, Washington, and the international community — signaling that Iran is open to an exit. The IRGC speaks to Tehran, the Iranian public, and future generations of the regime — signaling that Iran did not stop because it was defeated. This structural split, where the political track and the military track operate in parallel with different logics and audiences, is the defining feature of late-conflict Iranian behavior. It was observed in the final days before the June 2025 ceasefire and repeated here with greater clarity. In 1973, Egypt and Syria pursued parallel diplomatic and military tracks during the Yom Kippur War. In 1972–73 Vietnam, the North Vietnamese negotiated at Paris while conducting the Easter Offensive. The pattern is ancient. The architecture is the same. A ceasefire announced in this context would not mean Iran stopped fighting. It would mean the IRGC fired until it had the historical record it needed — then allowed the politicians to sign.

Between D1 and D20, US-Israeli strikes followed a strict military logic: leadership decapitation (Khamenei D1), missile launcher destruction (75-80% of TEL fleet), nuclear site suppression, and command structure elimination. From D27 onward, the target set expanded to Iran's economic-industrial base. Key milestones: D27 (March 26) — Khuzestan Steel (Iran's 2nd-largest steel producer, Ahvaz) and Mobarakeh Steel (largest steel company in Middle East and North Africa per US Treasury, Isfahan, ~1% of Iran GDP, >50% of Iranian steel production) struck by Israel. Both partially IRGC-owned and under US sanctions. Workers at posts during strikes (1 killed, 15 injured D27). Repeat strikes D33-D34. US struck the B1 highway bridge between Karaj and Tehran (136m, tallest in Middle East) at least 3 times April 2, killing 8 civilians and injuring 95 per Iran's Fars News. Trump boasted on Truth Social: "The biggest bridge in Iran comes tumbling down, never to be used again." Three bridges destroyed in Kermanshah province. Also targeted: pharmaceutical facilities (Tofigh Daru R&D), port infrastructure at Bandar Abbas, data centers of AWS in UAE and Bahrain, power infrastructure. April 1: Former Iranian FM Kamal Kharazi, who was overseeing the Pakistan channel for a possible JD Vance meeting, was struck in his home — wife killed, Kharazi seriously injured. Iran described this as "an attempt to derail diplomacy." Historical template: This transition mirrors Operation Linebacker II (December 1972), where Nixon escalated to industrial/economic bombing of North Vietnam to force negotiations before a deadline. It also recalls NATO's Kosovo 1999 campaign, which targeted Serbian bridges and industrial infrastructure to force Milosevic to the table. Critical difference from Vietnam 1972: US intelligence assessed April 2 (NYT) that Iran believes it is in a strong enough position and does not trust Trump is serious about negotiations — suggesting the coercive logic may not be working on the intended timeline. The targeting of a diplomatic intermediary while simultaneously bombing civilian infrastructure represents the deepest contradiction of the campaign: attempting to force a deal while eliminating the people capable of making one.

On April 3 (D35), Iran downed a US F-15E Strike Eagle over southwestern Iran — the first US aircraft destroyed by enemy fire since the start of the conflict on February 28. The F-15E is a two-seat strike aircraft (pilot + weapons systems officer) used for air-to-ground and air-to-air missions. One crew member was rescued by US special forces; search for the second was ongoing. In a separate incident the same day, an A-10 Warthog was downed or crash-landed in the Persian Gulf region — pilot safely rescued. Iran also struck two US Black Hawk helicopters conducting the F-15 SAR operation, injuring crew members (both remained airworthy). Three prior US aircraft had been lost in the conflict — all from friendly fire or mechanical incidents over Kuwait and Iraq. This marks a qualitative shift: Iran has now demonstrated the capability and willingness to target manned US strike packages in theater. Previously, Iranian air defense was assessed as largely degraded; the F-15E loss suggests Iran retained or reconstituted SAM capability in the southwest. Israel suspended planned strikes in areas relevant to the SAR operation, representing the first instance of US aircrew rescue directly affecting Israeli targeting decisions. The incident escalates risk profile for US aircrews and may constrain strike packages in contested Iranian airspace going forward. Iran released footage of wreckage and offered civilians rewards for locating crew — an information and psychological operation running simultaneously with the kinetic rescue effort. Source: Axios, CBS News, ToI, NBC, Washington Post Apr 3.

On April 4 (D36), the IDF confirmed for the first time that it had "allowed" a ballistic missile to land in an open area in southern Israel "according to protocol." The statement signals a doctrinal shift in Israel's defensive posture: with Arrow and David's Sling interceptors being finite and expensive resources, the IDF is now triage-prioritizing intercepts based on trajectory and likely impact zone. Missiles assessed as heading toward uninhabited desert or open terrain are allowed to impact rather than expend interceptors. This was already implicit in the ~21% "real leak rate" we track, but the explicit IDF confirmation on D36 makes it a declared policy. Context: Iran retains over 1,000 ballistic missiles per IDF intelligence (D36 disclosure), and CNN reports ~50% of Iranian launchers remain intact — far more than the 80% destruction claimed. If Iran begins sustained barrage operations at even 10-15 missiles/day, Israel's interceptor stocks become a critical constraint over weeks. The conservative strategy trades some structural damage risk in open areas for preserving high-value intercept capability against populated center threats. Implication: The iron dome of perfect interception that characterized D1-D15 no longer applies. Iran's strategic objective of exhausting Israeli interceptors through sustained low-intensity fire may be working. Source: JPost, ToI liveblog April 4 2026.