How to cite KillChains.com pages, evidence records, datasets, and simulations

Public page

Cite the page as a versioned web publication.

Recommended elements: named author, page title, publisher, release version, visible content-review date, canonical URL, and access date. Styles that prefer an organizational author may still cite KillChains.com as the publisher.

Michael Kappel. “What Is a Kill Chain? Definitions.” KillChains.com, release 1.38.0, reviewed 2026-08-07. https://killchains.com/what-they-are.php. Accessed 2026-09-16.

For styles that place the access date before the URL, retain the same information. Do not treat the release date as the date of an underlying government or manufacturer source.

Evidence Atlas

Cite both the Atlas view and the underlying source trail.

Michael Kappel. “Global Kill Chain Evidence Atlas.” KillChains.com, release 1.38.0, reviewed 2026-08-07. https://killchains.com/atlas.php. Accessed 2026-09-16.

A shared Atlas URL can preserve filters, selected entities, comparison choices, and timeline state. It is a view of the current release—not an immutable archival record. Record the release version and cite the visible source IDs or original sources supporting the claim.

Synthetic challenge

Identify the result as a fictional instructional artifact.

Michael Kappel. “Daily Break the Chain: [challenge title and code].” KillChains.com, synthetic interactive simulation, release 1.38.0, seed [seed if relevant]. https://killchains.com/?challenge=[id]&seed=[seed]. Accessed 2026-09-16.

State explicitly that timings, confidence values, evidence objects, actors, locations, and outcomes are synthetic. A replay demonstrates consequences inside a scripted causal model; it does not predict real system performance or establish a real-world fact.

Human Control replay

Cite the released module, HC1 code, and synthetic limitation.

Michael Kappel. “Human Control Lab: [module title].” KillChains.com, SYNTHETIC SCENARIO, release 1.38.0, replay code [HC1.__.____________.________]. https://killchains.com/human-control.php. Accessed 2026-09-16. Limitation: [copy the limitation shown with the replay].

The replay URL may reproduce only released module identifiers and allowlisted synthetic choices. Cite the clean canonical page, record the release and replay code, and retain the visible limitation. The code is not an identity, assessment certificate, server record, behavioral profile, or evidence about a real system.

Source Classification Evidence Lab

Cite the exercise separately from the public sources it teaches.

Michael Kappel. “Source Classification Evidence Lab.” KillChains.com, synthetic source-literacy exercise, release 1.38.0, challenge code [KC-EVIDENCE-__]. https://killchains.com/evidence-lab.php. Accessed 2026-09-16.

The exercise result records classifications, lineage inspections, and preserved unknowns inside a synthetic learning activity. It is not an evidentiary finding about a real system. For any real-world proposition shown on a card, cite the linked source record and original publisher separately.

KillWebs.com sister-site guide

Cite the KillChains guide and the relevant KillWebs.com page separately.

Michael Kappel. “KillWebs.com Sister Site: Kill Chains vs. Kill Webs.” KillChains.com, release 1.38.0, reviewed 2026-08-07. https://killchains.com/kill-webs/. Accessed 2026-09-16.

The KillChains.com page explains the relationship and preserves a reviewed source trail. When relying on a KillWebs.com definition, feature, methodology statement, or architecture explanation, also cite the exact first-party KillWebs.com page. Describe it as a first-party publication statement rather than independent verification of real-world capability.

Claim attribution

Carry the evidence state into the citation sentence.

Review the complete claim-state table.

Citing a claim-lineage record

Keep the claim ID, evidence state, source trail, and limitation together.

Michael Kappel. “[Claim title].” Claim Lineage & Institutional Authority Explorer, claim [claim-id], KillChains.com release 1.38.0, reviewed 2026-08-07. https://killchains.com/claim-lineage.php#[claim-id]. Accessed 2026-09-16.

A claim-lineage record documents how KillChains.com transformed and reused a bounded proposition. Cite the original source separately when the factual proposition matters. Do not describe the lineage record as a legal finding, independent fact-check certification, or evidence that a synthetic teaching value occurred in reality.

Citing an authority-casebook record

Cite the case, then cite the underlying sources separately.

Michael Kappel. “[Case title].” Institutional Authority Casebook, case [case-id], KillChains.com release 1.38.0, reviewed [case review date]. https://killchains.com/authority-casebook.php#casebook-[case-id]. Accessed 2026-09-16.

The casebook record documents KillChains.com’s bounded comparison of machine functions and institutional authority. Cite the original government, operator, manufacturer, or oversight source for the factual proposition. Do not cite the casebook as a legal finding, certification, performance rating, procurement recommendation, or proof of an undisclosed operating mode.

Citing a change-impact preview

Cite the subject, event, release, and non-mutating status.

Michael Kappel. “Change-impact preview: [subject title] — [event label].” KillChains.com release 1.38.0, reviewed 2026-08-07. https://killchains.com/change-impact.php?subject=[allowlisted-subject]&event=[event]. Accessed 2026-09-16.

A change-impact preview identifies records that would require review. It does not prove that the event occurred and does not change any source, claim, evidence state, route, or discovery artifact. Cite the original source, Source Review record, and accepted correction or supersession record separately when the underlying change matters.

Source-review record

Cite the original source first, then record the KillChains.com editorial state.

[Original publisher]. “[Source title].” [Source date and URL]. KillChains.com source-review record [source ID], release 1.38.0, reviewed 2026-08-07. https://killchains.com/source-review.php#review-[source-id]. Accessed 2026-09-16.

A source-review record documents when KillChains.com reviewed its bounded use of a source, which public records depend on it, and whether it is historical, superseded, disputed, or scheduled for later review. It does not replace the original source and must not be described as an independent fact-check certification.

Citing a concept route

Cite the concept, release, and the underlying owning record separately.

Michael Kappel. “[Concept title].” Cross-Lab Concept Matrix, concept [concept-id], KillChains.com release 1.38.0, reviewed 2026-08-07. https://killchains.com/concept-matrix.php#concept-[concept-id]. Accessed 2026-09-16.

The matrix explains where a concept appears across KillChains.com and where its multi-path or production-accountability continuation belongs. Cite the underlying glossary term, FAQ answer, Claim Lineage record, public source, KillWebs page, or Evulgare platform page separately when that evidence or product scope matters.

Citing the Machine Answerability Lab

Preserve the synthetic label and the legal-responsibility boundary.

Michael Kappel. “Machine Answerability & Accountability Handoff Lab.” KillChains.com release 1.38.0, reviewed 2026-08-07. https://killchains.com/accountability-handoff.php. Accessed 2026-09-16.

The fictional 86-millisecond sequence demonstrates why a final click does not prove meaningful control and which evidence a deployed system would need to preserve. Do not cite the scenario as a real incident, a product deployment, an independent evaluation of Evulgare, a legal conclusion, or proof that software can bear criminal or moral responsibility.

For Evulgare’s current product framing, cite the relevant official Evulgare page separately. For legal or factual propositions, cite the underlying primary authority rather than the lab.

Citing the Machine Answerability Replay

Cite the fixed event, evidence state, and remaining unknowns.

Michael Kappel. “Machine Answerability Replay and Causal Contribution Lab.” KillChains.com release 1.38.0, FICTIONAL SYNTHETIC EVENT, evidence state [1–4]. https://killchains.com/answerability-replay.php#machine-answerability-replay. Accessed 2026-09-16.

The event and ground truth remain fixed across all four states. Record which evidence state was inspected, retain the visible “records do not establish” and “further review required” language, and do not cite the causal-contribution map as a liability verdict or real incident analysis.

Citing the Machine Answerability Remediation Lab

Cite the fixed event, selected safeguards, and synthetic-effect boundary.

Michael Kappel. “Machine Answerability Remediation and Prevention Lab.” KillChains.com release 1.38.0, FICTIONAL COUNTERFACTUAL SAFEGUARD SET [IDs]. https://killchains.com/answerability-remediation.php. Accessed 2026-09-16.

Record the selected safeguard IDs and the visible bounded effect. Do not cite the result as proof that a real system would be prevented, contained, compliant, certified, or legally answerable.

Machine-readable discovery

Use indexes for discovery, then cite the human-readable record.

• content-index.json lists canonical routes, page summaries, topics, and direct questions.
• source-index.json mirrors the public source registry with source IDs and bounded support statements.
• feed.xml and feed.json expose current release discovery entries.
• llms.txt is a nonstandard convenience map, not a citation, access-control file, or ranking guarantee.

Machine-readable files are derived from repository-owned page and source registries. The canonical page and original public source remain the human-readable evidence path.

Quotation and reuse

Preserve context, attribution, and uncertainty.

Short quotations should identify KillChains.com and link to the canonical page. Do not crop away “synthetic scenario,” “manufacturer claim,” “unknown,” generation date, review date, or source-state labels from shared artifacts. External source material remains subject to the rights and terms of its original publisher.

For code and repository material, review LICENSE and THIRD_PARTY_NOTICES.md.