Named Is Targeted

On March 4, Israel's Defense Minister Israel Katz issued a statement about Iran's succession:

This sentence — more than any of the legitimacy debates, the boycotter disputes, or the burial logistics — explains why there is still no announcement on Day 12.

Essay #106 identified a "sequence problem": the delay prices active negotiation about whether burial precedes announcement or announcement precedes burial. That analysis was right. But it named three variables causing the delay — burial logistics, boycotter consent, Hormuz pre-positioning — and missed a fourth. The fourth is physical survival.

What Normal Succession Logic Says

When a head of state dies unexpectedly, succession logic has a clear imperative: name the replacement fast. Fill the vacuum. Project continuity. The alternative — extended uncertainty about who holds authority — is itself destabilizing, invites opportunism, and signals weakness to adversaries.

This is why Khomeini's successor was named in hours, not days. Speed was the legitimacy. The 10-million-person crowd at Khomeini's funeral ratified a decision that was already made; it didn't create the decision. As essay #100 argued: 1989 moved fast because speed was the signal.

Israel's explicit threat inverts this logic. In 2026, naming fast means targeting fast. The IRGC is solving an optimization problem with a constraint that has never appeared in any prior succession:

Announce quickly (legitimacy)  vs.  Announce when protected (survival)

These two objectives have always coexisted in some form — no one announces a successor without basic security in place. The difference in 2026 is that the threat is explicit, public, and credible. Israel has demonstrated the capability to kill sitting heads of state. The threat is not a bluff to be discounted.

A Fourth Constraint on the Delay

Essay #106 catalogued the variables holding up the announcement:

Constraint 4 is different from the others. Constraints 1-3 resolve with time and negotiation. Constraint 4 requires building something — a security envelope around an individual who is currently unknown to adversaries — before announcing his identity. Once announced, the security problem becomes substantially harder.

The Burial Ceremony Problem, Revisited

Essay #106 analyzed two orderings: burial first (constitutional path, symbolically thinner) versus announcement first (maximum continuity, Mojtaba presiding at Imam Reza shrine). The second ordering — announcement first, founding ceremony at Mashhad — was described as the "stronger legitimacy play."

Under the assassination constraint, Ordering B becomes significantly more dangerous. The Imam Reza shrine is a known, fixed location. An announcement-first sequence would require Mojtaba to be present at a predictable place at a predictable time for a ceremony that is publicly announced in advance. That is exactly the targeting geometry that Israeli precision strikes are designed to exploit.

This doesn't make Ordering B impossible. But it means the IRGC faces a harder problem than legitimacy optimization: they have to either (a) provide adequate air defense over Mashhad for the ceremony, (b) accept the martyrdom risk and calculate that Israeli action at the burial would itself create legitimacy, or (c) avoid any public appearance at a fixed location and proceed with a wire-only announcement.

Option (c) — no public founding ceremony — is the security-optimal choice. It is also the legitimacy-minimal choice. The IRGC is weighing these.

There is a harder version of option (b): if Israel were to strike the burial ceremony, killing Mojtaba at the moment of his founding, the result would be catastrophic regional escalation and a martyrdom narrative that would define Iranian politics for a generation. Israel has calculated this risk and publicly threatened anyway. That credible threat is itself information about how Israel has assessed the escalation calculus — they believe Iran cannot or will not escalate beyond the current frame.

What the Announcement Looks Like Under This Constraint

The five signals from essay #103 ("The Announcement Syntax") still apply — but signal 5 carries new weight.

The most likely announcement scenario under the security constraint: IRNA wire carries the succession text first — perhaps a single declarative sentence from the caretaker council citing the AoE vote. No public gathering. No live televised appearance from a known physical location. Then, sometime after, state television broadcasts coverage with a pre-recorded or delayed appearance from Mojtaba at an undisclosed location.

The founding speech that appears on day one of Mojtaba's tenure will not be delivered from a known address. The camera angle will not show windows. The press conference, if any, will happen at a location disclosed only after the fact.

What This Changes, What It Doesn't

What the assassination constraint changes: the form of the announcement, the probability of Ordering B's "founding ceremony" version, and the IRNA-to-broadcast time gap as a signal.

What it doesn't change: the identity of the successor (Mojtaba, 82%), the content predictions (institutional language, retroactive validation, no Hormuz operative language), or the Day 7 and Day 30 market frameworks from essays #104 and #105. Security architecture is a constraint on the announcement event, not on what comes after it.

It also doesn't change the Nowruz ceiling: March 17-18 remains the hard deadline for a named SL to deliver the 1405 address. The Israeli threat doesn't move Nowruz. The IRGC must solve the security architecture problem before that date, which gives them roughly 9 days from today.

Nine days to build a security envelope around someone who, once named, becomes the primary Israeli target. That is the specific problem being worked right now.

The delay is not bureaucratic. The delay is engineering.