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

AI KILL CHAINS & DECISION SYSTEMS

Safe 3D and VR Simulation of AI Kill Chains

An event-driven instructional architecture for desktop and WebXR that teaches causality, uncertainty, defensive intervention, and governance without becoming an attack-execution or targeting platform.

REAL-WORLD INTERPRETIVE

ANALYTICAL & SAFETY BOUNDARIES

Keep related capabilities, evidence, and authority states separate.

  • attacks against AI systems
  • AI as a conventional cyber enabler
  • AI-enabled military targeting

Analytical boundary: AI kill chain is used here as a family of analytical models. Attacks against AI systems, AI as a conventional cyber enabler, and AI-enabled military targeting are related but distinct subjects. Capability is not deployment; deployment is not autonomy; classification confidence is not positive identification; recommendation is not authorization; a simulation is not operational evidence.

Simulation safety boundary: Use synthetic identities, reserved domains, fictional infrastructure, nonfunctional artifacts, abstract effects, and constrained defensive actions. Do not accept executable scripts, malware, credentials, arbitrary external URLs, real targets, command execution, or contact with third-party systems.

Source basis: Owner-supplied exact source packet with bounded official-primary-source currentness; external claims remain subject to stated source and review limits.

LEVEL 1

ORIENTATION

Why this matters

REAL-WORLD INTERPRETIVE

One-sentence brief

Immersive views can reveal dependencies and lateral propagation hidden in a flat diagram, but spectacle, cognitive overload, unsafe authoring, or real-system connectivity can undermine the educational purpose.

REAL-WORLD INTERPRETIVE

Three key points

  1. Keep the server authoritative and accept only constrained instructional commands.
  2. Use synthetic actors, reserved domains, fictional infrastructure, nonfunctional artifacts, and abstract effects.
  3. Provide desktop, keyboard, reduced-motion, no-JavaScript, and non-spatial alternatives for essential learning.
LEVEL 2

WORKING BRIEF

Evidence, context, and limits

REAL-WORLD INTERPRETIVE

Authoritative event model

Clients request constrained actions such as inspect indicator, compare evidence, apply control, pause, advance, or replay. The server validates authorization and scenario rules, appends an immutable event, derives the next state, and broadcasts a bounded state delta. The client never supplies executable code or authoritative outcomes.

GAME MECHANIC
Fictional exercise

Deterministic replay supports after-action explanation and testability.

REAL-WORLD VERIFIED

Safe scenario content

Scenario authoring rejects scripts, shell syntax, executable attachments, arbitrary HTML, external model or media URLs, credentials, malware, real targets, and unreviewed connections. Imported 3D assets are transcoded, validated, budgeted, and quarantined before publication.

GAME MECHANIC
Fictional exercise

A two-person review is required for realistic, organization-specific, exportable, or range-linked scenarios.

REAL-WORLD INTERPRETIVE

Spatial meaning without spectacle

Nodes represent sources, models, memories, tools, human gates, controls, and effects. Edges show data flow, authority, uncertainty, and trust boundaries. Animation is useful only when it explains temporal sequence or propagation; decorative motion should yield to reduced-motion preferences.

GAME MECHANIC
Fictional exercise

The same event ledger drives 3D, 2D, table, and text views.

REAL-WORLD INTERPRETIVE

Privacy, accessibility, and learner protection

Head pose, hand movement, gaze, voice, room mapping, and performance history can be sensitive. Collect only what the learning objective requires, minimize retention, disclose use, support withdrawal, and avoid inferring mental state. Essential content remains available without a headset or biometric telemetry.

GAME MECHANIC
Fictional exercise

Accessibility and privacy controls are part of the scenario contract rather than optional polish.

LEVEL 3

COMPLETE DOSSIER

Limitations, game links, and review context

DISPUTED / MULTIPLE ACCOUNTS

Known limitations and gaps

  • The phrase AI kill chain has multiple meanings and no single universal definition.
  • Public descriptions of military and security systems are incomplete, uneven, and often mix doctrine, demonstrations, manufacturer claims, and deployment evidence.
  • These pages explain capability, uncertainty, defense, governance, and simulation boundaries; they do not provide operational attack or targeting instructions.
GAME MECHANIC

RogueIntelligence.org connections

No game connection is required to use this educational page.

REAL-WORLD INTERPRETIVE

Publication audit checklist

Execution boundary

Can any client content become code, a real request, or contact with a third-party system?

Pass condition: No; only schema-validated instructional commands can change synthetic scenario state.

Evidence boundary

Are doctrine, claims, demonstrations, deployment, and effects visibly separate?

Pass condition: Each record carries source authority, supported proposition, prohibited inference, and uncertainty.

Human authority

Does the simulation show who may authorize, reject, abort, or reopen action?

Pass condition: Every irreversible transition has an explicit authority and intervention model.

Accessibility

Can a learner complete the essential lesson without VR, animation, pointer precision, or JavaScript?

Pass condition: Equivalent text, table, keyboard, reduced-motion, and desktop paths are available.

Privacy

Is XR telemetry minimized and prevented from becoming mental-state inference?

Pass condition: Only necessary telemetry is collected with clear purpose, retention, access, and withdrawal controls.

EVIDENCE

SOURCE QUALITY · UNCERTAINTY · NEUTRALITY

How to interpret AI kill-chain claims

OWNER-SUPPLIED RESEARCH INPUT — NOT SPECIALIST DISPOSITION

Evidence classes

Official Doctrine Or Policy

Primary institutional doctrine or policy; supports what the issuing body states, not deployment or compliance.

Official Technical Documentation

Primary technical specification or documentation; supports interface/status claims, not truth or field effectiveness.

Manufacturer Claim

First-party capability statement requiring independent corroboration.

Publicly Documented Deployment

Attributable public evidence of deployment scope; does not automatically establish autonomy, effectiveness, or legality.

Demonstration Or Exercise

Observed demo or exercise under bounded conditions; not field deployment.

Controlled Experiment

Structured test with stated conditions; external validity remains limited.

Peer Reviewed Research

Scholarly evidence with method and scope limitations.

Media Report

Journalistic account requiring attribution and corroboration assessment.

Owner Supplied Research Synthesis

Preserved source packet; claims remain unverified unless separately supported.

Editorial Inference

Repository-authored inference explicitly marked and linked to supporting evidence.

Hypothetical Simulation

Synthetic scenario for education; not operational evidence.

Unknown Not Retrieved

Evidence absent from the bounded search; absence is not proof of nonexistence.

REAL-WORLD INTERPRETIVE

Three meanings that must not be conflated

MeaningSubjectAnalysis model
AI_AS_TARGETAttacks against models, data, retrieval, context, tools, infrastructure, and users.Lifecycle defense: provenance, isolation, least privilege, retrieval authorization, tool-specific credentials, deterministic policy outside the model, egress controls, telemetry, rollback, and human approval.
AI_AS_CYBER_ENABLERAI accelerates conventional reconnaissance, social engineering, vulnerability analysis, or campaign execution.Defensive analysis must remain non-operational and must not provide executable payloads, credentials, real targets, or attack procedures.
AI_ENABLED_MILITARY_KILL_CHAINAI assists sensing, fusion, classification, prioritization, assignment, guidance, engagement support, or assessment.Use a function-context-control model; distinguish recommendation from authorization, navigation autonomy from target-selection autonomy, and classifier score from positive identification.
Uncertainty and control boundaries
  • Capability is not deployment.
  • Deployment is not autonomous use of force.
  • Autonomy in navigation is not autonomy in target selection.
  • A classifier score is not positive identification.
  • Recommendation is not authorization.
  • Human presence is not automatically meaningful human control.
  • Faster processing is not necessarily better judgment.
  • A manufacturer statement is not independent operational evidence.
  • A demonstration is not deployment.
  • Doctrine is not fielded capability.
  • A simulation is not operational evidence.
  • A test signature is not truth or endorsement.
  • A public allegation is not attribution.
  • An observed effect is not proof of the claimed cause.

Instructional boundary: Educational, defensive, governance-focused, synthetic, and non-operational. No executable payloads, credentials, malware, arbitrary target URLs, real target selection, or weapon-employment procedures.

LEVEL 4

RESEARCH EDITION

Sources, methods, and stable links

REAL-WORLD INTERPRETIVE

Linked reports

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.

NEXT

CONTINUE

Related learning

Page complete Safe 3D and VR Simulation of AI Kill Chains Page label: REAL-WORLD INTERPRETIVE