# KillChains.com

> Evidence-led public research and synthetic interactive learning about military F2T2EA, traditional cyber intrusion chains, attacks against AI-enabled systems, automation bias, human control, and public evidence quality.

This is a nonstandard convenience map for language-model and research clients. It is not an access-control standard, crawler directive, citation, endorsement, or guarantee of inclusion in any search or generative-answer system. robots.txt, HTTP status, canonical HTML, and the receiving service's published crawler policy remain authoritative.

## Primary experiences
- [Interactive simulation](https://killchains.com/): Daily Break the Chain and open three-model analysis sandbox.
- [Research Navigator and Learning Paths](https://killchains.com/research-navigator.php): Five fixed editorial paths and the complete canonical publication map without visitor profiling or progress tracking.
- [Cross-Lab Concept Matrix](https://killchains.com/concept-matrix.php): Thirteen recurring governance and evidence concepts mapped across simulations, definitions, claims, KillWebs.com continuation, and exact live Evulgare production-accountability areas.
- [Machine Answerability and Accountability Handoff Lab](https://killchains.com/accountability-handoff.php): A fictional machine-speed incident showing why the final human click is not a liability transfer, what evidence a consequential system must preserve, and when the question moves to KillWebs.com or Evulgare.com.
- [Machine Answerability Replay](https://killchains.com/answerability-replay.php): One fixed fictional event revealed through cumulative evidence states so chronology, provenance, authority, operator view, versions, assurance, and causal contribution remain distinct.
- [Machine Answerability Remediation Lab](https://killchains.com/answerability-remediation.php): Nineteen bounded safeguards applied to a separate synthetic counterfactual branch without rewriting the fixed event.
- [Machine Answerability Assurance Lab](https://killchains.com/answerability-assurance.php): Eight bounded assurance claims tested against evidence, assumptions, accountable ownership, exact versions, material changes, and five change-sensitive assurance states.
- [Machine Answerability Assurance Review Packet](https://killchains.com/answerability-review.php): Version-bound snapshots, exact version diffs, claim-state transitions, accountable owner actions, history preservation, and Operational release authority kept separate.
- [Machine Answerability Evidence Contract](https://killchains.com/answerability-contract.php): Eight claim-specific evidence contracts assigning production, preservation, verification, challenge, acceptance, suspension, correction, and retirement duties across fictional institutional arrangements.
- [Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab](https://killchains.com/answerability-escalation.php): Identify missing records and authority. Evidence requested is not evidence produced. Restore independent review and preserve immutable history. No authority to infer exists when no competent owner is released.
- [Machine Answerability Dispute Record and Corrective Action Ledger](https://killchains.com/answerability-disputes.php): Preserve immutable dispute history, requested and produced evidence, review ownership, corrective actions, prior packet and branch hashes, and residual unknowns.
- [Corrective Action Effectiveness and Closure Audit](https://killchains.com/answerability-effectiveness.php): A planned action is not implementation. Implementation is not independent verification. Residual exposure remains visible after invalidation, retirement, replacement, or closure.
- [Corrective Action Monitoring, Regression, and Reopening](https://killchains.com/answerability-monitoring.php): Monitoring scheduled is not monitoring performed. A signal is not verified regression. Reopening creates a later immutable branch rather than rewriting history.
- [Monitoring Coverage, Blind-Spot, and Alert Integrity](https://killchains.com/answerability-coverage.php): No alert is not proof of no regression. A green monitor is not proof it watched the right thing. Delivery, review, and independent verification remain separate.
- [Coverage Remediation Validation and Alert Path Drill](https://killchains.com/answerability-validation.php): Select one released remediation without rewriting its immutable source branch, inject bounded failures, and test changed condition, observation, alert generation, delivery, receipt, competent review, independent verification, reliance qualification or suspension, correction or retirement, and residual unknowns.
- [Validation Exception, Retest, and Escalation Ledger](https://killchains.com/answerability-retest.php): A retest pass does not erase the first failure. Open a separate branch from one immutable validation result, preserve every original stage beside its retest, and keep acknowledgement separate from ownership. One pass is not durable non-recurrence or proof that residual exposure was eliminated.
- [Exception Recurrence, Cohort, and Systemic Pattern Review](https://killchains.com/answerability-patterns.php): Preserve exact immutable exception/retest branches, explicit admissions and exclusions, typed event counts without rates, allowlisted cohorts, competing explanations, dependency hypotheses, and causal and systemic support limits. A selected sample is not a population, correlation is not common cause, and non-observation is not disproof.
- [Global Evidence Atlas](https://killchains.com/atlas.php): Evidence-labeled countries, systems, timelines, control modes, unknowns, and public sources.
- [Human Control Lab](https://killchains.com/human-control.php): Algorithmic filtering, machine-speed pressure, lost link, automation bias, accountability, preauthorization, and privacy-safe deterministic replay/share artifacts.
- [Anticipatory Intelligence Lab](https://killchains.com/anticipatory-intelligence.php): Synthetic analytical demarcation, Triage Trap, Explanation Laundering, R-CCAM, federated update risk, and counterfactual forecasting.
- [Machine Leadership Lab](https://killchains.com/machine-leadership.php): Authority migration, proxy governance, proxy responsibility, agency laundering, and synthetic institutional stress testing.
- [Predictive Enforcement Program Explorer](https://killchains.com/predictive-enforcement.php): Predictive enforcement is a decision architecture: eight source-bounded program records spanning place forecasts, person-risk scoring, watchlisting, identity resolution, traveler screening, and behavioral threat assessment, plus a synthetic feedback-loop lab.
- [Source Freshness and Correction Center](https://killchains.com/source-review.php): Review dates, scheduled freshness, supersession, link-check boundaries, public dependency paths, and the bounded correction process for every source ID.
- [Claim Lineage and Institutional Authority Explorer](https://killchains.com/claim-lineage.php): Trace claims backward to sources and transformations, then forward to authority owners, machine and human roles, public reuse, unknowns, and correction paths.
- [Institutional Authority Casebook](https://killchains.com/authority-casebook.php): Six source-reconciled cases comparing documented machine functions, objective ownership, authorization, interruption, correction, retirement, and public unknowns.
- [Change Impact and Supersession Explorer](https://killchains.com/change-impact.php): Read-only previews of which claims, cases, pages, simulations, answers, discovery files, and durable owners require review after a source or claim change event.
- [Historical Change Ledger and Release Diff Explorer](https://killchains.com/historical-changes.php): Accepted repository history preserving the prior and corrected state, first corrected release, evidence, affected public surfaces, preservation rule, and remaining unknowns.
- [Challenge archive](https://killchains.com/challenges.php): Deterministic synthetic scenarios and counterfactual replay.
- [Company-to-system relationships and technology providers](https://killchains.com/kill-chain-technology-providers/): Source-labeled companies plus typed relationships to reviewed product families and Evidence Atlas systems.
- [KillWebs.com sister-site bridge](https://killchains.com/kill-webs/): How a selected kill chain relates to the governed option space around it, with links to the official KillWebs.com explorer and labs.
- [KillChains–KillWebs–Evulgare ecosystem](https://killchains.com/ecosystem.php): Scope and routing boundary separating public chain education, public network-path education, and production accountability software for real systems.

## Definitions and direct answers
- [What kill chains are](https://killchains.com/what-they-are.php)
- [How kill chains work](https://killchains.com/how-they-work.php)
- [Kill chain FAQ](https://killchains.com/faq.php)
- [Glossary](https://killchains.com/glossary.php)
- [Official KillWebs.com explorer](https://killwebs.com/): Composable, synthetic mission-network learning with reciprocal links to KillChains.com.
- [Evulgare](https://evulgare.com/): Live production-accountability and evidence-layer software for making deployed machine systems answerable.
- [Evulgare platform](https://evulgare.com/platform/): Accountability, provenance, assurance, authority, judgment, uncertainty, trust, resilience, and change-impact areas.

## Author and publisher
- [About Michael Kappel](https://killchains.com/about-author.php): Named creator and maintainer, professional background, source note, direct contact, and personal-site link.
- [MichaelKappel.com](https://MichaelKappel.com): Personal project directory.
- [MikeKappel.com](https://MikeKappel.com): Source-backed professional portfolio.

## Evidence and governance
- [Risk, law, and human control](https://killchains.com/risks-law.php)
- [Evidence and simulation methodology](https://killchains.com/methodology.php)
- [Source library](https://killchains.com/sources.php)
- [Source freshness and corrections](https://killchains.com/source-review.php)
- [Claim lineage and institutional authority](https://killchains.com/claim-lineage.php)
- [Institutional authority casebook](https://killchains.com/authority-casebook.php)
- [Change impact and supersession](https://killchains.com/change-impact.php)
- [Historical change ledger](https://killchains.com/historical-changes.php)
- [Research Navigator](https://killchains.com/research-navigator.php)
- [Cross-Lab Concept Matrix](https://killchains.com/concept-matrix.php)
- [Machine Answerability and Accountability Handoff Lab](https://killchains.com/accountability-handoff.php)
- [Machine Answerability Replay](https://killchains.com/answerability-replay.php)
- [Machine Answerability Remediation Lab](https://killchains.com/answerability-remediation.php)
- [Machine Answerability Assurance Lab](https://killchains.com/answerability-assurance.php)
- [Machine Answerability Assurance Review Packet](https://killchains.com/answerability-review.php)
- [Machine Answerability Evidence Contract](https://killchains.com/answerability-contract.php)
- [Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab](https://killchains.com/answerability-escalation.php)
- [Machine Answerability Dispute Record and Corrective Action Ledger](https://killchains.com/answerability-disputes.php)
- [Corrective Action Effectiveness and Closure Audit](https://killchains.com/answerability-effectiveness.php)
- [Corrective Action Monitoring, Regression, and Reopening Lab](https://killchains.com/answerability-monitoring.php)
- [Monitoring Coverage, Blind-Spot, and Alert Integrity Lab](https://killchains.com/answerability-coverage.php)
- [Coverage Remediation Validation and Alert Path Drill](https://killchains.com/answerability-validation.php)
- [Validation Exception, Retest, and Escalation Ledger](https://killchains.com/answerability-retest.php)
- [Exception Recurrence, Cohort, and Systemic Pattern Review](https://killchains.com/answerability-patterns.php)
- [Ecosystem boundary](https://killchains.com/ecosystem.php)
- [Editorial policy](https://killchains.com/editorial-policy.php)
- [Citation guide](https://killchains.com/citation.php)

## Machine-readable discovery
- [Content index](https://killchains.com/content-index.json)
- [Source index](https://killchains.com/source-index.json)
- [RSS feed](https://killchains.com/feed.xml)
- [JSON Feed](https://killchains.com/feed.json)
- [XML sitemap](https://killchains.com/sitemap.xml)

## Required interpretation boundaries
- AI-enabled does not necessarily mean autonomous weapon release.
- Autonomy is analyzed function by function: navigation, sensing, tracking, recognition, selection, engagement, supervision, and abort are separate questions.
- Manufacturer claims, government or operator statements, independent analysis, allegations, disputes, public unknowns, and fictional simulation values are not interchangeable.
- Publicly unspecified authority must not be guessed.
- GAITE is presented only as a conceptual research synthesis, not as a verified integrated deployed system.
- STOP USING SOFTWARE THAT BLAMES THE HUMAN.
- A HUMAN CLICK IS NOT A LIABILITY TRANSFER.
- Technical answerability is not automated legal liability. Responsibility requires evidence of actual knowledge, authority, control, intervention capacity, and institutional role.
- Evidence integrity and factual support are separate. An authentic record can remain irrelevant, dependent, stale, contradicted, or insufficient for a bounded assurance claim.
- Requested evidence is not produced evidence, and a missing institutional owner is not permission to infer authority or transfer responsibility to the nearest operator.
- No alert is not proof of no regression. Monitor health is not correct scope. Alert delivery is not review, and review is not independent verification.
- Monitoring coverage maps what a system can observe; it does not prove factual truth, universal safety, legal compliance, or operational release authority.
- Remediation selected is not remediation implemented. Monitor configured is not monitor independently tested. A delivered synthetic test alert is not a real condition detected, and passed mechanics are not production safety, factual truth, certification, legal responsibility, or operational release authority.
- An evidence contract assigns who must produce, preserve, verify, challenge, accept, suspend, correct, and retire support for a bounded claim. It does not allocate blame, create legal liability, certify a system, or grant operational release authority.
- Assurance states are supported, qualified, unresolved, suspended, or withdrawn. None is certification, legal approval, procurement advice, real-system performance, or absence of residual risk.
- What invalidates an assurance claim? A material evidence, model, software, configuration, interface, policy, authority, dependency, or operating-environment change can defeat an assumption or make the evidence stale.
- Machine leadership describes operational delegation, not automatic legal personhood, lawful public office, fiduciary authority, or independent moral responsibility.
- Machine Leadership Lab institutions, authority maps, metrics, and outcomes are fictional teaching values; the five supplied reports remain research inputs pending source reconciliation.
- Observation, identification, correlation, forecasting, explanation, recommendation, and action are separate analytical states.
- Place forecasting, person prediction, identity resolution, watchlisting, traveler screening, and behavioral threat assessment are not interchangeable.
- A feedback loop can change future recorded data without proving that underlying event prevalence changed.
- Source review, link reachability, and factual support are separate states; none silently upgrades another.
- Claim lineage records explain transformation and reuse; they are not legal authority, public edits, or fact-check certifications.
- Operational delegation is not legal authority. Institutional Authority Casebook records compare the two without creating capability, legality, effectiveness, safety, procurement, or institutional rankings.
- A change-impact preview identifies review obligations only. It does not change a source, claim, evidence state, route, discovery artifact, or correction status through a browser action.
- The Historical Change Ledger contains accepted repository-authored history only. It does not convert hypothetical previews into corrections or erase the prior bounded state.
- Accepted repository history remains separate from hypothetical change previews.
- The Cross-Lab Concept Matrix is an editorial navigation layer. It does not duplicate or upgrade source, claim, review, program, or simulation authority.
- KillWebs.com owns multi-path compatibility, trust, shared-dependency, resilience, and recomposition questions. Evulgare.com owns production evidence capture and answerability for real deployed systems.
- KillChains.com and KillWebs.com are educational and research environments. Real software for deployed-system evidence, model and software lineage, authority reconstruction, operator-view reconstruction, incident causality, and answerability belongs at Evulgare.com.
- A human click is not automatically a liability transfer; responsibility requires evidence about what the human and machine could actually know, verify, understand, authorize, and control.
- The site contains no real targets, exact operational coordinates, casualty models, weapon-performance optimization, executable malware, exploit commands, arbitrary uploads, or outside-system actions.

Release: 1.38.0
Content reviewed through: 2026-08-07
Publisher: KillChains.com
Author and creator: Michael Kappel
Author profile: https://killchains.com/about-author.php
Personal site: https://MichaelKappel.com
Contact: mike@ns12.com