- Vigil category device · not official insignia
Identity provenance
Vigil category device — drawn from this record’s own domain, echelon and role. Not an official insignia.
In brief
The body between the Supreme Leader and Iran's three military pillars — a general staff whose mandate is planning, coordination and integration, and which this atlas deliberately does not draw as the commander of the forces it coordinates.
- Scope
- Structure, role, lineage and links. 1 subordinate record published.
- Subordination
- Subordination confirmed
- Sources
- 2 on the record
- Record state
- Partial
Broad area of activity
Iran's whole military structure
Notable history
Iran created the General Staff in June 1988, in the closing weeks of the war with Iraq, to coordinate the national and the revolutionary armed forces that the revolution had left running in parallel. It reports directly to the Supreme Leader as commander-in-chief, and it is institutionally distinct from the Ministry of Defence and Armed Forces Logistics, which sits in the executive branch under the President and does the administering, funding and procuring while the General Staff does the planning. That split is the reason a defence minister can be a civilian and a chief of staff never is. The post has been catastrophically exposed: Mohammad Bagheri was killed on the opening day of the June 2025 war, and his successor Abdolrahim Mousavi on the opening day of the 2026 war.
Strengths
A single planning and intelligence interface to the Supreme Leader, a functional directorate structure modelled on joint-staff practice, and — in air defence — one function where coordination between the two militaries is documented to work.
Limitations
Its authority over the Revolutionary Guard is the contested question in Iranian military organisation, and the honest answer is that credible accounts differ. Some describe the General Staff as exercising operational control across the whole structure; others describe the Guard's autonomy as making real joint command unattainable and the staff's operations function as deconfliction between parallel forces. This atlas therefore places the General Staff beside the three pillars rather than above them: drawing it as their parent would resolve, silently and in a diagram, a question the evidence leaves open.
Subordinate formations
Rows are layout only — position and order carry no hierarchy, importance, sequence or strength. Every record shown is an immediate subordinate of the selected organisation.
Related organisations
- Artesh Institutionally linked to · as of 2026-09 · moderate confidence
The AFGS is mandated to plan for and coordinate the Artesh and to supervise its training and organisation. It is NOT drawn here as the Artesh's parent, because the Artesh answers to the Supreme Leader and a parent-child line would assert a command relationship the evidence does not establish in the form the tree would imply.
- Islamic Revolutionary Guard Corps Institutionally linked to · as of 2026-09 · moderate confidence
Coordination in mandate; contested in practice. Accounts of the AFGS describe it as holding operational control across the force structure, while the same accounts describe the Revolutionary Guard as operating with enough autonomy that genuine joint integration is difficult and the joint staff functions largely as a deconfliction mechanism. This module records the disagreement rather than picking a side, and encodes neither as a command line.
- Law Enforcement Command Institutionally linked to · as of 2026-09 · low confidence
The AFGS's mandate includes integrating paramilitary and law-enforcement elements in wartime. What that has meant in the current war is not established in open sources, and the edge is graded low for that reason.
Lineage & institutional history
Iran's declared command doctrine puts a general staff between the Supreme Leader and three parallel forces. Whether that staff exercises operational command or coordinates forces that answer elsewhere is genuinely disputed between credible accounts, and this record does not settle it.
Preferred operating methods
A general staff above parallel forces. The General Staff was created in June 1988 to coordinate the national and the revolutionary armed forces that the revolution had left running side by side, and its mandate is described as covering military planning across the whole force structure, supervision of training and organisation, intelligence to the commander-in-chief, and integration of paramilitary and law-enforcement elements in wartime. Its functional organisation follows a J-directorate model, and its chief reports directly to the Supreme Leader rather than through the executive branch — which is what distinguishes it from the Ministry of Defence and Armed Forces Logistics, an executive body that administers, funds and procures while the General Staff plans.
A broad generalisation about how this organisation operates, graded as an assessment — not a description of current tactics, and deliberately carrying no capability or effectiveness score.
Command style
Contested, and stated as contested. One institutional account describes the General Staff as the apex military command body holding operational control across the entire force structure. The same body of evidence describes the Revolutionary Guard as operating with enough autonomy that genuine joint integration is difficult, the two forces as maintaining separate services, intelligence and logistics, and the joint staff's operations function as a deconfliction mechanism between parallel forces rather than a unified command. Analysts note that outside air defence there has been very little interoperability between the two militaries and few joint or coordinated exercises in recent years.
Where this generalisation breaks down
The generalisation fails in three ways, and they matter more than the doctrine does. First, mandate is not practice: a body can be assigned operational control and not exercise it, and the accounts that describe the General Staff's authority and the accounts that describe the Guard's autonomy are largely the same accounts, which means the tension is inside the evidence rather than between good and bad sources. Second, the structure has not been observed under conditions that would settle the question, and the conditions that came closest point the other way: both the June 2025 and February 2026 opening strikes killed the chief of the General Staff, and Iranian missile operations continued afterwards, which indicates pre-delegated authority below the top rather than command exercised from it. Third, nothing in this record should be read as a claim about what Iran's command arrangements are in this war — only about what published accounts of the institution say, and where they disagree.
What remains unknown
- Whether the Armed Forces General Staff exercises operational command over the Artesh, the Revolutionary Guard and the Law Enforcement Command, or coordinates forces that answer to the Supreme Leader in parallel, is UNRESOLVED. This module records the disagreement and encodes neither reading in the Force Atlas hierarchy.
- Iran publishes no authoritative organisational documentation, and the accounts this record rests on are compiled secondary analysis rather than primary institutional sources. A published Iranian command instrument, or an authoritative institutional account, would resolve the question; a single operation would not.
- The post of chief of the General Staff was vacant after 28 February 2026 and whether it has been filled is not established in sources this module has read. Iranian command appointments since 2 March 2026 remain unverified and none is authored anywhere in this module.
Quick actions
System access
Where this record connects into the rest of Vigil. Each row is here because this organisation actually reaches it.
Assessed as of2026-09Last reviewed2026-09-04
See this force in the structure Interactive: select this record and follow what connects to it.