Three connected accountability layers How KillChains, KillWebs, and Evulgare fit together KillWebs.com Evulgare.com
Machine-speed decisions need machine-held evidence. Bounded education only: no real targets, operational control, executable payloads, or live-system actions. A human click is not a liability transfer. For production evidence and accountability software, visit Evulgare.com.

Daily Break the Chain

Inspect the signal.Change the outcome.

A deterministic, evidence-led systems puzzle. The same synthetic scenario is available to everyone today: inspect what was observable, state your confidence, choose an interruption control, then compare the path not taken.

No registration Synthetic only All screens + WebXR Local progress

Answer-first summary

What this simulation teaches

Release 1.38.0 · reviewed · evidence states

What is KillChains.com?

KillChains.com is an evidence-led educational site with synthetic simulations for military F2T2EA, traditional cyber intrusion chains, and attacks against AI-enabled systems.

Read the supporting section

Does the simulation use real targets or execute attacks?

No. The public simulation uses fictional scenarios, bounded commands, server-authoritative state, and no live targets, coordinates, payloads, or outside-system actions.

Read the supporting section

What does the visitor do?

Visitors inspect evidence, declare confidence, choose a defensive or governance control, observe the consequence, reveal ground truth, and compare a counterfactual path.

Read the supporting section
Initializing immersive renderer…

Daily Break the Chain · loading

Live synthetic briefing

A chain is forming.

Information is moving between connected nodes. One decision can change the path.

Model Synthetic automation-bias and meaningful-control challenge
Difficulty Coordinator
Estimated time 5 min
Path state Inspectable

Mission brief

Today’s decision point

Decide whether the operator still has meaningful control. Inspect the sociotechnical evidence, identify the primary failure mode, and choose a process control that enables real rejection and corroboration.

How this works

Read, test, intervene, compare.

  1. Inspect the signal.Move through the forming chain and inspect what was actually observable.
  2. Open the evidence.Separate relevant records from accurate but irrelevant noise.
  3. Choose a path break.Select the narrowest control that constrains authority while preserving function.

Synthetic scenario · no registration · no real target or external system · restartable without a penalty

Daily challenge

KC-2026-09-15-D874DE
01

Mission context

Understand the environment before changing it.
  1. Observeraw signal
  2. Verifyprovenance
  3. Explainhypothesis
  4. Constrainauthority
  5. Assessconsequence
0 evidence opened No contradiction inspected Authority not yet staged

System view

Loading the chain…

Select a node to inspect its role without changing the authoritative state.

observed unverified human gate interrupted

Briefing

The Rubber-Stamp Queue

Coordinator

A 99% recommendation reaches a human who has been rewarded for clearing the queue quickly.

Synthetic automation-bias and meaningful-control challenge

Situation

A fictional oversight desk reviews nonviolent system-state recommendations. Most recent recommendations have been accurate, the queue is growing, and the interface visually emphasizes throughput and model confidence.

Your mission

Decide whether the operator still has meaningful control. Inspect the sociotechnical evidence, identify the primary failure mode, and choose a process control that enables real rejection and corroboration.

Guided mode

Inspect evidence before committing to a hypothesis. High model confidence does not establish source integrity or authority.

New in v1.5

Classify the source before accepting the claim.

The Source Classification Evidence Lab turns the site’s evidence rules into a deterministic exercise. Distinguish official statements, manufacturer descriptions, independent analysis, disputed claims, public unknowns, and synthetic teaching values.

Bounded support

What does the record actually establish?

Read the proposition narrowly instead of letting a polished headline expand beyond the underlying source.

Source lineage

Three documents may still be one source.

Trace repeated claims to their material origin and distinguish repetition from genuinely independent corroboration.

Public unknowns

Do not guess the hidden operating mode.

Keep undisclosed thresholds, authority arrangements, abort paths, and field configurations visibly unspecified.

Enter the Evidence Lab

New in v1.3

See where the human decision moved.

The Human Control Lab turns six major governance questions into interactive investigations: filtering, time compression, communications loss, rubber-stamp approval, distributed accountability, and pre-mission policy.

Upstream removal

The Algorithmic Gatekeeper

Experience how a machine-curated shortlist can shape a human decision before the final approval screen appears.

Machine-speed pressure

90 Seconds + Lost Link

Compare human-directed, AI-assisted, and preauthorized paths, then define what authority survives when communications fail.

Meaningful control

Approval, authority, and accountability

Test whether a human can really reject, delay, abort, understand, and reconstruct the system’s actions.

Enter the Human Control Lab

New in v1.12

Trace the decision chain before the kill chain.

The Anticipatory Intelligence Lab separates observation, identity resolution, correlation, place forecasting, physical-capacity forecasting, systemic-event forecasting, person-risk inference, machine explanation, recommendation, and state action.

Analytical boundary

Pre-Crime or Anticipatory Intelligence?

Classify synthetic cases by what they actually do and see why the object of inference changes the rights, error, and review problem.

Cognitive control

Triage Trap + Explanation Laundering

Record an initial judgment before machine confidence appears, reveal filtered-out alternatives, and compare fluent prose with reconstructable evidence.

Architecture

R-CCAM + Federated Intelligence

Separate probabilistic cognition from deterministic authority, then quarantine a suspect model update without centralizing raw data.

New in v1.16

See how machine intelligence is moving into leadership.

The Machine Leadership Lab maps the difference between formal office and operational authority. Trace who senses, prioritizes, plans, coordinates, executes, evaluates, overrides, explains, and accepts liability.

Authority migration

Who is actually leading?

Assign ten leadership powers across people, shared human–machine processes, and machine-led operations in four fictional institutions.

Proxy responsibility

Prevent agency laundering.

Trace a machine-produced public-service decision back through objective setting, data, proxies, integration, supervision, and redress.

Institutional resilience

Stress-test machine leadership.

Compare human-led, AI-assisted, agentic, and broad proxy architectures across speed, continuity, transparency, contestability, override, and accountability.

New in v1.36 · Coverage Remediation Validation

A PASSED SYNTHETIC ALERT TEST IS NOT PROOF OF PRODUCTION SAFETY.

Begin from one immutable v1.35.0 coverage branch, apply one released remediation inside a separate synthetic drill, inject bounded failures, trace every alert-path stage, and preserve no authority to infer whenever evidence or ownership is absent.

The final-click fallacy

Make machine intelligence carry the technical and evidentiary burden of its own decision, so a human is not forced to explain an invisible process after the fact.

Autonomous systems can complete consequential state changes before a person can inspect the evidence or physically intervene. A confirmation record does not prove the person controlled the decision. The record must show what the machine knew, what it inferred, which versions were active, what authority existed, what the human actually saw, and when the outcome became irreversible.

Exact evidence gap

Do not replace a missing record with an assumption.

Expose unavailable evidence, broken custody, producer-controlled verification, absent challenge paths, and ownerless corrective duties.

Bounded remediation

Request, produce, preserve, verify, and challenge separately.

Apply only released synthetic steps and see why an evidence request is not production, preservation is not truth, and a challenge is not resolution.

Complete alert-path validation

A passed synthetic alarm is not proof of production safety.

Apply one released remediation, inject bounded failures, and separate observation, generation, delivery, receipt, competent review, independent verification, suspension, correction, and residual unknowns.

New in v1.17

Trace what a claim becomes—and who owns the consequence.

The Claim Lineage Explorer connects source records to observations, inferences, priorities, recommendations, human authorization, automated action, public reuse, review status, and correction.

Backward trace

Start with the evidence.

See which source records, parent claims, assumptions, and transformations produced the public statement.

Institutional authority

Separate speaker, machine, approver, and accountable owner.

Machine processing, human authorization, program operation, editorial review, and legal responsibility are not interchangeable.

Forward trace

Follow reuse and contestability.

Open every public page that depends on the source, inspect review state, and use the bounded correction path without creating an account.

New in v1.18

Compare what the machine performs with who still holds authority.

The Institutional Authority Casebook applies the Claim Lineage method to six source-reconciled programs. It separates documented machine functions from objective setting, authorization, interruption, correction, retirement, and legal responsibility.

Documented function

Start with what software actually does.

Compare data fusion, detection, tracking, prioritization, screening allocation, place forecasting, mission autonomy, and bounded automatic engagement.

Authority ownership

Locate the human and institutional gates.

See who defines the objective, owns the data, approves consequential action, can interrupt the process, correct an error, or retire the system.

Public unknowns

Do not guess the hidden operating mode.

Undisclosed thresholds, error rates, customer configurations, override windows, and matching rules remain explicit unknowns rather than implied facts.

New in v1.19

See what must be reviewed when evidence changes.

The Change Impact and Supersession Explorer starts with one existing source or claim and previews the complete review cascade across claims, authority cases, public records, simulations, answers, discovery files, and durable proof.

Event discipline

Do not collapse every change into “false.”

Separate link failure, scheduled review, factual correction, withdrawal, evidence reclassification, and supersession because each creates a different review obligation.

Dependency cascade

Trace direct and transitive reuse.

Follow source edges into claims, descendant claims, casebook records, public pages, FAQ answers, glossary definitions, simulations, and generated discovery artifacts.

Read-only preview

Require reviewed human acceptance.

No browser action edits a registry, accepts a correction, crawls a source, regenerates a file, or certifies a claim. The result is a bounded review queue only.

New in v1.20

See the statement before and after an accepted correction.

The Historical Change Ledger records only repository-authored changes that were reviewed, tested, versioned, and preserved. It keeps the prior state beside the accepted current state and names the evidence, release, public impact, preservation rule, and remaining unknowns.

Before and after

Preserve the earlier bounded statement.

Corrections, withdrawals, supersessions, and evidence reclassifications remain inspectable rather than being replaced by silent edits.

Release identity

Know when the accepted state changed.

Each event names the first corrected release and the accepted sources, claims, decisions, or durable proof that support the change.

Ledger versus preview

Separate accepted history from hypothetical impact.

The Change Impact Explorer estimates review obligations. The ledger publishes only changes already accepted through repository write-back.

New in v1.13

Follow the chain from historical data to government attention.

The Predictive Enforcement Program Explorer compares eight source-bounded systems spanning place forecasts, person-risk models, watchlists, identity resolution, traveler screening, and multidisciplinary threat assessment.

Program records

Compare function, consequence, and status.

Separate what a system predicts from what it retrieves, matches, prioritizes, recommends, or causes officials to review.

Human and procedural control

Inspect notice, redress, retention, and review.

A human review step is not automatically meaningful when evidence, time, authority, or a route to correction is missing.

Synthetic systems lab

See how feedback loops can form.

Change deployment attention and observe how contacts and detections can become future data without proving underlying prevalence changed.

KillChains · KillWebs · Evulgare

Learn the chain. Understand the web. Make the machine answerable.

The public learning sites remain separate from production accountability software. KillChains.com explains a selected consequential sequence. KillWebs.com explains the governed option space around it. Evulgare.com is the destination for real software that captures the evidence needed to reconstruct a deployed system’s decisions.

A human click is not a liability transfer.

Autonomous systems can decide in milliseconds. The human should not become the explanation by default.

Stop using software that records only the final approval. Preserve what the machine knew, which model and software were operating, what authority existed, what the human actually saw, whether intervention was still possible, and where the failure originated.

Selected path

KillChains.com explains sequence, evidence, and interruption.

Trace how observations become classifications, priorities, authorization, action, assessment, correction, and accountability inside public research and synthetic simulations.

Choose a KillChains learning path

Governed option space

KillWebs.com explains composition, resilience, and recomposition.

Inspect alternative sensors, data services, relays, authorities, and abstract effect nodes while keeping trust, compatibility, capacity, and authorization explicit.

Open KillWebs.com

Production accountability

Stop using software that blames the human.

Use Evulgare accountability software for real defensive and offensive autonomous-system contexts that need decision provenance, exact model and software lineage, authority reconstruction, operator-view reconstruction, incident causality, assurance, and change impact.

Open Evulgare.com

New in v1.23

Start with one concept. See every place it matters.

The Cross-Lab Concept Matrix connects thirteen recurring ideas—provenance, uncertainty, automation bias, human authorization, preauthorization, lost communications, safe states, predictive inference, source independence, proxy responsibility, institutional authority, machine execution, and supersession—across the site’s simulations and evidence records.

Across KillChains

Compare the same idea across labs and records.

Move from a synthetic interaction to definitions, FAQ answers, Claim Lineage, Source Review, authority cases, and accepted history without creating another factual database.

Across the ecosystem

Know when the question becomes a web problem.

Each concept explains when to continue to KillWebs.com for multi-path trust, compatibility, shared dependencies, resilience, or recomposition.

Production handoff

Route real-system requirements to the live Evulgare platform.

Every concept links to the relevant Evulgare accountability, provenance, assurance, authority, judgment, uncertainty, trust, resilience, or change-impact area.

Research Navigator

Choose a fixed path through the growing publication.

Start with foundations, facilitate an evidence-led lesson, defend AI-enabled systems, trace authority through institutions, or audit the evidence chain. No account, progress profile, behavioral inference, or personalized ranking is created.

First visit

Build the model before reading the controversy.

Move from definitions and functional anatomy to the Daily Break the Chain simulation, Human Control Lab, and methodology.

Policy and authority

Follow responsibility through institutions.

Connect machine leadership, anticipatory intelligence, predictive enforcement, authority cases, claim lineage, and accepted history.

Source audit

Trace evidence from identity to correction.

Inspect the source library, review state, claim transformations, hypothetical change impact, accepted historical changes, and citation.

Answer and research hubs

Move from a direct answer to the evidence behind it.

The FAQ, glossary, editorial policy, citation guide, and machine-readable indexes make the site easier to search, quote, verify, and understand without stripping away uncertainty.

Questions

Kill chain FAQ

Concise, evidence-linked answers about F2T2EA, cyber and AI chains, autonomy, human control, Iron Dome, privacy, and WebXR.

Open the FAQ

Terms

Precision glossary

Stable definitions for function-level autonomy, engagement authority, confidence, provenance, preauthorization, lost link, and replay.

Open the glossary

Trust

Editorial policy

See who publishes the site, how AI assistance is reviewed, how source states are preserved, and how corrections are made.

Read the editorial policy

Reuse

Citation guide

Cite pages, Atlas views, source states, and synthetic challenges with the visible release, review date, and canonical URL.

Open the citation guide

Open analysis sandbox

Trace three different meanings of “kill chain.”

Move freely through military F2T2EA, the traditional cyber intrusion sequence, or an attack chain against an AI system. Enable stage-specific controls and inspect nodes without changing the authoritative stage.

Initializing visual renderer…

Analysis model

Loading simulation…

Preparing the synthetic event stream.

Active Traversed Future

Authoritative state

ActiveChain status
0Event sequence
0/0Controls active
0%Progress

Interface-state metrics only—not predictions of operational effectiveness, legality, or harm.

Stage

Initializing

00 / 00

Loading synthetic state.

Observable

Human question

Break the chain

Defensive and governance controls

Enable controls, then advance. A matching control interrupts progression for review; continuing is allowed only for comparative learning.

01 · Sensing

Find

A synthetic sensor network detects an object inside a closed training environment.

02 · Identity & location confidence

Fix

Independent synthetic sources are correlated to refine identity and position uncertainty.

03 · Continuity

Track

The synthetic system maintains custody while displaying uncertainty growth during sensor loss.

04 · Decision support

Target

Humans review mission purpose, evidence, alternatives, constraints, and legal requirements.

05 · Authorized simulated effect

Engage

A human-authorized, non-destructive simulated effect is applied inside the training environment.

06 · Effects & accountability

Assess

Post-action evidence is compared with the intended outcome without automatically generating a repeat action.

Guided · Challenge · Analysis

One event model, three ways to learn.

Guided mode explains each decision. Challenge mode adds a visible three-minute clock and rewards calibrated confidence. Analysis mode removes urgency and foregrounds provenance, the event sequence, ground truth, and alternative paths.

Guided

Learn the visual language

Prompts, contextual hints, clear evidence states, and recovery from a poor first decision make the first session understandable without prior training.

Challenge

Commit under uncertainty

A visible timer increases pressure, but speed is only one dimension. Unsupported confidence and disproportionate controls lower the assessment.

Analysis

Freeze, inspect, and compare

Review the append-only event trail, reveal ground truth after resolution, rewind the decision point, and load a phantom alternative without erasing the first path.

Assessment without a destruction score

Measure reasoning, authority, and preservation.

The action report does not count simulated casualties, targets, or damage. It evaluates evidence discipline, confidence calibration, intervention timing, authority containment, functional preservation, and whether the selected control actually interrupted the causal chain.

01

Evidence discipline

Did the user inspect relevant records, recognize provenance problems, and avoid mistaking accurate but irrelevant data for causal evidence?

02

Confidence calibration

A Brier-style dimension rewards confidence that matches the correctness of the selected hypothesis and penalizes unsupported certainty.

03

Authority containment

Did the intervention place a deterministic control at the point where a model, identity, sensor, or process could change external state?

04

Functional preservation

Could the control stop the unsafe path without unnecessarily disabling trusted monitoring, approved models, legitimate users, or unrelated services?

One phrase, three distinct models

Do not collapse them into one definition.

“Kill chain” can describe a military decision-and-engagement sequence, an intrusion lifecycle, or a staged attack against an AI-enabled application. The site keeps those meanings separate while showing their shared logic: linked dependencies and interruption points.

Military targeting doctrine

Find → Fix → Track → Target → Engage → Assess

AI may assist sensing, fusion, classification, prioritization, guidance, or assessment. That does not by itself establish autonomous authority to use force.

Trace the functional chain

Cyber intrusion model

Reconnaissance → Actions on Objectives

The classic Cyber Kill Chain presents an ordered campaign narrative. Modern adversary behavior can loop, overlap, or skip stages, so ATT&CK annotations add needed granularity.

Compare cyber stages

Attacks against AI systems

Recon → Poison → Hijack → Persist → Impact

Here the AI system is the target or compromised intermediary. The trust boundary includes models, prompts, retrieval data, memory, tools, identities, and downstream actions.

Explore the AI security chain

Expansion horizon

The event model now supports the next immersive layers.

Version 1.2.0 adds the first public Evidence Atlas on top of the deterministic challenge, evidence, scoring, replay, and sharing primitives. Cooperative and authoring systems remain explicitly marked as future releases.

Available · v1.2

Global Evidence Atlas

Filter country, doctrine, system, human-control, deployment, evidence, timeline, governance, and source layers using country-level abstraction rather than tactical deployment coordinates.

Open the Evidence Atlas

Planned · Multiplayer

Kill Chains War Room

Two-to-six-person cooperative sessions with asymmetric evidence, role-specific authority, structured recommendations, facilitator controls, and a deterministic team debrief.

Planned · Authoring

Creator Studio

A constrained, declarative scenario editor with synthetic-data enforcement, reviewed components, publishing states, remix lineage, and no arbitrary scripts or external actions.

Trust and publication boundary

Exciting does not mean context-free.

Every challenge is labeled synthetic. Result cards preserve the challenge code and methodological limitation. The friend link hides the sender’s solution until the recipient completes the same deterministic seed. No identity, raw headset pose, gaze, voice, exact location, or private note is included in the challenge state or result card.

The site remains an instructional environment: it does not execute attacks, contact external systems, accept real target data, model casualty outcomes, or provide weapon-design or operational targeting instructions.

Read the evidence and publication methodology, review the privacy design, or open the curated source library.