Iron Dome
Enable an AI agent to recognise Iron Dome, distinguish its system configurations, assess documented condition and evidence, and identify authorised support actions.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an AI agent to recognise Iron Dome, distinguish its system configurations, assess documented condition and evidence, and identify authorised support actions.
Iron Dome is an Israeli short-range air-defence system developed by Rafael with Israeli partners that combines radar, battle-management software and Tamir interceptor missiles to engage incoming rockets and other aerial threats assessed as endangering defended areas.
It can be Classify a documented asset as a complete Iron Dome configuration, constituent component or related external system.; Compare configuration records and flag unsupported component combinations for qualified review.; Trace a capability or effectiveness statement to its source, configuration, date and measurement definition.; Summarise readiness evidence and identify missing inspections or support records without declaring combat readiness.; Route maintenance, handling and configuration-change requests to the documented responsible authority..
Distinguishing features
Identification requires documented membership in the Iron Dome family; a generic short-range air-defence system does not qualify by function alone.
A complete system configuration connects detection and tracking, battle management, and interceptor launch functions; a launcher or interceptor alone is a component.
Its characteristic functional description includes assessing predicted impact and selectively engaging threats judged relevant to protected areas.
The model distinguishes Iron Dome from adjacent defence systems through documented system identity, component compatibility and integration boundaries, rather than through overlapping threat labels.
Scope
+ Identity and boundaries of the Iron Dome system family
+ Relationships among detection, battle-management, launch and interception functions
+ Documented configurations and interfaces that establish system membership
+ Evidence-qualified capability claims and readiness descriptions
+ Maintenance, controlled handling and authorised lifecycle support
- Detailed construction or internal design of interceptor missiles and radar equipment
- Tactical deployment, engagement settings and targeting decisions
- Other air-defence systems and the architecture of a national defence network
- Military organisations, procurement programmes and manufacturing companies as independent entities
- Conflict histories and political assessments of system use
Characteristics
- System identity and designation
- Documented official designation, aliases and configuration identifier Prevents confusion between the named family, related products and individual equipment.
- Configuration membership
- Configuration linked to documented radar, battle-management, launcher and interceptor types Establishes which components form a supported system combination.
- Functional role
- Detection and tracking; threat assessment; engagement coordination; launch; interception; support Separates component functions from claims about the complete system.
- Documented threat coverage
- Source-stated threat classes, qualified by configuration, date and evidence type Avoids attributing one configuration's claimed capabilities to every Iron Dome installation.
- Claimed engagement envelope
- km for explicitly defined distance or altitude measures, with conditions and source Keeps target travel range, interceptor reach and defended footprint from becoming interchangeable figures.
- Readiness evidence
- Unknown; under maintenance; under test; restricted; declared ready, with authority and timestamp A component's apparent availability cannot establish complete-system readiness.
- External support dependencies
- Documented power, communications, resupply and authorised support dependencies Exposes dependencies that affect whether a configuration can be supported.
- Performance claim basis
- Manufacturer claim; operator report; controlled test; independent analysis; unresolved Makes the provenance and limits of effectiveness statements explicit.
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 5 bundles · 9 layers · 14 findings · 22 questions.
Identity and System Boundary Establishes what the registered Iron Dome concept includes and how named variants and physical instances relate to it.
Iron Dome can denote a system family, a particular configuration or deployed equipment; these meanings must remain distinguishable.
Family Identity
Records the evidence that a designation belongs to the registered system family.
Documented Family Membership
Recognition requires attributable identity evidence rather than resemblance or a shared defensive role.
- Which authoritative record identifies this designation as Iron Dome or a member of its system family? provenance
- Does the designation identify the family, a configuration, a battery or a component? definition
Adjacent System Boundaries
Separates the registered concept from related naval products, component offerings and wider defence networks.
Variant Versus Neighbour
Related branding or shared components alone do not settle whether another product belongs within this entry.
- How do authoritative product records describe the relationship between Iron Dome and C-Dome? boundary
- Which functions belong to Iron Dome itself and which belong to an external integrated defence network? boundary
Functional Chain and Configuration Describes the system-level relationship between tracking, assessment, coordination and interception.
Iron Dome is recognised and assessed through connected functions, not merely the presence of missile launchers.
Detection to Assessment
Captures the distinction between observing a trajectory and assessing its relevance to a protected area.
Selective Threat Assessment
The model records the documented role of predicted-impact assessment without encoding operational thresholds or engagement settings.
- How does the configuration's documentation distinguish tracking a threat from judging that it warrants interception? definition
- Which source establishes the respective roles of the radar and battle-management functions in that assessment? provenance
Interception Chain
Relates battle management, launch equipment and interceptors within a documented configuration.
Supported Component Combination
A valid configuration needs evidence of supported relationships among its constituent equipment and software baselines.
- Which documented launcher, interceptor and battle-management versions belong to this configuration? provenance
- What approval evidence is required before a substituted component or software revision is accepted into the configuration? action
Capability and Effectiveness Evidence Qualifies statements about threat coverage, engagement envelopes and interception outcomes.
Iron Dome performance figures are interpretable only when their denominators, conditions and configuration applicability are explicit.
Coverage Claims
Separates threat categories and different meanings of range or coverage.
Qualified Capability Envelope
Each capability statement must identify its configuration and distinguish the quantity actually being described.
- Which threat classes are documented for this configuration, and is the evidence a claim, test result or operational report? provenance
- Does a quoted distance describe the incoming threat's range, interception distance, altitude or defended footprint? measurement
Outcome Interpretation
Makes interception statistics and their evidential limitations comparable.
Defined Success Denominator
A success percentage is incomplete without a defined outcome, counted population and treatment of non-engaged threats.
- Does the reported percentage use all detected threats, threats assessed as dangerous, attempted engagements or another denominator? measurement
- How was successful interception established, and what uncertainty or independent verification accompanies the result? provenance
Readiness and Controlled Support Connects system condition, support dependencies and lifecycle work to documented authority.
The condition of Iron Dome depends on the integrated system and its controlled explosive components, not a single equipment status.
Integrated Readiness
Distinguishes component condition from a supported declaration about the complete configuration.
Readiness With Evidence
Readiness records retain the assessed configuration, responsible authority, assessment date and unresolved restrictions.
- Which authorised record establishes the readiness state of the complete configuration rather than one radar or launcher? provenance
- Which missing or expired power, communications, inspection or support evidence prevents a current readiness assessment? boundary
Maintenance and Handling Authority
Records the applicable controls for support work, interceptor handling and return to service.
Authorised Lifecycle Actions
Support actions depend on the exact equipment identity, applicable instructions and the authority of qualified personnel.
- Which current manufacturer and operator instructions govern maintenance, storage, transport and disposal for the identified equipment? provenance
- Who may authorise the requested support action and certify the affected equipment's return to service? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- This description is recalled knowledge, not source-verified research; deployment counts, configurations and supported target classes require checking.
- Reported interception percentages depend on how threatening trajectories and successful engagements are counted; no universal effectiveness figure is asserted.
- Published range figures can describe incoming rockets rather than interceptor reach or defended area; measurements are omitted to avoid conflating these quantities.
- Which of these check these first hold for the sense of Iron Dome this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Land-based Iron Dome
- Naval C-Dome variant
- Which of these kinds and varieties hold for the sense of Iron Dome this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Defence of populated areas and critical infrastructure against short-range rocket attacks.
- Protection of military forces and installations against selected aerial threats.
- Naval air defence through the C-Dome variant.
- Operation as the short-range component of Israel's layered missile-defence architecture.
- Which of these real-world use hold for the sense of Iron Dome this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Interceptions can fail, allowing an incoming threat to reach the defended area.
- Simultaneous attacks can exceed available engagement capacity or interceptor stocks.
- Radar, communications, power or battle-management failures can impair protection.
- Falling interceptor and target debris can cause injury and damage.
- Interceptor storage, handling and launch involve explosive and propulsion hazards.
- Which of these failure modes and hazards hold for the sense of Iron Dome this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Israeli deployment forms part of a layered defence that also includes David's Sling and Arrow.
- Export configurations and integration with national command systems can differ from Israeli configurations.
- Which of these regional variation hold for the sense of Iron Dome this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Tamir - Tamir is an interceptor missile used by Iron Dome; Iron Dome is the complete defensive system.
- Iron Dome battery - A battery is an operational grouping of system equipment; Iron Dome names the system family rather than an individual deployed unit.
- David's Sling - David's Sling is a separate system addressing a different, generally longer-range threat tier.
- Arrow - Arrow is a separate family focused on ballistic-missile defence at higher defensive tiers.
- Iron Beam - Iron Beam uses laser energy for interception, whereas Iron Dome uses interceptor missiles.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Iron Dome this model covers, and on what evidence? provenance
What the second pass must settle
- Does an existing Vercy world model already cover Iron Dome, requiring this registry entry to link to that publication?
- Should C-Dome and other related named configurations be represented as variants or neighbouring models under the registry's authoritative granularity?
- Which authoritative public sources establish configuration-specific component identities, threat coverage and capability limits?
- Which effectiveness reports provide sufficiently clear denominators, outcome definitions and verification to support comparison?
- Which maintenance, certification, handling and readiness requirements can be established from accessible authoritative documentation?