Conversation

“JADC2, explained Abadie, progresses the discussion from kill chains to kill webs. Instead of having a single, linear pipeline from one sensor to one shooter, the kill web creates a network of pathways that can connect any sensor to the best shooter”
Quote Tweet
At second Project Convergence, US Army experiments with joint operations in the Arizona desert c4isrnet.com/battlefield-te
5
7
They claim to have gotten response time down from 20min to 20sec. Without knowing the details of the claim, I kinda believe it. Things were already headed towards this web direction when I was working on this stuff in 2004-06. It’s like a fat protocol instead of thin.
2
1
Back then the kill chain (FFTTEA — find-fix-track-target-engage-assess) was assumed to pass through a centralized tasking step at theater level, like a JSTARS aircraft. This is a bit like Soviet central planning. Sounds like they’ve decentralized this a bit in this “web” concept.
1
1
But if you’ve got enough loitering assets, and a surplus, then statistically the tasking would be faster if you had a kind of bidding system, “anyone want to kill this?” “I can do it” within a broad mission like persistent area denial aka hit anything that moves.
2
3
In effect you’ll have a giant network doing a kind of Hebbian learning in a theater. Tasking patterns already done will likely trigger faster. Skynet/Matrix type stuff. Grim, but things have been headed this way for 30 years now.
Replying to
Modern antiwar movement rightly focuses on the troubling rise of this kind of instant precision-killing integrated machine at the disposal of every major military, but it’s important to acknowledge the progress — it’s less terrible than shit like the Dresden firebombing of WW2.
1
4
The fact that we’ve gone from civilian casualties and collateral damage being counted in anonymous aggregate ways (“15,000 people killed and hundreds of buildings destroyed”) to named, micro ways (“Hamid’s wedding party mistakenly tagged as a terrorist cell”) is grim progress.
1
6