Educational companion dossier · Fact, interpretation, lived experience, clinical education, fiction, and mechanics are labeled separately. Scope & safety
PsychologicalWar.orgHistory before hype.
REAL-WORLD INTERPRETIVE

AI KILL CHAINS & DECISION SYSTEMS

Testing Kill Web Resilience: Mission Threads, Fault Injection, and Authority Under Degradation

Kill webs should be tested as evolving mission threads under compound degradation, not only as individually compliant components connected in a demonstration.

Read the working brief Choose a learning path
REAL-WORLD INTERPRETIVE

ANALYTICAL & SAFETY BOUNDARIES

Keep related capabilities, evidence, and authority states separate.

  • A kill chain is a mission process or selected path; a kill web is the changing option space from which paths may be composed.
  • JADC2/CJADC2 is broader than a kill web and includes doctrine, people, authorities, training, policy, security, and enterprise data.
  • Technical connectivity, mission validity, delegated authority, and legal permission are separate conditions.

Analytical boundary: A web does not abolish chains. Connectivity does not create authority. Capability is not deployment; recommendation is not authorization; classification confidence is not positive identification; redundancy is not guaranteed resilience.

Simulation safety boundary: Synthetic identities, abstract nodes, fictional infrastructure, nonfunctional controls, and defensive governance only. No real targets, coordinates, payloads, waveforms, vulnerabilities, defeat advice, or external execution.

Source basis: Thirteen exact owner-supplied reports plus bounded official-primary-source currentness v16.

LEVEL 1

ORIENTATION

Why this matters

REAL-WORLD INTERPRETIVE

One-sentence brief

The architecture can pass interface tests while failing when timing, identity, data quality, authority, capacity, and communications degrade at the same time.

REAL-WORLD INTERPRETIVE

Three key points

  1. Use mission-thread digital twins and deterministic replay.
  2. Inject node, link, timing, data, model, key, and authority failures together.
  3. Measure graceful degradation, abstention, recovery, audit completeness, and operator understanding.
LEVEL 2

WORKING BRIEF

Evidence, context, and limits

REAL-WORLD INTERPRETIVE

Mission-thread contracts

Each thread should declare required functions, data quality, latency budgets, authority, allowed substitutions, dependencies, fail states, recovery objectives, and evidence retained for audit.

  • No universal latency budget applies to every function.
  • A component can meet its requirement while the mission thread fails.
REAL-WORLD INTERPRETIVE

Compound fault and deception testing

Exercises should combine packet loss, delay, stale data, spoofed timing, identity revocation, model drift, corrupted telemetry, unavailable services, and overloaded operators.

  • Independent single-fault tests understate interaction risk.
  • Red-team findings require remediation and retest, not only documentation.
REAL-WORLD INTERPRETIVE

Authority under degradation

Testing must show what happens when command links, evidence quality, supervision, or policy services disappear. The expected response may be continue a reversible task, hold, return, abstain, isolate, or terminate—not silently expand authority.

  • Loss of communication is not new permission.
  • Safe state must be function-specific and tested.
REAL-WORLD INTERPRETIVE

Replay, correction, and reopening

Append-only event records, signed configuration identity, source provenance, deterministic scenario replay, correction dependency maps, and reopening triggers allow investigators to reconstruct what each participant and service knew.

  • Auditability is not correctness.
  • A visible correction is not full downstream repair.
LEVEL 3

COMPLETE DOSSIER

Limitations, game links, and review context

DISPUTED / MULTIPLE ACCOUNTS

Known limitations and gaps

  • Public sources do not disclose many operational parameters, algorithms, authorities, field configurations, or test results.
  • Owner-supplied reports are preserved exactly but their embedded external citations are not silently certified.
  • The pages explain architecture, evidence, risk, governance, and defense; they exclude real targets, exploit procedures, weapon settings, and system-defeat instructions.
LEVEL 4

RESEARCH EDITION

Sources, methods, and stable links

REAL-WORLD INTERPRETIVE

Linked reports

  • From Kill Chain to Kill Web Operational Rationale, Technical Architecture, and the DARPA ACK Model.mdProtected research reference; no public report route in this release.
  • KillWebs Concept Website Strategy.mdProtected research reference; no public report route in this release.
  • Kill Web Vulnerabilities And Defense.mdProtected research reference; no public report route in this release.
  • Defense Procurement and Kill Webs.mdProtected research reference; no public report route in this release.
  • AI Autonomy in Kill Webs.mdProtected research reference; no public report route in this release.
  • Kill Webs and JADC2 Integration.mdProtected research reference; no public report route in this release.
  • Military Kill Web Architecture.mdProtected research reference; no public report route in this release.
  • From Kill Chain to Kill Web Strategic Rationale, Technical Architecture, and DARPA’s ACK Program.mdProtected research reference; no public report route in this release.
  • Why Legacy Defense Procurement Struggles to Build Kill Webs.mdProtected research reference; no public report route in this release.
  • Cybersecurity Vulnerabilities and Non-Kinetic Disruption of Kill Web Architectures.mdProtected research reference; no public report route in this release.
  • AI and Autonomy in Kill Webs.mdProtected research reference; no public report route in this release.
  • Kill Webs as the Operational Engine of Joint All-Domain Command and Control.mdProtected research reference; no public report route in this release.
  • Kill Web vs. Kill Chain From Sequential Targeting Processes to Composable Battle Networks.mdProtected research reference; no public report route in this release.
REAL-WORLD VERIFIED

Method and corrections

This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.

Read the methodView corrections
NEXT

CONTINUE

Related learning

AI Kill Chains & Decision Systems90 Seconds: Human Command Versus Machine-Speed WarfareA synthetic three-mode comparison showing how manual, AI-assisted, and preauthorized defensive architectures distribute speed, workload, and authority differently.AI Kill Chains & Decision SystemsAI and Autonomy in Kill Webs: Bounded Recommendations and Preserved UncertaintyAI is most defensibly used as layered perception, fusion, prediction, uncertainty estimation, and constrained recommendation—not as an unbounded replacement for legal, command, or contextual judgment.AI Kill Chains & Decision SystemsAI Kill Chains: Systems, Evidence, Human Control, and DefenseA neutral map of AI-system attacks, AI-enabled military decision systems, kill chains, kill webs, JADC2, lifecycle human control, cybersecurity, procurement, evidence, and safe simulation.AI Kill Chains & Decision SystemsAI-Enabled Military Targeting: Functions, Authority, and RiskA neutral, non-operational explanation of where AI can assist sensing, fusion, classification, prioritization, assignment, guidance, and assessment—and why those functions do not all transfer the same authority. Learning pathKill Webs: Architecture, Resilience, Evidence, and AccountabilityMove from the kill-chain process to composable mission networks, DARPA ACK, JADC2, data and trust architecture, non-kinetic vulnerabilities, bounded AI autonomy, procurement friction, compound-failure testing, and public evidence control.
Page complete Testing Kill Web Resilience: Mission Threads, Fault Injection, and Authority Under Degradation Page label: REAL-WORLD INTERPRETIVE