The submitted global reports describe several procurement logics: networked precision systems, lower-cost attritable mass, anti-radiation systems, and emerging swarm-oriented platforms. [1][2]
02 / Comparative systems
Loitering Munitions and Sensor–Shooter Convergence
Examines the convergence of sensing and strike functions, divergent procurement models, reported autonomy features, counter-UAS pressure, and the difference between platform capability and engagement authority.
DIRECT ANSWER / EVIDENCE BOUNDARY
Route orientation
- Scope
- The route uses high-level categories and evidence questions. It omits operational ranges, warhead design, target-recognition recipes, attack profiles, and countermeasure instructions.
- Evidence posture
- Report-supported comparative synthesis. Product specifications, market forecasts, and combat claims remain attributed to the submitted reports and require fresh verification.
- Source base
- 4 retained reports are connected to this route.
EVIDENCE-QUALIFIED FINDINGS
What the submitted material supports
Every finding carries an explicit evidence state and links to the retained report trail.
Sensor–shooter convergence can reduce latency, but it also concentrates perception, classification, navigation, communication, and terminal-action failures on one platform. [1][3]
“Fire and forget,” autonomous navigation, automatic target recognition, and autonomous target selection describe different functions and should never be used as synonyms. [3][4]
The exact operating mode, human approval point, lost-link behavior, and software configuration may vary by user, mission, block, and doctrine and are often not public. [3][4]
RISK / CONTROL / OPEN QUESTION
A claim is not complete without its failure modes and limits
Risks
- Cost comparisons can ignore support, training, replacement, and defensive-response costs.
- Manufacturer autonomy language can be mistaken for independently verified operating behavior.
- Persistent sensing can create broader surveillance and retention consequences.
Safeguards
- Publish capability, deployment, operating mode, and authority as separate evidence fields.
- Use system-block and date-specific source states.
- Require post-action audit and evidence retention.
Open questions
- Which functions remain available or permitted after link loss?
- Which claims come from manufacturers, operators, tests, or independent observation?
- How are abort, reassessment, and civilian-protection constraints represented?
CROSS-DOMAIN CONNECTION
Compare the same function in policing, intelligence, and kill-web architecture
Function-specific analysis prevents behavioral assessment, geospatial warning, automatic recognition, resource ranking, and engagement authority from being treated as equivalent.
RETAINED REPORT BASIS
Source trail for this research route
The complete submitted Markdown remains protected in the repository. This page publishes a bounded bilingual synthesis and does not independently verify every embedded claim.
Submitted global-trends report
The Global Proliferation of Loitering Munitions: Multi-Domain Architectures, Autonomous Swarms, and the New Economics of Attrition Warfare
Submitted global-trends report. Market figures, platform specifications, current deployments, and manufacturer claims require fresh primary-source verification before publication as fact.
Submitted global-trends report
The Global Proliferation of Autonomous Kill Webs: Loitering Munitions, Artificial Intelligence, and the Future of Multi-Domain Warfare
Submitted global-trends report. It is used for taxonomy, doctrine, industrial, and systems-architecture questions; operational claims remain report-supported rather than independently verified.
Submitted system case study
The Switchblade 600 in the Modern Kill Chain: Autonomy, Lethality, and the Evolution of Loitering Munitions
Submitted system case study. The public synthesis omits tactical performance details and uses the report only to examine functional stages, authorization, electronic-warfare exposure, and procurement questions.
Submitted system case study
The Switchblade 600 and the Autonomous Kill Web: Sensor-to-Shooter Architecture in Multi-Domain Operations
Submitted system-integration case study. It informs discussion of handoffs, software-defined integration, edge processing, and authority boundaries without publishing operational interfaces or targeting procedures.