01 / Conceptual synthesis
Kill Chain and Kill Web: Process Versus Option Space
A precise comparison showing that F2T2EA remains an ordered mission process while a kill web supplies multiple possible sensor, decision, support, transport, and effect pathways from which one chain can be selected.
DIRECT ANSWER / EVIDENCE BOUNDARY
Route in brief
- Central claim
- The chain is the executed route; the web is the changing, constrained option space. Resilience comes from retaining alternative authorized pathways, not from replacing process discipline with indiscriminate connectivity.
- Evidence posture
- Cross-report conceptual synthesis with explicit public unknowns
- Primary boundary
- The term kill web has no single universally binding public technical definition.
DEFINITION AND CENTRAL CLAIM
A web composes chains; it does not abolish them
A precise comparison showing that F2T2EA remains an ordered mission process while a kill web supplies multiple possible sensor, decision, support, transport, and effect pathways from which one chain can be selected.
Central claim
The chain is the executed route; the web is the changing, constrained option space. Resilience comes from retaining alternative authorized pathways, not from replacing process discipline with indiscriminate connectivity.
EVIDENCE-QUALIFIED SYNTHESIS
What the retained material supports
Labels distinguish documented public records, architectural synthesis, cautions, recommendations, and publicly unspecified details. A citation does not erase the qualification in the sentence.
SUPPORTED BY SUBMITTED REPORTS
The submitted reports consistently retain the ordered find, fix, track, target, engage, and assess functions; the architectural change is that those functions need not be bound in advance to one sensor, headquarters, network, and effector. [13] [1] [8]
CROSS-REPORT ANALYSIS
At the moment of execution, one pathway through the web still behaves as a chain. The web changes when and how that pathway is assembled, compared, rerouted, and audited. [13] [12]
EVIDENCE CAUTION
A physically distributed architecture can remain logically centralized if every route depends on one cloud, identity service, fusion engine, gateway, classification domain, or approval authority. [13] [7]
SUPPORTED BY SUBMITTED REPORTS
The recurring strategic claim is optionality under disruption: losing a preferred node should narrow the option set rather than automatically terminate the mission. [1] [8] [12]
RECOMMENDED CONTROL
The practical objective should be the best authorized, compatible, sufficiently trusted, and operationally available pathway—not a literal rule that every sensor must connect to every shooter. [13] [12]
PUBLIC-INTEREST IMPLICATIONS
What responsible institutions can do with this evidence
- Model the doctrinal process and the technical graph separately, then show how an authorized mission thread binds them.
- Measure alternative valid pathways, shared dependencies, and graceful degradation rather than raw connection count.
- Expose which authority, identity, data-quality, and release conditions make a technical edge usable.
- Keep selected-path audit records so post-action review can reconstruct why one chain was chosen from the web.
EVIDENCE CAUTIONS
What this route should not be used to claim
- The term kill web has no single universally binding public technical definition.
- A robust chain may contain redundancy, while a nominal web may contain hidden single points of failure.
- Topology does not by itself establish command authority, legal sufficiency, target validity, or accountability.
- The public collection does not reproduce operational mission graphs or real system dependencies.
OPEN QUESTIONS
Questions the current public record does not settle
An open question is not a prediction, a finding, or proof that a capability is fielded in the configuration described.
- Which dependencies are common to every apparently independent pathway?
- How should a commander compare speed, confidence, reversibility, cost, and political risk across candidate pathways?
- When does additional connectivity increase resilience, and when does it increase correlated failure?
- What evidence would prove that a rerouted path remains authorized and sufficiently trusted?
RETAINED SOURCES
Selected records underlying this public synthesis
Submitted reports, official program descriptions, doctrine, policy, oversight, and public research are labeled separately. Inclusion is not blanket endorsement.
-
Submitted comparative analysis
Kill Web vs. Kill Chain: From Sequential Targeting Processes to Composable Battle Networks
Submitted comparative report. It provides the collection’s clearest process-versus-topology distinction and cautions that connectivity, resilience, command authority, and lawful use are separate variables.
-
Submitted architecture report
From Kill Chain to Kill Web: Operational Rationale, Technical Architecture, and the DARPA ACK Model
Submitted architecture report. It distinguishes documented public facts, architectural synthesis, and recommended engineering targets; this release preserves those distinctions and does not independently reverify every cited source.
-
Submitted architecture report
From Kill Chain to Kill Web: Strategic Rationale, Technical Architecture, and DARPA’s ACK Program
Submitted executive architecture report. It is especially useful for the optionality argument, mission-specific timing, ACK boundaries, and unresolved public parameters.
-
Submitted joint-integration analysis
Kill Webs as the Operational Engine of Joint All-Domain Command and Control
Submitted joint-integration report. It treats JADC2 as the broader enterprise and the kill web as a composable mission thread spanning data, transport, authorities, services, partners, and effects.
-
Submitted architecture report
The Architecture of Decision-Centric Warfare: Engineering the Transition from Kill Chains to Cross-Domain Kill Webs
Submitted engineering architecture report. It covers modular hardware, edge computing, transport, middleware, capability orchestration, and centralization risk at a conceptual level.