Sensor A → Fusion → Authority → Path A → Effector A → Assessment
AvailableSYSTEMS / COMMAND / RESILIENCE
Kill Webs: Architecture, Resilience, and Authority
An evidence-qualified atlas of composable battle networks, DARPA ACK, JADC2, technical dependencies, cyber resilience, AI decision support, procurement, and governance.
The collection treats the kill chain as the ordered mission process and the kill web as the changing option space around it. It preserves the reports’ central insight—optionality under disruption—while separating technical reachability, data quality, identity, command authority, lawful use, and public evidence.
DIRECT ANSWER / EVIDENCE BOUNDARY
Kill webs in brief
- What is a kill web?
- A networked mission architecture containing alternative combinations of sensors, data services, command nodes, communications paths, support functions, and effectors.
- Does it replace the kill chain?
- No. A mission still executes through a specific chain. The web supplies more than one possible chain and can recompose the path under disruption.
- What does this collection not establish?
- It does not prove current classified configurations, universal latency requirements, unrestricted autonomous lethal authority, or seamless joint interoperability.
INTERACTIVE / SYNTHETIC / NON-OPERATIONAL
Path-resilience lab
Toggle abstract node failures to see the difference between one fixed path and a small web of alternatives. The model is deliberately generic: it teaches common-mode dependency, not real mission planning.
Available
Unavailable
Shared dependency
Complete routes
1
One complete route remains; the architecture has no additional path margin.
Path diversityLow
Shared bottlenecks6
Independent sensing sources1
Assessment coveragePresent
Common dependencies: Sensor A, Fusion, Authority, Path A, Effector A, Assessment
SenseSensor A
Make senseFusion
DecideAuthority
TransportPath A
ActEffector A
LearnAssessment
SenseSensor A
SenseSensor B
Make senseFusion
Make senseEdge
Shared decision dependencyAuthority
TransportPath A
TransportPath B
ActEffector A
ActEffector B
Shared learning dependencyAssessment
Sensor A → Fusion → Authority → Path A → Effector A → Assessment
AvailableSensor B → Edge → Authority → Path B → Effector B → Assessment
AvailableSensor A → Edge → Authority → Path B → Effector B → Assessment
AvailableSensor B → Fusion → Authority → Path A → Effector A → Assessment
AvailableThe authority and assessment nodes are intentionally shared. A web with many visible paths can still fail at one common dependency.
FROM CONNECTIVITY TO GOVERNED CHOICE
Two decision labs and two observatories test the complete thread
The path lab counts surviving routes. The capability marketplace tests eligibility before ranking. The assurance lab asks what evidence proves a complete thread. The evidence observatory preserves public unknowns, while the interoperability observatory tests whether meaning, releasability, human intervention, and lifecycle control survive the handoffs.
A high score cannot override a failed authority, identity, provenance, releasability, or assessment gate.
Capability Marketplace Lab
Apply fictional degradation, release, authority, assessment, and capacity conditions. Hard gates remove ineligible packages before a transparent comparative score is calculated.
Open the marketplace labMission-Thread Assurance Register
Filter twelve assurance checks across authority, data, infrastructure, the human-machine system, recovery, and institutional accountability.
Open the assurance registerNEW / MISSION-THREAD ASSURANCE
Test the difference between connectivity and a governed mission thread
The Mission-Thread Assurance Lab combines a resilience scorecard, authority map, integrity stress test, ACK marketplace explainer, and procurement controls in one non-operational, client-local experience.
Open the assurance lab- Eight-dimension mission-thread scorecard
- Function-by-function authority map
- Integrity and graceful-degradation stress test
- ACK marketplace and procurement explainers
NEW / EVIDENCE AND DEGRADED-MODE OBSERVATORY
Kill Webs Evidence and Degraded-Mode Observatory
Trace forty-seven evidence-qualified findings to the thirteen retained reports, then test how a synthetic mission thread should change behavior when identity, time, semantics, transport, provenance, or assessment can no longer be trusted.
Open the evidence observatory- Forty-seven evidence-qualified findings
- Five explicit evidence states
- Thirteen retained-report source trails
- Seven synthetic degraded-mode conditions
NEW / INTEROPERABILITY CONTRACTS
Observe what a connected mission thread can still misunderstand
The Interoperability Observatory exposes semantic loss, coalition release boundaries, nominal human control, and acquisition lock-in through four deterministic public tools.
Open the interoperability observatory- Eight-field semantic exchange contract
- Three-role coalition release views
- Five-dimension human-intervention diagnostic
- Seven-stage procurement lifecycle proof
FOUR RESEARCH CORRIDORS
One architecture, four different evidence problems
The collection separates composition and architecture, joint institutions and acquisition, and automation and resilience so that technical reach is never confused with command authority or operational maturity.
Concepts and orchestration
Separate the ordered mission process from the option space, then examine how ACK-style capability discovery can compose alternatives without becoming command authority.
Joint enterprise and technical backbone
Place the kill web inside JADC2 and trace the data, transport, edge, identity, interface, timing, and test requirements that make a mission thread usable.
Resilience, integrity, and autonomy
Examine silent integrity failure, cyber and electromagnetic disruption, uncertainty multiplication, automation bias, bounded autonomy, and meaningful intervention.
Acquisition, governance, and assurance
Connect platform-centric incentives, data rights, shared infrastructure, mission-level accountability, degraded-mode testing, authority, and public evidence boundaries.
EIGHT ARCHITECTURE LAYERS
Connectivity becomes a mission system only when every layer agrees
A capability marketplace cannot compensate for stale data, an untrusted identity, a broken command relationship, an unavailable transport path, or a control loop placed too far from the edge.
Mission purpose and authority
Objectives, legal constraints, command relationships, delegated permissions, and termination conditions define which technical paths are actually usable.
Capability model and discovery
Machine-readable descriptions must expose what a node can provide, under which limits, with what availability, quality, capacity, and releasability.
Data semantics and provenance
Tracks, observations, confidence, age, classification, source lineage, and uncertainty must retain consistent meaning across organizations and systems.
Resilient transport, PNT, and time
Multiple communications paths are useful only when identity, timing, priority, position, navigation, and synchronization remain trustworthy under degradation.
Edge, regional, and cloud computing
Functions must be placed according to mission-specific latency and disconnection tolerance; tightly bounded control loops cannot depend on a distant enterprise service.
Orchestration and decision support
Software may compare authorized combinations and surface tradeoffs, but it must preserve uncertainty, constraints, provenance, and realistic opportunities for human rejection or delay.
Effects, support, and legacy integration
Open interfaces, translation services, data rights, modularity, logistics, and support capabilities determine whether a recommended path can become an executable mission thread.
Assessment, testing, and adaptation
End-to-end mission-thread tests must cover cyber, electronic warfare, timing loss, data poisoning, authority changes, coalition constraints, and graceful degradation—not only nominal connectivity.
EVIDENCE AND SAFETY GUARDRAILS
Seven distinctions that keep architecture from becoming mythology
Process is not topology
A kill chain describes required mission functions; a kill web describes possible nodes and pathways. The collection never treats one as a simple replacement for the other.
Connectivity is not authority
A technically reachable node is not automatically authorized, trusted, releasable, compatible, or lawful for a particular mission.
Capability is not fielded use
A concept, demonstration, manufacturer claim, transition statement, and routine operational behavior are different evidence states.
Automation, autonomy, and AI are distinct
Rule-based automation, navigation autonomy, machine learning, target recognition, selection, and authorization must be described function by function.
Time is mission-specific
Local control, tactical exchange, human decision support, and cross-domain resource allocation require different latency budgets. No universal public threshold is assumed.
Unknown remains visible
Classified or undisclosed settings, error rates, authority modes, fielding details, and dependencies remain publicly unspecified rather than being filled with confident inference.
Public-interest and non-operational
The site explains architecture, governance, resilience, and evidence. It excludes real target data, routes, frequencies, thresholds, exploit steps, weapon assignment, and defeat advice.
EIGHT RESEARCH ROUTES
Follow the pathway from definition to institutional implementation
Each route identifies its organizing report, separates public facts from synthesis and recommendations, and states what the evidence does not establish.
01
Conceptual synthesis
Concepts and orchestration
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.
- Organizing report
- Kill Web vs. Kill Chain: From Sequential Targeting Processes to Composable Battle Networks
- Evidence posture
- Cross-report conceptual synthesis with explicit public unknowns
02
Program analysis
Concepts and orchestration
Discover, compare, and reallocate capabilities across boundaries
An evidence-bounded explanation of DARPA’s Adapting Cross-Domain Kill-Webs program, its consumer–supplier marketplace analogy, bid-and-offer logic, Virtual Liaison abstraction, and the public limits on what is known about transition and fielding.
- Organizing report
- From Kill Chain to Kill Web: Operational Rationale, Technical Architecture, and the DARPA ACK Model
- Evidence posture
- Public program description plus cross-report architectural interpretation
03
Enterprise integration
Joint enterprise and technical backbone
JADC2 is the enterprise; the kill web is one composable operational thread
A joint-enterprise route separating the broader JADC2 framework—data, networks, people, doctrine, authorities, security, partners, and training—from the narrower mission pathways that connect sensing, decision, support, and effects.
- Organizing report
- Kill Webs as the Operational Engine of Joint All-Domain Command and Control
- Evidence posture
- Cross-service synthesis with program maturity kept explicit
04
Systems architecture
Joint enterprise and technical backbone
Semantics, transport, edge computing, identity, interfaces, and test
A systems view of the capability model, governed data fabric, multipath communications, cloud–edge continuum, mission-specific timing, zero-trust identity, modular interfaces, and realistic degraded-mode testing required before dynamic composition is credible.
- Organizing report
- The Architecture of Decision-Centric Warfare: Engineering the Transition from Kill Chains to Cross-Domain Kill Webs
- Evidence posture
- Architecture synthesis with recommended controls clearly labeled
05
Defensive risk analysis
Resilience, integrity, and autonomy
A connected web can fail silently through corrupted trust and data
A defensive architecture route covering identity, data and telemetry integrity, timing and positioning, electronic-warfare isolation, middleware, supply chain, cloud orchestration, AI manipulation, insiders, monitoring, and graceful degradation.
- Organizing report
- Cybersecurity Vulnerabilities and Non-Kinetic Disruption of Kill Web Architectures
- Evidence posture
- Defensive synthesis with attack detail deliberately excluded
06
AI and governance analysis
Resilience, integrity, and autonomy
Use AI to preserve options and uncertainty, not to hide authority
A layered analysis of perception, fusion, tracking, prediction, resource assignment, swarm coordination, uncertainty multiplication, automation bias, meaningful intervention, abstention, and independently enforced legal and policy constraints.
- Organizing report
- AI and Autonomy in Kill Webs
- Evidence posture
- Technical and governance synthesis with strong human-control cautions
07
Institutional analysis
Acquisition, governance, and assurance
The unit of accountability is smaller than the unit of mission value
An institutional route examining bounded platform programs, fragmented budgets, connective-tissue underfunding, contract incentives, data rights, modular open systems, software pathways, certification, continuous authorization, sustainment, and mission-level accountability.
- Organizing report
- Why Legacy Defense Procurement Struggles to Build Kill Webs
- Evidence posture
- Procurement and incentive synthesis with explicit analytical inferences
08
Governance and assurance
Acquisition, governance, and assurance
A system of systems needs mission-thread assurance and visible unknowns
A governance route connecting command authority, human judgment, safety and legal gates, configuration, identity, degraded-mode contracts, test infrastructure, auditability, public evidence labels, and the limits of demonstrations, transition claims, and classified performance.
- Organizing report
- From Kill Chain to Kill Web: Strategic Rationale, Technical Architecture, and DARPA’s ACK Program
- Evidence posture
- Governance synthesis with public-source and safety boundaries
COMPARATIVE VIEW
Compare the unit of analysis before comparing conclusions
A doctrine comparison, a DARPA program analysis, an enterprise architecture, a human-machine governance study, a defensive risk catalog, and an acquisition analysis answer different questions.
| Route | Genre | Unit of analysis | Evidence horizon | Evidence posture | First caution |
|---|---|---|---|---|---|
| A web composes chains; it does not abolish them | Conceptual synthesis | Mission process, technical topology, and command pathway | Current public concepts and architecture | Cross-report conceptual synthesis with explicit public unknowns | The term kill web has no single universally binding public technical definition. |
| Discover, compare, and reallocate capabilities across boundaries | Program analysis | Capability discovery, allocation, and orchestration | Public ACK program record and transition claims | Public program description plus cross-report architectural interpretation | Marketplace language is an analogy; military authority, risk, and legal review cannot be reduced to price. |
| JADC2 is the enterprise; the kill web is one composable operational thread | Enterprise integration | Joint enterprise and mission-thread integration | Current public JADC2/CJADC2 concepts | Cross-service synthesis with program maturity kept explicit | JADC2 is not one product, one network, or one command application. |
| Semantics, transport, edge computing, identity, interfaces, and test | Systems architecture | Data, transport, compute, trust, interface, and test layers | Current public engineering concepts | Architecture synthesis with recommended controls clearly labeled | More data can increase confusion when semantics, time, identity, or provenance do not agree. |
| A connected web can fail silently through corrupted trust and data | Defensive risk analysis | Mission dependencies, trust relationships, and degraded operation | Current architecture-level cyber and resilience risks | Defensive synthesis with attack detail deliberately excluded | A defensive risk taxonomy is not evidence that every listed vulnerability exists in every implementation. |
| Use AI to preserve options and uncertainty, not to hide authority | AI and governance analysis | Human-machine decision system and delegated functions | Near-term decision support and bounded autonomy | Technical and governance synthesis with strong human-control cautions | A model confidence value is not the probability that an action is lawful, necessary, proportionate, or strategically wise. |
| The unit of accountability is smaller than the unit of mission value | Institutional analysis | Acquisition portfolios, budgets, contracts, data rights, and sustainment | Current acquisition structure and reform options | Procurement and incentive synthesis with explicit analytical inferences | Open standards alone do not guarantee interoperability, competition, cybersecurity, or maintainability. |
| A system of systems needs mission-thread assurance and visible unknowns | Governance and assurance | Mission-thread assurance, authority, audit, and public claims | Lifecycle governance from design through operation and correction | Governance synthesis with public-source and safety boundaries | A demonstration proves only the tested conditions, not the full operational envelope. |
CROSS-CUTTING QUESTIONS
Questions every claimed web should be able to answer
-
01
How many apparently independent paths share one hidden identity, timing, cloud, gateway, or authority dependency?
-
02
How should a web represent evidence quality and uncertainty without collapsing them into one confidence score?
-
03
Which mission outcomes should own cross-service budgets and accountability?
-
04
What functions may continue safely when transport, identity, policy, or human intervention is unavailable?
-
05
How can public transparency distinguish capability, demonstration, transition, fielding, and authority without exposing sensitive details?
-
06
When does more composability improve resilience, and when does it increase complexity, attack surface, and correlated failure?
CONTROLLED VOCABULARY
Fourteen terms that should not be collapsed into one another
The vocabulary separates mission process, network topology, technical capability, operational authority, evidence status, and institutional implementation.
- Kill chain
- An ordered mission process connecting sensing, identification, decision, action, and assessment. F2T2EA is a common dynamic-targeting formulation.
- Kill web
- A changing network of heterogeneous nodes and potential connections from which one or more authorized mission chains can be composed.
- Mission thread
- The end-to-end combination of systems, data, people, authorities, interfaces, timing, and procedures needed to produce and assess one mission outcome.
- Optionality
- The availability of multiple valid courses or pathways so that loss of a preferred node narrows choices rather than ending the mission.
- Capability model
- A machine-readable description of what a node can provide, with quality, availability, dependencies, authority, timing, and constraints.
- Data fabric
- A governed set of services and standards that make data discoverable, understandable, distributable, protected, and traceable across systems.
- Virtual Liaison
- The ACK service abstraction described in the reports for advertising an effect, availability, and constraints across organizational boundaries.
- JADC2 / CJADC2
- The broader joint or combined enterprise for sensing, making sense, and acting across domains, including data, networks, policy, people, security, partners, and command.
- Graceful degradation
- A designed reduction in capability that preserves safe and useful functions instead of producing sudden total failure or untrusted operation.
- Fencing and authority gate
- A control that prevents stale, unauthorized, incompatible, or superseded actors from committing a transition or executing a consequential function.
- Meaningful human judgment
- Human involvement with enough information, time, authority, interface support, and practical intervention ability to affect the outcome.
- Integrity failure
- A condition in which data or control remain available but are false, stale, manipulated, misbound, or insufficiently trusted.
- MOSA
- Modular Open Systems Approach: an acquisition and engineering strategy using separable modules, defined interfaces, and life-cycle competition rather than one closed monolith.
- Publicly unspecified
- A deliberate evidence state for information that public sources do not establish, such as exact operating modes, thresholds, fielding details, or error rates.
HOW TO READ THE COLLECTION
Follow the source state, not the drama of the terminology.
- Preserve each submitted report in /docs with a source checksum before synthesizing it.
- Treat the reports as research inputs, not automatic verification of every citation or claim.
- Separate process, topology, technical capability, fielding, command authority, and legal sufficiency.
- Use evidence labels for report-supported synthesis, analysis, caution, recommendation, and publicly unspecified details.
- Remove operationally sensitive detail and convert scenarios into generic, synthetic, accessible models.
- Preserve English and Spanish event identity, numbers, evidence state, uncertainty, and source mapping while allowing idiomatic wording.
- Keep disagreement, unresolved parameters, and architectural tradeoffs visible rather than averaging them into certainty.
RETAINED SOURCE REGISTER
Thirteen submitted research reports
The retained reports organize the inquiry and preserve their own source trails. This collection treats them as research inputs rather than automatic verification of every embedded claim or citation.
-
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 concept and website report
The Architecture of KillWebs.com: Operationalizing the Shift from Linear Chains to Dynamic Combat Networks
Submitted website-strategy report. It informs public explanation, interaction design, and graph-oriented presentation; technical and historical claims remain subject to fresh verification before being stated as fact.
-
Submitted defensive analysis
The Vulnerability Surface of Kill Web Architectures: Non-Kinetic Disruption and Defense Strategies in Joint All-Domain Command and Control
Submitted defensive-analysis report covering cyber, electromagnetic, timing, middleware, and zero-trust risks. The public synthesis retains only architecture-level defensive lessons and excludes exploit procedures.
-
Submitted procurement analysis
The Architecture of Friction: Why Legacy Defense Procurement Struggles to Build Kill Webs
Submitted procurement analysis. It describes platform-centric incentives, budget fragmentation, open-architecture policy, and software acquisition using a mixture of sourced findings and interpretation.
-
Submitted AI and autonomy analysis
Algorithmic Warfare and the Evolution of the Kill Web: AI-Driven Decision-Making, Autonomous Swarms, and Strategic Stability
Submitted AI-and-autonomy report. It organizes technical methods, legal questions, automation-bias risks, and strategic-stability concerns; numerical or program-specific claims require independent confirmation before reuse.
-
Submitted joint-integration analysis
The Algorithmic Battlespace: Architecting the Kill Web and the Future of Combined Joint All-Domain Command and Control
Submitted JADC2 integration report. It supplies service, space, coalition, data-fabric, and mission-thread framing; scenario details are treated as illustrative rather than operational fact.
-
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.
-
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 procurement analysis
Why Legacy Defense Procurement Struggles to Build Kill Webs
Submitted acquisition-reform report. It distinguishes statutory tools from the broader organizational, budgetary, data-rights, certification, sustainment, and incentive problems that shape a system of systems.
-
Submitted defensive analysis
Cybersecurity Vulnerabilities and Non-Kinetic Disruption of Kill Web Architectures
Submitted defensive architecture report. It emphasizes identity, data integrity, time, supply-chain, electronic-warfare, AI, cloud, and insider risks, along with monitoring and resilience exercises.
-
Submitted AI and autonomy analysis
AI and Autonomy in Kill Webs
Submitted AI decision-support report. It argues for uncertainty and provenance preservation, independent constraint gates, abstention, realistic human-machine testing, and bounded autonomy.
-
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 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.
AUTONOMY / AUTHORITY / HANDOFFS
A dynamic web still needs bounded authority at every handoff.
Continue from network optionality into autonomy, target-decision functions, and authority migration.
The Autonomous Systems atlas extends this collection into predictive target nomination, lost-link behavior, swarms, meaningful human intervention, and the difference between resource composition and permission to use force.