AI KILL CHAINS & DECISION SYSTEMS
A high-level, evidence-disciplined explanation of terminal defensive chains and Iron Dome’s detect–track–predict–prioritize–assign–intercept–update loop.
ANALYTICAL & SAFETY BOUNDARIES
Analytical boundary: Autonomy is analyzed by function, context, constraints, evidence, authority, intervention capability, and lifecycle—not as a single label attached to an entire machine. Capability is not deployment; deployment is not autonomous use; recommendation is not authorization; model confidence is not positive identification.
Simulation safety boundary: Synthetic, non-graphic, non-operational education only. Use fictional geography, abstract objects, reserved domains, nonfunctional artifacts, constrained inspect/pause/replay actions, and no real targeting data, attack geometry, payloads, credentials, arbitrary external URLs, malware, command execution, or contact with third-party systems.
Source basis: Exact owner-supplied research-source instances plus bounded official-primary-source currentness v15.
ORIENTATION
Terminal defense shows why automation is attractive under short timelines, while also demonstrating why operating modes, human authorization, error handling, and public evidence must be described precisely.
WORKING BRIEF
Public descriptions support a loop of launch detection, track formation, trajectory analysis, predicted impact, selective prioritization, interceptor assignment, engagement, and continuous update. New launches and uncertain outcomes make the chain iterative rather than purely linear.
The defining public concept is discrimination between trajectories expected to threaten defended zones and those expected to land harmlessly. This preserves defensive capacity but makes prediction, configured defended areas, and uncertainty central governance questions.
Public accounts differ on whether engagement is automatic after configuration or presented to a soldier for a decision. These differences may reflect periods, configurations, users, or doctrine. The responsible public conclusion is that the universal mode is not established.
COMPLETE DOSSIER
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
| Stage | Publicly supported high-level function | What remains unknown |
|---|---|---|
| Detect and track | Radar detects and follows incoming projectiles | Detailed filtering, confidence, and clutter behavior |
| Predict impact | Battle management estimates trajectory and landing area | Exact thresholds and uncertainty handling |
| Prioritize | Selective defense focuses on threats to defended zones | Configured protection criteria and tie-breaking |
| Assign and intercept | System issues or supports engagement and interceptor launch | Universal authorization mode, assignment logic, re-engagement rules |
| Update | Tracks and system state are revised continuously | Full kill-assessment and fallback logic |
Pass condition:
Pass condition:
Pass condition:
Pass condition:
Pass condition:
SOURCE QUALITY · UNCERTAINTY · NEUTRALITY
Primary institutional doctrine or policy; supports what the issuing body states, not deployment or compliance.
Primary technical specification or documentation; supports interface/status claims, not truth or field effectiveness.
First-party capability statement requiring independent corroboration.
Attributable public evidence of deployment scope; does not automatically establish autonomy, effectiveness, or legality.
Observed demo or exercise under bounded conditions; not field deployment.
Structured test with stated conditions; external validity remains limited.
Scholarly evidence with method and scope limitations.
Journalistic account requiring attribution and corroboration assessment.
Preserved source packet; claims remain unverified unless separately supported.
Repository-authored inference explicitly marked and linked to supporting evidence.
Synthetic scenario for education; not operational evidence.
Evidence absent from the bounded search; absence is not proof of nonexistence.
Official operator or government statement; supports what that body says, not independent verification of performance.
Independent public evidence supporting a bounded capability, test, status, or deployment proposition.
Material public claim with unresolved attribution, mode, outcome, or corroboration; must remain attributed and nonfinal.
| Meaning | Subject | Analysis model |
|---|---|---|
| AI_AS_TARGET | Attacks against models, data, retrieval, context, tools, infrastructure, and users. | Lifecycle defense: provenance, isolation, least privilege, retrieval authorization, tool-specific credentials, deterministic policy outside the model, egress controls, telemetry, rollback, and human approval. |
| AI_AS_CYBER_ENABLER | AI accelerates conventional reconnaissance, social engineering, vulnerability analysis, or campaign execution. | Defensive analysis must remain non-operational and must not provide executable payloads, credentials, real targets, or attack procedures. |
| AI_ENABLED_MILITARY_KILL_CHAIN | AI assists sensing, fusion, classification, prioritization, assignment, guidance, engagement support, or assessment. | Use a function-context-control model; distinguish recommendation from authorization, navigation autonomy from target-selection autonomy, and classifier score from positive identification. |
Instructional boundary: Explain systems, evidence, uncertainty, failure, oversight, and defense without reproducing targeting software, weapon configuration, attack procedures, evasion methods, or defeat advice.
CLAIM · SOURCE · LIMIT
| Claim block | Evidence class | Source | Supported proposition | Unsupported inference |
|---|---|---|---|---|
| closed-loop | OWNER_SUPPLIED_RESEARCH_SYNTHESIS | Iron Dome Automation Analysis.md | Public descriptions support a loop of launch detection, track formation, trajectory analysis, predicted impact, selective prioritization, interceptor assignment, engagement, and continuous update. New launches and uncertain outcomes make the chain iterative rather than purely linear. | Does not by itself establish deployment, exact operating mode, combat use, effectiveness, legality, consensus, or endorsement. |
| selective-defense | OWNER_SUPPLIED_RESEARCH_SYNTHESIS | Automated Terminal Defense Systems.md | The defining public concept is discrimination between trajectories expected to threaten defended zones and those expected to land harmlessly. This preserves defensive capacity but makes prediction, configured defended areas, and uncertainty central governance questions. | Does not by itself establish deployment, exact operating mode, combat use, effectiveness, legality, consensus, or endorsement. |
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE