The canonical definition
KillWebs.com uses kill web to mean a reconfigurable system of sensing, data, communications, processing, command, support, effect, and assessment capabilities. The network exposes possible relationships, but only a subset are technically compatible, sufficiently trusted, operationally available, and authorized at any moment.
A kill chain is the selected path through that network for a particular mission. The web is the option space; the chain is the executable sequence. This relationship is central to the uploaded research corpus and prevents a common false choice between linear process and network architecture.
Why the model changes
Optionality under disruption
When a preferred sensor, relay, data service, headquarters, or effect node becomes unavailable, the architecture can search for another valid combination rather than assuming the mission must end.
Later binding
The force delays some pairing decisions until current availability, confidence, communications, risk, capacity, and authority are known.
Distributed execution
Time-sensitive functions can remain at the edge while broader optimization, governance, and history live at theater or enterprise tiers.
Cross-domain composition
Capabilities may contribute according to the effect or service they provide, not only the organization or platform that owns them.
A web is not uncontrolled all-to-all connectivity
The slogan “any sensor, any shooter” is useful for challenging organizational stovepipes, but it is a poor literal engineering requirement. Full connectivity would create congestion, attack surface, ambiguity, and combinations that are technically possible but operationally or legally invalid.
The more defensible objective is selective reachability: qualified data should become discoverable to compatible and authorized consumers through an acceptable path within the relevant time window.
- A visible edge does not prove semantic compatibility.
- A compatible message does not prove the source is trustworthy.
- A trustworthy observation does not create engagement authority.
- An authorized capability may still be unavailable, reserved, or outside its safe operating bounds.
- Several paths may share one hidden dependency and therefore provide little true resilience.
What remains ordered
Actual decisions still require ordered dependencies. Evidence must be collected and interpreted; identity and confidence must be assessed; authority must be established; an action must be executed; and the result must be evaluated. Those functions can overlap or repeat, but their responsibilities do not disappear because the architecture is networked.
The web is most useful when it preserves several lawful and technically valid ways to satisfy those functions while keeping the final path explainable and auditable.
Research basis: KW-RPT-002, KW-RPT-009, and KW-RPT-014.