LC-1 · Kinematic Threat Briefs
Kinematic Threat Brief
Source-imported record. This page is not a QSVFF-sealed filing or a verification certificate.
# Kinematic Threat Brief **LRRK Watch / Open-Source Intelligence** — Five current signals across systems that sense, move, and act. | Field | Value | | --- | --- | | Collection cutoff | 30 April 2007 | | Platform | Quiet Systems | | Data label | Open-source intelligence // LRRK analytic product | | Handling | Public-source material. Image rights require separate verification before publication. | ## Executive read ### BLUF April is a pipeline month: Reaper is in Nevada training, the 432nd Wing is days from standup, and later National Defense reporting will place the first three armed SWORDS ground robots in Iraq with 3rd Infantry Division this month—acting systems arriving on the same surge streets as the sensors. ### Key judgments 1. **[Assessment — moderate confidence]** Later National Defense and Wired reporting places three M249-armed SWORDS robots in Iraq from April 2007 with 3rd Infantry Division, 3rd Brigade; that is a later-published fact about this month, not an April primary on the wire. 2. **[Assessment — high confidence]** Reaper remains a Creech training aircraft; no April public combat or IOC declaration was fetched. 3. **[Inference — moderate confidence]** Surge brigades closing through the spring will keep pulling theater Predators and unit Shadows/Ravens harder than joint paper can reallocate them. ### Analytic labels - **Fact** — verified reporting or primary record - **Assessment** — analytic judgment - **Inference** — reasoned but not directly observed - **Uncertainty** — unresolved information gap ### Source grades - **A1** — authoritative primary record / directly confirmed - **B1–B2** — generally reliable and corroborated - **C3** — useful but requires caution ## 01. Armed ground robots — later press dates the first SWORDS to April Iraq *Event / publication dates: later National Defense (August 2007 issue reporting) and Wired 2 August 2007; both attribute an April 2007 Iraq presence.* **Verified record — [Fact — B2]** Wired, 2 August 2007, reports that three SWORDS robots “have deployed to Iraq, armed with M249” machine guns—the first time, the magazine says, machines have carried guns in a war zone. https://www.wired.com/2007/08/httpwwwnational/ An archived National Defense piece (August 2007) states the three robots “have been in Iraq since April” with 3rd Infantry Division, 3rd Brigade, were formally approved for combat use in June, and that 80 more approved under urgent materiel release lacked FY06–07 funding (Lt. Col. William Wiggins, ASA(ALT)). The April date is therefore a later reconstruction, not an April primary. **Threat landscape.** A remotely piloted, rifle-armed ground robot on an Iraqi street changes the acting layer: the soldier is no longer the only trigger in the stack. Safety, radio lag, and kill-switch design become the trust boundary. **Intelligence assessment.** [Assessment — moderate confidence] Three SWORDS are in Iraq by late spring. [Inference — moderate confidence] They will be used first for reconnaissance and presence, not as a funded program of record. [Uncertainty] No April 2007 Army release confirming arrival or missions was fetched; weapons have not been publicly reported as fired. **Opportunity.** An April 3rd ID or ARDEC release would have made this an A1 April fact. **LRRK relevance.** Lab/KAT: first public armed-acting robot in a U.S. combat theater. Watch: record April as the later-attributed arrival month; do not invent a firefight. **Confidence.** Moderate on April presence (two later outlets); low on missions and firing status. ## 02. Reaper still a training airframe — combat “by this summer” is still a target *Event / publication dates: 13 March Creech arrival; no April combat primary.* **Verified record — [Fact — B1]** Air Force News attributed the first Creech MQ-9 arrival to 13 March and quoted the 42nd ATKS commander targeting combat by summer. No April 2007 Air Force release fetched this filing announces a Reaper combat sortie or IOC. **Threat landscape.** Hunter-killer payload exists in Nevada, not yet over Afghanistan or Iraq. The C2 pattern (remote split) is already combat-proven on Predator. **Intelligence assessment.** [Assessment — high confidence] No April combat. [Inference — moderate confidence] May wing standup is the next organizational fact. [Uncertainty] April Reaper flight hours unpublished. **Opportunity.** 42nd ATKS April training-hour note. **LRRK relevance.** Watch: keep Reaper on the training line until a combat or IOC primary. **Confidence.** High on absence of an April combat primary; moderate on the summer target. ## 03. Joint CONOPS is one month old — allocation visibility still the GAO problem *Event / publication dates: March 2007 Joint CONOPS; GAO fieldwork running through June.* **Verified record — [Fact — A1]** GAO-07-836 (issued 11 July) records the March Joint CONOPS and finds DOD still lacks DOD-wide advance coordination, a mechanism to see all theater and tactical ISR, and a complete metrics set. https://www.globalsecurity.org/intell/library/reports/gao/d07836.pdf **Threat landscape.** Paper exists; the surge is already producing the integration failures GAO will print in July. **Intelligence assessment.** [Assessment — high confidence] CONOPS did not solve tasking visibility. [Inference — moderate confidence] Duplicative Hunter/Predator taskings will continue. [Uncertainty] April JFACC/tactical database status unpublished. **Opportunity.** CENTCOM April ISR CONOPS compliance report. **LRRK relevance.** Control Fabric: doctrine ≠ picture. **Confidence.** High on GAO’s later diagnosis applying to this month’s structure. ## 04. ER/MP still SDD — Army persistence remains borrowed *Event / publication dates: 10 August 2005 award unchanged.* **Verified record — [Fact — A1]** Team Warrior SDD: 17 aircraft, seven GCS, mid-2009. https://www.ga-asi.com/general-atomics-aeronautical-systems-and-its-team-warrior-partners-awarded-major-u-s-army-contract **Threat landscape.** No April public ER/MP combat line. **Intelligence assessment.** [Assessment — high confidence] Continuity. [Inference — moderate confidence] Warrior-Alpha / contractor lines remain the Army’s 2007 persistence. [Uncertainty] April Alpha orbits unpublished. **Opportunity.** PEO Aviation April SAR extract. **LRRK relevance.** Lab: do not move ER/MP to “fielded.” **Confidence.** High on contract; low on April hardware. ## 05. UUV and export quiet *Event / publication dates: 2004 UUV Master Plan still current; MTCR Category I unchanged; Hydroid $26 million award is 15 May.* **Verified record — [Fact — B2]** No April 2007 Navy UUV master-plan update or MTCR plenary was fetched. The next hard undersea industrial fact is Hydroid’s 15 May DoD REMUS sustainment award. **Threat landscape.** Undersea and export-control clocks are not the Iraq clock. **Intelligence assessment.** [Assessment — high confidence] No April public change. [Inference — low confidence] May will be the REMUS and (separately) ROK/Global Hawk month. [Uncertainty] April license actions unpublished. **Opportunity.** NAVSEA April contract list. **LRRK relevance.** Watch: next month’s Hydroid award; next month’s Korea Times MTCR piece. **Confidence.** High on continuity. ## Forward indicators Ranked watchlist as of the collection cutoff (what a 2001–2011 Watch desk would have monitored next). 1. 1 May 432nd Wing activation at Creech. 2. Any Army confirmation of SWORDS location, ROE, or firing. 3. First Reaper combat or IOC notice. 4. Hydroid REMUS sustainment award (industry chatter). 5. ROK/Global Hawk MTCR diplomacy. > **Collection integrity.** April is thin on contemporaneous primaries. SWORDS April dating is taken from August 2007 Wired/National Defense and is labeled as later reconstruction. Refused: any claim that SWORDS fired in April; any Reaper combat date before 25 September; undated encyclopedia robot inventories. *LRRK — security assurance for systems that sense, move, and act.* <p align="right"><span style="opacity:0.35;letter-spacing:0.18em;font-size:0.8em">L-C1</span></p>