{ "schema_version": "1.0", "site": "KillChains.com", "canonical_origin": "https://killchains.com", "release": "1.38.0", "reviewed_through": "2026-08-07", "generated_from": [ "data/pages.php", "data/faq.php", "data/glossary.php", "data/author.php", "data/companies.php", "data/company-systems.php", "data/ecosystem.php", "data/sister-sites.php", "data/research-navigator.php", "data/concept-matrix.php", "data/accountability-handoff.php", "data/answerability-replay.php", "data/answerability-remediation.php", "data/answerability-assurance.php", "data/answerability-review.php", "data/answerability-contract.php", "data/answerability-escalation.php", "data/answerability-disputes.php", "data/answerability-effectiveness.php", "data/answerability-monitoring.php", "data/answerability-coverage.php", "data/answerability-validation.php", "data/answerability-retest.php", "data/answerability-patterns.php", "data/human-control-replays.php", "data/anticipatory-intelligence.php", "data/machine-leadership.php", "data/predictive-enforcement.php", "data/source-review.php", "data/claim-lineage.php", "data/authority-casebook.php", "data/change-impact.php", "data/historical-changes.php" ], "author": { "name": "Michael Kappel", "url": "https://MichaelKappel.com", "profile": "https://killchains.com/about-author.php" }, "disclaimer": "This discovery index is derived metadata. Canonical HTML pages and their cited public sources remain the publication authority.", "routes": [ { "url": "https://killchains.com/", "route": "/", "title": "Interactive Kill Chain Simulation | KillChains.com", "short_title": "Simulation", "description": "Explore a synthetic, server-authoritative simulation of military F2T2EA, cyber intrusions, AI-system attacks, human control, evidence, and counterfactual replay.", "page_type": "WebPage", "topics": [ "Kill chain", "F2T2EA", "Cyber Kill Chain", "AI security", "Human control", "WebXR" ], "questions_answered": [ { "question": "What is KillChains.com?", "answer": "KillChains.com is an evidence-led educational site with synthetic simulations for military F2T2EA, traditional cyber intrusion chains, and attacks against AI-enabled systems.", "supporting_path": "/what-they-are.php" }, { "question": "Does the simulation use real targets or execute attacks?", "answer": "No. The public simulation uses fictional scenarios, bounded commands, server-authoritative state, and no live targets, coordinates, payloads, or outside-system actions.", "supporting_path": "/methodology.php#safety-boundary" }, { "question": "What does the visitor do?", "answer": "Visitors inspect evidence, declare confidence, choose a defensive or governance control, observe the consequence, reveal ground truth, and compare a counterfactual path.", "supporting_path": "/challenges.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/challenges.php", "route": "/challenges.php", "title": "Daily Kill Chain Challenges | KillChains.com", "short_title": "Challenge Archive", "description": "Browse deterministic synthetic challenges for AI security, cyber defense, military governance, evidence evaluation, confidence calibration, and human control.", "page_type": "CollectionPage", "topics": [ "Daily challenge", "Cyber defense", "AI security", "Military governance", "Counterfactual replay" ], "questions_answered": [ { "question": "What is a Daily Break the Chain challenge?", "answer": "It is a short deterministic systems puzzle in which every visitor receives equivalent synthetic evidence and must choose a proportionate interruption control.", "supporting_path": "/#daily-challenge" }, { "question": "Are challenge results a measure of combat performance?", "answer": "No. Results assess evidence discipline, confidence calibration, timing, authority containment, functional preservation, and chain disruption inside a fictional scenario.", "supporting_path": "/methodology.php#simulation-method" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/research-navigator.php", "route": "/research-navigator.php", "title": "Research Navigator and Learning Paths | KillChains.com", "short_title": "Research Navigator", "description": "Choose a fixed learning path or browse the complete KillChains.com publication map across simulations, concepts, labs, evidence, governance, sources, and history.", "page_type": "CollectionPage", "topics": [ "Research navigation", "Learning paths", "Kill chain education", "Evidence literacy", "Human control", "Publication map" ], "questions_answered": [ { "question": "Where should a first-time KillChains.com reader begin?", "answer": "Begin with What They Are, continue through How They Work, complete the Daily Break the Chain simulation, inspect the Human Control Lab, and finish with Methodology.", "supporting_path": "/research-navigator.php#path-foundations" }, { "question": "Does the navigator personalize or track visitors?", "answer": "No. It provides fixed editorial paths and a complete route map without an account, progress profile, behavioral analytics, inferred expertise, or persistent browser state.", "supporting_path": "/research-navigator.php#navigator-boundary" }, { "question": "How does the ecosystem split affect the learning paths?", "answer": "KillChains.com remains the educational chain and evidence environment, KillWebs.com covers governed network paths, and Evulgare.com is the destination for production accountability software for real systems.", "supporting_path": "/ecosystem.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/concept-matrix.php", "route": "/concept-matrix.php", "title": "Cross-Lab Concept Matrix | KillChains.com", "short_title": "Concept Matrix", "description": "Compare thirteen recurring concepts across KillChains.com labs, evidence records, KillWebs, and live Evulgare accountability areas for real systems.", "page_type": "CollectionPage", "topics": [ "Concept matrix", "Evidence provenance", "Automation bias", "Human authorization", "Proxy responsibility", "Machine execution", "Evulgare" ], "questions_answered": [ { "question": "What is the Cross-Lab Concept Matrix?", "answer": "It is a read-only learning workspace that maps thirteen recurring concepts to the existing KillChains.com simulations, labs, evidence explorers, methods, history pages, and ecosystem handoffs where each concept can be studied.", "supporting_path": "/concept-matrix.php#concept-register" }, { "question": "Does the Concept Matrix create new factual claims or track learners?", "answer": "No. It references existing typed owners and creates no account, profile, completion record, analytics event, persistent state, public edit, or operational recommendation.", "supporting_path": "/concept-matrix.php#how-to-use-concept-matrix" }, { "question": "When does a concept move from KillChains.com to Evulgare?", "answer": "KillChains.com teaches the concept through public research and synthetic simulation. When a real deployed system needs evidence capture, model or software lineage, authority reconstruction, operator-view reconstruction, incident causality, or assurance, the handoff is to Evulgare.com.", "supporting_path": "/concept-matrix.php#evulgare-live-platform" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/accountability-handoff.php", "route": "/accountability-handoff.php", "title": "Machine Answerability & Accountability Handoff Lab | KillChains.com", "short_title": "Answerability Lab", "description": "Reconstruct a synthetic machine-speed failure, test whether human control was meaningful, and route production evidence requirements to Evulgare.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Human scapegoating", "Meaningful human judgment", "Decision provenance", "Authority reconstruction", "Evulgare" ], "questions_answered": [ { "question": "What does it mean to make a machine answerable?", "answer": "It means preserving enough evidence to reconstruct what the system knew, did not know, inferred, was authorized to do, showed to people, actually did, and caused.", "supporting_path": "/accountability-handoff.php#machine-evidence-contract" }, { "question": "Does machine answerability eliminate human or institutional responsibility?", "answer": "No. It prevents responsibility from being assigned merely because a person clicked a button. Legal and institutional responsibility still depends on actual authority, knowledge, control, design, deployment, and capacity to prevent or remedy harm.", "supporting_path": "/accountability-handoff.php#stop-blaming-the-human" }, { "question": "When should the question move from KillChains.com to Evulgare?", "answer": "Move to Evulgare when a real deployed system must preserve operational evidence, model and software versions, authority state, operator-visible information, incident causality, assurance, or change impact.", "supporting_path": "/accountability-handoff.php#evulgare-defensive-offensive-software" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-replay.php", "route": "/answerability-replay.php", "title": "Machine Answerability Replay Lab | KillChains.com", "short_title": "Answerability Replay", "description": "Replay a fictional machine-speed failure as provenance, authority, operator-view, software, and change evidence make its explanation more defensible.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Causal contribution", "Decision provenance", "Operator-view reconstruction", "Change impact", "Evulgare" ], "questions_answered": [ { "question": "What is the Machine Answerability Replay?", "answer": "It is a synthetic four-state replay showing how an ordinary chronological log becomes a more defensible explanation when provenance, model, authority, operator-view, software, configuration, assurance, and change-impact evidence are added.", "supporting_path": "/answerability-replay.php#machine-answerability-replay" }, { "question": "Does the replay assign blame or legal liability?", "answer": "No. It maps responsibility-relevant influence and persistent evidence deficiencies without deciding guilt, innocence, intent, liability, compensation, punishment, or blame percentages.", "supporting_path": "/answerability-replay.php#causal-contribution-map" }, { "question": "Does additional evidence change the fictional ground truth?", "answer": "No. The event and outcome remain fixed. Additional evidence changes only which causal questions can be answered and which explanations are defensible.", "supporting_path": "/answerability-replay.php#machine-answerability-replay" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-remediation.php", "route": "/answerability-remediation.php", "title": "Machine Answerability Remediation & Prevention Lab | KillChains.com", "short_title": "Answerability Remediation", "description": "Apply bounded safeguards to the fixed Orison replay and compare prevention, earlier detection, containment, recovery, answerability, unknowns, and ceremonial review.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Remediation", "Prevention", "Continuous assurance", "Safe state", "Authority boundaries", "Evulgare" ], "questions_answered": [ { "question": "What is the Machine Answerability Remediation Lab?", "answer": "It applies bounded safeguards to the fixed Orison replay and compares whether each control could prevent the demonstrated synthetic path, detect a defect earlier, contain consequences, preserve recovery, improve answerability, remain unknown, or merely create ceremonial review.", "supporting_path": "/answerability-remediation.php#remediation-workspace" }, { "question": "Does selecting a safeguard prove that it would prevent a real incident?", "answer": "No. Every effect is a synthetic counterfactual classification with explicit assumptions and non-establishment language. The lab is not certification, compliance testing, procurement advice, or a product-performance claim.", "supporting_path": "/answerability-remediation.php#safeguard-catalog" }, { "question": "Why is a post-action human click not a sufficient safeguard?", "answer": "A click recorded after irreversibility does not show that the person received the evidence, had enough time, possessed authority to reject, or could still stop the action.", "supporting_path": "/answerability-remediation.php#ceremonial-review-trap" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-assurance.php", "route": "/answerability-assurance.php", "title": "Machine Answerability Assurance Lab | KillChains.com", "short_title": "Answerability Assurance", "description": "Assemble a synthetic assurance case from a bounded claim, evidence, assumptions, defeaters, version identity, and accountable review ownership, then test material-change invalidation.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Assurance case", "Continuous assurance", "Evidence integrity", "Material change", "Defeaters", "Evulgare" ], "questions_answered": [ { "question": "What is a machine-answerability assurance case?", "answer": "It is a bounded, version-sensitive argument connecting one claim to supporting evidence, explicit assumptions, known defeaters, operating conditions, and a review owner who can qualify, suspend, or withdraw support.", "supporting_path": "/answerability-assurance.php#assurance-workspace" }, { "question": "Does a supported assurance state certify a real system?", "answer": "No. The state describes only this synthetic argument. It is not certification, accreditation, legal approval, compliance proof, procurement advice, operational effectiveness, or evidence that no residual risk remains.", "supporting_path": "/answerability-assurance.php#assurance-persistent-unknowns" }, { "question": "What invalidates an assurance claim?", "answer": "A material model, software, configuration, interface, policy, source, dependency, authority, or operating-environment change can defeat an assumption or make the supporting evidence no longer match the active state.", "supporting_path": "/answerability-assurance.php#assurance-invalidation-matrix" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-review.php", "route": "/answerability-review.php", "title": "Machine Answerability Assurance Review Packet | KillChains.com", "short_title": "Assurance Review Packet", "description": "Compare two synthetic version-bound assurance snapshots, preserve prior claim states, inspect exact evidence and version changes, and generate a bounded review packet.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Assurance review packet", "Version diff", "Evidence lineage", "Historical preservation", "Operational release authority", "Evulgare" ], "questions_answered": [ { "question": "What is an assurance review packet?", "answer": "It is a version-bound record connecting a bounded claim to the exact evidence, assumptions, defeaters, review owner, prior state, current state, missing evidence, required actions, and next review trigger.", "supporting_path": "/answerability-review.php#review-packet" }, { "question": "Does a completed review packet authorize operational release?", "answer": "No. Review completion, assurance support, evidence integrity, factual support, and operational release authority are separate states. This lab grants none of them for a real system.", "supporting_path": "/answerability-review.php#five-separate-questions" }, { "question": "Why preserve the prior snapshot after revalidation?", "answer": "A later reviewed version may support a new claim, but it cannot erase the earlier suspension, withdrawal, missing evidence, or operating state. Each snapshot remains independently reconstructable.", "supporting_path": "/answerability-review.php#snapshot-register" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-contract.php", "route": "/answerability-contract.php", "title": "Machine Answerability Evidence Contract Lab | KillChains.com", "short_title": "Evidence Contract Lab", "description": "Map who must produce, preserve, verify, challenge, accept, suspend, correct, and retire the evidence supporting a version-bound machine assurance claim.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Evidence contract", "Review ownership", "Many hands", "Independent challenge", "Suspension authority", "Evulgare" ], "questions_answered": [ { "question": "What is a machine-answerability evidence contract?", "answer": "It assigns bounded obligations to produce, preserve, verify, challenge, accept, suspend, correct, and retire the evidence supporting one version-bound assurance claim.", "supporting_path": "/answerability-contract.php#evidence-record-contract" }, { "question": "Why can a review be blocked even when many teams are involved?", "answer": "Many hands can still leave no independent challenger, no direct evidence access, no suspension authority, or no institution able to correct and retire an unsupported state.", "supporting_path": "/answerability-contract.php#ownership-comparison" }, { "question": "Does a complete evidence contract authorize a real system?", "answer": "No. Contract completeness, evidence integrity, factual support, assurance state, review completion, operational release authority, and legal responsibility remain separate questions.", "supporting_path": "/answerability-contract.php#evidence-contract-unknowns" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-escalation.php", "route": "/answerability-escalation.php", "title": "Evidence-Gap Remediation Lab | KillChains.com", "short_title": "Evidence-Gap Escalation", "description": "Identify missing evidence and authority, apply bounded synthetic remediation, and follow a non-destructive dispute path without rewriting history or inferring missing owners.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Evidence gaps", "Dispute escalation", "Independent review", "Suspension authority", "Correction ownership", "Evulgare" ], "questions_answered": [ { "question": "What is evidence-gap remediation?", "answer": "It is a bounded synthetic process that identifies a missing record or authority, assigns an allowed remediation step, and creates a new review branch without altering the immutable source packet or ownership arrangement.", "supporting_path": "/answerability-escalation.php#evidence-gap-workspace" }, { "question": "Why is requesting evidence different from producing it?", "answer": "A request establishes that a record was sought. It does not establish that the record exists, was supplied, is authentic, is complete, or supports the bounded claim.", "supporting_path": "/answerability-escalation.php#requested-versus-produced" }, { "question": "What does no authority to infer mean?", "answer": "When a required institutional owner is absent, the lab preserves the gap instead of assigning the duty to the nearest operator or treating an interface click as authorization.", "supporting_path": "/answerability-escalation.php#no-authority-to-infer" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-disputes.php", "route": "/answerability-disputes.php", "title": "Machine Answerability Dispute Ledger | KillChains.com", "short_title": "Dispute Ledger", "description": "Inspect immutable synthetic dispute records, evidence requests and production, independent review owners, corrective actions, preserved prior states, and residual unknowns.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Dispute record", "Corrective action ledger", "Evidence production", "Independent review", "Historical preservation", "Evulgare" ], "questions_answered": [ { "question": "What is a machine-answerability dispute record?", "answer": "It is an immutable synthetic record of a bounded challenge, requested and produced evidence, review ownership, corrective action, preserved prior state, current disposition, and residual unknowns.", "supporting_path": "/answerability-disputes.php#dispute-ledger-workspace" }, { "question": "Does closing a dispute prove that the system was safe or that a person was responsible?", "answer": "No. Closure records a bounded disposition and unresolved questions. It is not certification, operational release authority, a legal verdict, or a blame allocation.", "supporting_path": "/answerability-disputes.php#dispute-ledger-unknowns" }, { "question": "Why must a correction preserve the earlier packet?", "answer": "A corrective action should create a new state while retaining the earlier packet, statement, evidence basis, and reason for change so history cannot be rewritten after the outcome.", "supporting_path": "/answerability-disputes.php#preserved-prior-state" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-effectiveness.php", "route": "/answerability-effectiveness.php", "title": "Corrective Action Effectiveness & Closure Audit | KillChains.com", "short_title": "Effectiveness Audit", "description": "Audit whether a synthetic corrective action was merely planned, implemented, independently verified, effective, later invalidated, retired, or closed with residual exposure.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Corrective action effectiveness", "Implementation evidence", "Independent verification", "Continuous assurance", "Residual exposure", "Evulgare" ], "questions_answered": [ { "question": "What is a corrective-action effectiveness audit?", "answer": "It begins with an immutable dispute and one recorded corrective action, then separately examines implementation, implementation evidence, independent verification, bounded effect, later invalidation, and residual exposure.", "supporting_path": "/answerability-effectiveness.php#effectiveness-workspace" }, { "question": "Does a closed ticket prove that a corrective action worked?", "answer": "No. A plan, policy, training record, ticket closure, or human sign-off may document workflow without establishing that the control entered the system or addressed the identified gap.", "supporting_path": "/answerability-effectiveness.php#five-effectiveness-questions" }, { "question": "Does closing an effectiveness audit eliminate residual risk or authorize a real system?", "answer": "No. Closure records a bounded synthetic disposition. It does not eliminate residual exposure, grant operational release authority, certify compliance, or determine legal responsibility.", "supporting_path": "/answerability-effectiveness.php#effectiveness-residual-exposure" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-monitoring.php", "route": "/answerability-monitoring.php", "title": "Corrective Action Monitoring, Regression & Reopening | KillChains.com", "short_title": "Monitoring & Reopening", "description": "Monitor synthetic corrective-action audits, verify regression signals, preserve prior closures, reopen review, remediate, and independently revalidate changed states.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Corrective action monitoring", "Regression detection", "Audit reopening", "Independent revalidation", "Continuous assurance", "Evulgare" ], "questions_answered": [ { "question": "What is corrective-action monitoring?", "answer": "It checks whether a previously reviewed control still matches the evidence, versions, authority, interface, dependencies, and operating conditions that supported the earlier effectiveness conclusion.", "supporting_path": "/answerability-monitoring.php#monitoring-workspace" }, { "question": "Does a regression signal prove that a control failed?", "answer": "No. A signal triggers review. Independent verification is required before the site represents regression as established for the bounded synthetic state.", "supporting_path": "/answerability-monitoring.php#monitoring-separations" }, { "question": "Does reopening an audit erase its earlier closure or assign responsibility?", "answer": "No. Reopening creates a later immutable branch while preserving the earlier audit, closure, evidence, and hash. It does not determine guilt, liability, command responsibility, or operational release authority.", "supporting_path": "/answerability-monitoring.php#preserved-monitoring-history" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-coverage.php", "route": "/answerability-coverage.php", "title": "Monitoring Coverage, Blind Spots & Alert Integrity | KillChains.com", "short_title": "Coverage & Alert Integrity", "description": "Map what a synthetic monitoring architecture can observe, expose blind spots, separate monitor health from scope, and trace alerts through delivery, review, and independent verification.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Monitoring coverage", "Blind spots", "Alert integrity", "Monitor health", "Independent verification", "Evulgare" ], "questions_answered": [ { "question": "Does no monitoring alert mean no regression occurred?", "answer": "No. Silence may reflect stability, incomplete coverage, a disabled monitor, a stale baseline, a muted or deduplicated alert, inaccessible evidence, or a condition outside the monitored scope.", "supporting_path": "/answerability-coverage.php#coverage-separations" }, { "question": "What is the difference between monitor health and monitoring scope?", "answer": "Monitor health asks whether the configured check ran. Scope asks whether it observed the exact evidence, versions, authority, interface, dependencies, and operating conditions that could change the conclusion.", "supporting_path": "/answerability-coverage.php#coverage-dimensions" }, { "question": "Does alert delivery prove that regression was verified?", "answer": "No. Alert generation, delivery, acknowledgement, competent review, and independent verification are separate events with separate evidence and owners.", "supporting_path": "/answerability-coverage.php#coverage-alert-path" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-validation.php", "route": "/answerability-validation.php", "title": "Coverage Remediation Validation & Alert Path Drill | KillChains.com", "short_title": "Validation Drill", "description": "Apply a released monitoring-coverage remediation, inject bounded failures, and test alert generation, delivery, review, verification, suspension, correction, and residual unknowns.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Coverage remediation", "Alert path validation", "Failure injection", "Independent verification", "Institutional ownership", "Evulgare" ], "questions_answered": [ { "question": "Does selecting a monitoring remediation mean it was implemented?", "answer": "No. The drill preserves remediation selection and synthetic implementation as separate states. Neither state represents implementation in a real deployed system.", "supporting_path": "/answerability-validation.php#validation-separations" }, { "question": "Does a delivered synthetic alert prove competent review or independent verification?", "answer": "No. Alert generation, transport, receipt, competent review, independent verification, reliance qualification or suspension, and correction or retirement are separate stages with separate evidence and owners.", "supporting_path": "/answerability-validation.php#validation-alert-path" }, { "question": "Does a passed synthetic alert-path test prove production safety?", "answer": "No. A passed drill establishes only the mechanics of one bounded synthetic fixture. Factual truth, production safety, real implementation, legal responsibility, certification, procurement fitness, and operational release authority remain unsupported.", "supporting_path": "/answerability-validation.php#validation-no-authority" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-retest.php", "route": "/answerability-retest.php", "title": "Validation Exception, Retest & Escalation Ledger | KillChains.com", "short_title": "Exception & Retest Ledger", "description": "Open a synthetic exception branch from an immutable validation result, compare original and retest stages, and preserve recurrence, evidence, ownership, escalation, and residual unknowns.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Validation exception", "Same-fixture retest", "Recurrence classification", "Independent verification", "Institutional ownership", "Escalation", "Evulgare" ], "questions_answered": [ { "question": "Does acknowledging a validation exception mean an institution owns it?", "answer": "No. Acknowledgement records that an exception was seen. Ownership requires an identified institution responsible for evidence, corrective response, retest, escalation, and closure.", "supporting_path": "/answerability-retest.php#retest-separations" }, { "question": "Does one successful same-fixture retest prove durable non-recurrence?", "answer": "No. It establishes only that recurrence was not observed in one bounded synthetic run. The first result, residual exposure, alternate paths, future changes, and unsupported production-safety claims remain preserved.", "supporting_path": "/answerability-retest.php#retest-stage-diff" }, { "question": "Can a changed retest fixture be compared as though it were the original fixture?", "answer": "No. A materially changed fixture can produce a new result, but it cannot silently support the same recurrence comparison as the frozen source fixture.", "supporting_path": "/answerability-retest.php#retest-no-authority" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/answerability-patterns.php", "route": "/answerability-patterns.php", "title": "Exception Recurrence & Systemic Pattern Review | KillChains.com", "short_title": "Recurrence Pattern Review", "description": "Compare immutable exception and retest branches, count recurrence observations without rates, and inspect cohort patterns without implying population, causation, risk, or legal findings.", "page_type": "CollectionPage", "topics": [ "Machine answerability", "Recurrence review", "Cohort comparison", "Shared dependency hypothesis", "Causal support", "Systemic pattern support", "Independent verification", "Evulgare" ], "questions_answered": [ { "question": "Does a recurrence count create a recurrence rate?", "answer": "No. The review counts exact typed observations only. It creates no denominator, percentage, probability, weighting, trend score, population estimate, or operational-risk measure.", "supporting_path": "/answerability-patterns.php#pattern-event-counts" }, { "question": "Do same-stage or same-fixture branches prove a common cause?", "answer": "No. Comparability can support a bounded description, but shared labels, cohorts, and correlation do not establish event independence, shared mechanism, causal direction, production trace evidence, or common cause.", "supporting_path": "/answerability-patterns.php#pattern-dependencies" }, { "question": "Does no observed recurrence disprove recurrence?", "answer": "No. Non-observation is limited to exact admitted bounded runs. Missing, excluded, inaccessible, unfrozen, incomplete, or unverified observations remain unknown rather than zero.", "supporting_path": "/answerability-patterns.php#pattern-residual-unknowns" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/atlas.php", "route": "/atlas.php", "title": "Global Kill Chain Evidence Atlas | KillChains.com", "short_title": "Evidence Atlas", "description": "Explore evidence-labeled public records about countries, doctrine, systems, kill-chain functions, human-control arrangements, timelines, unknowns, and sources.", "page_type": "CollectionPage", "topics": [ "Evidence Atlas", "Military AI", "Human control", "Autonomous weapons", "Doctrine", "OSINT" ], "questions_answered": [ { "question": "What does the Evidence Atlas map?", "answer": "It connects countries and alliances to public doctrine, systems, kill-chain functions, control arrangements, lifecycle status, evidence states, timelines, governance, and source records.", "supporting_path": "/atlas.php#atlas-layers" }, { "question": "Does the Atlas show tactical locations?", "answer": "No. It uses country-level or abstract topological views and intentionally excludes active unit positions, exact operational coordinates, strike locations, and vulnerable infrastructure.", "supporting_path": "/methodology.php#atlas-method" }, { "question": "How are manufacturer claims handled?", "answer": "Manufacturer descriptions remain visibly attributed and are not displayed as equivalent to independently corroborated operational facts.", "supporting_path": "/atlas.php#evidence-states" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/human-control.php", "route": "/human-control.php", "title": "Human Control in Automated Kill Chains | KillChains.com", "short_title": "Human Control Lab", "description": "Explore six synthetic labs on algorithmic filtering, machine-speed pressure, lost links, automation bias, accountability, preauthorization, and private deterministic replay.", "page_type": "CollectionPage", "topics": [ "Human control", "Automation bias", "Preauthorization", "Lost link", "Accountability", "Algorithmic filtering" ], "questions_answered": [ { "question": "Are humans simply removed from automated kill chains?", "answer": "Often they are removed from particular micro-decisions or moved earlier into design, policy, mission configuration, activation, supervision, abort, and review rather than disappearing from the whole lifecycle.", "supporting_path": "/human-control.php#before-it-began" }, { "question": "What makes human control meaningful?", "answer": "Meaningful control depends on adequate time, information, understanding, authority to reject or delay, an effective intervention path, and reconstructable evidence—not merely a button press.", "supporting_path": "/human-control.php#rubber-stamp" }, { "question": "Why does upstream filtering matter?", "answer": "A human may formally authorize an action after algorithms have already discarded observations, fused sources, ranked candidates, and framed the available choices.", "supporting_path": "/human-control.php#gatekeeper" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/anticipatory-intelligence.php", "route": "/anticipatory-intelligence.php", "title": "Anticipatory Intelligence Lab | KillChains.com", "short_title": "Anticipatory Intelligence Lab", "description": "Compare observation, forecasting, person-risk inference, provenance, machine explanations, and human control in six synthetic anticipatory-intelligence labs.", "page_type": "CollectionPage", "topics": [ "Anticipatory intelligence", "Predictive policing", "Pre-crime", "Automation bias", "Explanation laundering", "Federated intelligence", "Counterfactual forecasting" ], "questions_answered": [ { "question": "What is anticipatory intelligence?", "answer": "Anticipatory intelligence estimates how observable physical, environmental, organizational, or systemic conditions may develop so people can test hypotheses and plan bounded responses before an event is fully realized.", "supporting_path": "/anticipatory-intelligence.php#orientation" }, { "question": "How is anticipatory intelligence different from pre-crime?", "answer": "The strongest distinction is the object and consequence: systemic or physical forecasting examines places, infrastructure, logistics, or events, while pre-crime architectures infer the future conduct of identifiable people and may attach coercive consequences.", "supporting_path": "/anticipatory-intelligence.php#orientation" }, { "question": "Is GAITE a verified deployed system?", "answer": "No. KillChains.com uses GAITE as an explicitly labeled conceptual research synthesis. The site has not established one integrated system with the proposed name, architecture, performance, or operational status.", "supporting_path": "/anticipatory-intelligence.php#gaite-concept" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/machine-leadership.php", "route": "/machine-leadership.php", "title": "Machine Leadership and Proxy Governance | KillChains.com", "short_title": "Machine Leadership Lab", "description": "Explore how AI moves from tool to analyst, orchestrator, operational delegate, and proxy leader while humans retain formal office, override duties, and liability.", "page_type": "CollectionPage", "topics": [ "Machine leadership", "Proxy governance", "Algorithmic executive", "Agentic AI", "Municipal AI", "Human accountability" ], "questions_answered": [ { "question": "What is machine leadership?", "answer": "Machine leadership occurs when software performs institutional leadership functions such as sensing, prioritizing, planning, coordinating, executing, or evaluating while people may retain the formal title and legal responsibility.", "supporting_path": "/machine-leadership.php#leadership-thesis" }, { "question": "Can AI legally lead a company or government?", "answer": "The supplied reports describe extensive operational delegation but generally frame legal office, fiduciary duty, public authority, and liability as remaining with human or institutional proxies. Named legal claims require jurisdiction-specific verification.", "supporting_path": "/machine-leadership.php#leadership-spectrum" }, { "question": "How can responsibility disappear when AI makes decisions?", "answer": "Responsibility can be laundered across policy, procurement, data, model design, integration, supervision, and oversight. A complete account must trace those upstream choices instead of stopping at the machine output.", "supporting_path": "/machine-leadership.php#proxy-responsibility" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/predictive-enforcement.php", "route": "/predictive-enforcement.php", "title": "Predictive Enforcement Program Explorer | KillChains.com", "short_title": "Predictive Enforcement", "description": "Compare eight source-bounded predictive-policing, watchlisting, traveler-screening, and behavioral-threat-assessment programs, then test a synthetic feedback loop.", "page_type": "CollectionPage", "topics": [ "Predictive policing", "Predictive enforcement", "Watchlisting", "Traveler screening", "Behavioral threat assessment", "Feedback loops", "Algorithmic accountability" ], "questions_answered": [ { "question": "What is predictive enforcement?", "answer": "Predictive enforcement is a decision architecture that connects historical or administrative data to identity resolution, inference or prioritization, human interpretation, state attention, retention, and review or redress.", "supporting_path": "/predictive-enforcement.php#orientation" }, { "question": "Are place forecasts, person scores, watchlists, and threat assessments the same?", "answer": "No. They ask different questions, use different evidence, affect different decisions, and create different error, rights, notice, and evaluation problems.", "supporting_path": "/predictive-enforcement.php#program-explorer" }, { "question": "Why do feedback loops matter?", "answer": "When a forecast or designation changes where officials look or whom they scrutinize, the resulting contacts and detections can become future data that appears to confirm the original priority.", "supporting_path": "/predictive-enforcement.php#feedback-loop" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/evidence-lab.php", "route": "/evidence-lab.php", "title": "Source Classification Evidence Lab | KillChains.com", "short_title": "Evidence Lab", "description": "Classify official, manufacturer, independent, disputed, unknown, and synthetic evidence while preserving source lineage, uncertainty, and bounded support.", "page_type": "WebPage", "topics": [ "Source classification", "Evidence quality", "Source lineage", "OSINT", "Public unknowns", "Media literacy" ], "questions_answered": [ { "question": "What is the Source Classification Evidence Lab?", "answer": "It is a local-only exercise that asks visitors to classify public claims by source type, inspect lineage, preserve unknowns, and identify what each record does not establish.", "supporting_path": "/evidence-lab.php#evidence-exercise" }, { "question": "Why is a manufacturer statement not independent verification?", "answer": "A manufacturer page establishes what the developer publicly says. Independent verification requires evidence outside the organization whose capability or performance is being described.", "supporting_path": "/evidence-lab.php#classification-key" }, { "question": "Why keep publicly unspecified details visible?", "answer": "Classified or undisclosed operating modes, authority arrangements, thresholds, and abort paths cannot responsibly be guessed in either direction.", "supporting_path": "/methodology.php#claim-states" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/what-they-are.php", "route": "/what-they-are.php", "title": "What Is a Kill Chain? Definitions | KillChains.com", "short_title": "What They Are", "description": "Understand military kill chains, the Cyber Kill Chain, AI-system attack chains, kill webs, AI-enabled functions, and the spectrum of human control.", "page_type": "WebPage", "topics": [ "Kill chain definition", "F2T2EA", "Cyber Kill Chain", "AI Kill Chain", "Kill web" ], "questions_answered": [ { "question": "What is a kill chain?", "answer": "A kill chain is a staged model that connects detection or access to a later objective and helps analysts identify points where the sequence can be interrupted.", "supporting_path": "/glossary.php#kill-chain" }, { "question": "What is F2T2EA?", "answer": "F2T2EA means Find, Fix, Track, Target, Engage, and Assess—the familiar military dynamic-targeting sequence used as one of the site’s three distinct models.", "supporting_path": "/how-they-work.php#military-chain" }, { "question": "Is an AI-enabled kill chain necessarily an autonomous weapon?", "answer": "No. AI may assist sensing, fusion, classification, prioritization, navigation, or assessment while a human retains authority over force.", "supporting_path": "/what-they-are.php#ai-enabled-not-autonomous" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/how-they-work.php", "route": "/how-they-work.php", "title": "How Kill Chains Work: Military, Cyber & AI | KillChains.com", "short_title": "How They Work", "description": "Follow F2T2EA, the Cyber Kill Chain, and attacks against AI systems stage by stage, including sensing, fusion, authority, feedback, uncertainty, and controls.", "page_type": "WebPage", "topics": [ "F2T2EA stages", "Cyber Kill Chain stages", "AI attack chain", "Sensor fusion", "Authority" ], "questions_answered": [ { "question": "How does a military kill chain work?", "answer": "Sensors produce observations; systems and people establish identity and location, maintain tracks, validate and prioritize a course of action, apply an authorized effect, and assess the result.", "supporting_path": "/how-they-work.php#military-chain" }, { "question": "How does the Cyber Kill Chain work?", "answer": "It organizes an intrusion from reconnaissance through weaponization, delivery, exploitation, installation, command and control, and actions on objectives.", "supporting_path": "/how-they-work.php#cyber-chain" }, { "question": "How do attacks against AI systems differ?", "answer": "They can manipulate data, context, models, memory, tools, and downstream actions without requiring a conventional malware foothold.", "supporting_path": "/how-they-work.php#ai-system-chain" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/countries.php", "route": "/countries.php", "title": "Countries Using AI Kill Chains | KillChains.com", "short_title": "Countries & Use", "description": "Review evidence-labeled country and alliance summaries of public military-AI programs, doctrine, systems, human-control arrangements, and unresolved unknowns.", "page_type": "CollectionPage", "topics": [ "Countries", "Military AI policy", "Autonomous weapons policy", "Public doctrine", "Evidence states" ], "questions_answered": [ { "question": "Which countries use AI-enabled kill chains?", "answer": "Public evidence shows many states using AI or automation in sensing, intelligence fusion, decision support, navigation, defensive interception, or terminal guidance, but the exact delegated authority often remains undisclosed.", "supporting_path": "/atlas.php#world-atlas" }, { "question": "Does possession prove autonomous combat use?", "answer": "No. A country can possess a system with an autonomous mode without publicly establishing that the mode is enabled or used in combat.", "supporting_path": "/methodology.php#country-analysis" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/systems.php", "route": "/systems.php", "title": "AI-Enabled Kill Chain Systems | KillChains.com", "short_title": "Systems", "description": "Compare ISR, command networks, terminal recognition, loitering munitions, local defense, autonomous mobility, swarms, and AI-security system categories.", "page_type": "CollectionPage", "topics": [ "Military systems", "ISR", "Air defense", "Loitering munitions", "Autonomous mobility", "Swarms" ], "questions_answered": [ { "question": "What systems can participate in an AI-enabled kill chain?", "answer": "Relevant systems include sensors, intelligence-fusion platforms, command networks, decision-support tools, autonomous vehicles, defensive interceptors, seekers, and assessment systems.", "supporting_path": "/systems.php" }, { "question": "What is the key analytical distinction?", "answer": "The key distinction is between autonomy of a function—such as navigation or recognition—and autonomy over the use of force.", "supporting_path": "/systems.php#autonomy-spectrum" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/kill-chain-technology-providers/", "route": "/kill-chain-technology-providers/", "title": "Kill Chain Technology Companies & Systems | KillChains.com", "short_title": "Technology Providers", "description": "Browse source-labeled kill-chain technology companies and trace reviewed relationships to sensing, command, autonomy, defense, communications, space, and cyber systems.", "page_type": "CollectionPage", "topics": [ "Technology providers", "Company-to-system relationships", "Defense technology", "Command and control", "Autonomy", "Defensive interception", "Cyber defense", "Evidence states" ], "questions_answered": [ { "question": "Which companies provide kill-chain technologies?", "answer": "The directory covers publicly documented providers of sensing, intelligence, command and control, decision support, defensive interception, autonomy, communications, space, and cyber-defense technologies.", "supporting_path": "/kill-chain-technology-providers/#provider-directory" }, { "question": "Does inclusion mean KillChains.com endorses a company or product?", "answer": "No. Inclusion is descriptive and source-based; the directory is not a ranking, buying guide, procurement recommendation, safety certification, or claim of independent performance verification.", "supporting_path": "/kill-chain-technology-providers/#directory-boundary" }, { "question": "Does every listed company provide autonomous weapons or military AI?", "answer": "No. Some provide sensors, communications, cybersecurity, or conventional automation. Each entry separates the documented function from the publicly known human-control arrangement.", "supporting_path": "/kill-chain-technology-providers/#directory-method-summary" }, { "question": "How are companies connected to specific systems or programs?", "answer": "The relationship explorer links each reviewed provider to a specific Atlas system or bounded product-family record, with source IDs, documented functions, lifecycle, human-control boundaries, unknowns, and a statement of what the relationship does not establish.", "supporting_path": "/kill-chain-technology-providers/#company-system-relationships" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/kill-webs/", "route": "/kill-webs/", "title": "KillWebs.com Sister Site: Kill Chains vs. Kill Webs", "short_title": "KillWebs.com", "description": "See how KillChains.com and KillWebs.com fit together, compare an ordered mission chain with a governed option space, and open the official KillWebs explorer and labs.", "page_type": "WebPage", "topics": [ "Kill web", "Kill chain versus kill web", "Mission networks", "Resilience", "Authority", "Sister sites" ], "questions_answered": [ { "question": "What is KillWebs.com?", "answer": "KillWebs.com is the sister learning site for governed, reconfigurable mission networks: the option space from which one or more technically valid, trusted, available, and authorized chains can be composed.", "supporting_path": "/kill-webs/#relationship" }, { "question": "Does a kill web replace the kill chain?", "answer": "No. The web is the changing option space; a chain is the selected, ordered path used to sense, decide, authorize, act, and assess for a particular mission.", "supporting_path": "/kill-webs/#chain-versus-web" }, { "question": "Is KillWebs.com an operational planning tool?", "answer": "No. Its nodes, scenarios, scores, latency bands, and outcomes are fictional teaching values for architecture, evidence, resilience, trust, and authority.", "supporting_path": "/kill-webs/#shared-boundary" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/ecosystem.php", "route": "/ecosystem.php", "title": "KillChains, KillWebs & Evulgare Ecosystem | KillChains.com", "short_title": "Ecosystem", "description": "Understand the split among KillChains.com education, KillWebs.com network and resilience research, and Evulgare.com production accountability software for real systems.", "page_type": "CollectionPage", "topics": [ "KillChains.com", "KillWebs.com", "Evulgare", "Machine accountability", "Evidence layer", "Human responsibility" ], "questions_answered": [ { "question": "What stays on KillChains.com?", "answer": "KillChains.com remains the public educational and research site for synthetic simulations, kill-chain anatomy, evidence, human control, anticipatory intelligence, predictive enforcement, and institutional authority.", "supporting_path": "/ecosystem.php#killchains-role" }, { "question": "When should a reader use KillWebs.com?", "answer": "Use KillWebs.com when the question concerns multiple governed mission paths, resilience, compatibility, trust, common dependencies, graceful degradation, or controlled recomposition.", "supporting_path": "/ecosystem.php#killwebs-role" }, { "question": "When should a reader go to Evulgare.com?", "answer": "Use Evulgare.com for real software serving real systems: evidence capture, model and software lineage, authority reconstruction, operator-information reconstruction, incident causality, auditability, and system answerability.", "supporting_path": "/ecosystem.php#evulgare-role" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/ai-security.php", "route": "/ai-security.php", "title": "AI Kill Chain Security & Defense | KillChains.com", "short_title": "AI Security", "description": "Learn how attackers reconnoiter, poison, hijack, persist in, and impact AI-enabled systems—and how provenance, least privilege, approval, monitoring, and rollback interrupt them.", "page_type": "WebPage", "topics": [ "AI Kill Chain", "Prompt injection", "Data poisoning", "Excessive agency", "AI security controls" ], "questions_answered": [ { "question": "What is an AI kill chain?", "answer": "It is a staged model of how an adversary gains knowledge or access, places malicious material, changes model-mediated behavior, persists influence, and causes an impact.", "supporting_path": "/glossary.php#ai-kill-chain" }, { "question": "What is the strongest defensive principle?", "answer": "Keep sensitive authorization outside the probabilistic model, minimize tool authority, verify provenance, monitor sequences, and make models, prompts, indexes, memory, and credentials rollbackable.", "supporting_path": "/ai-security.php#controls" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/risks-law.php", "route": "/risks-law.php", "title": "Autonomous Weapons Risk, Law & Human Control | KillChains.com", "short_title": "Risk, Law & Control", "description": "Examine international humanitarian law, weapons review, responsible-AI principles, meaningful human control, testing, accountability, escalation, and governance.", "page_type": "WebPage", "topics": [ "International humanitarian law", "Weapons review", "Meaningful human control", "AI governance", "Accountability" ], "questions_answered": [ { "question": "Is there one globally agreed human-control standard?", "answer": "No. Institutions use related but distinct terms such as appropriate human judgment, meaningful human control, context-appropriate human involvement, and human-in/on/out-of-the-loop.", "supporting_path": "/glossary.php#meaningful-human-control" }, { "question": "Does autonomy determine legality by itself?", "answer": "No. Legal assessment depends on the weapon, target, environment, predictability, mission constraints, human judgment, testing, and circumstances of use; the site does not issue case-specific legal rulings.", "supporting_path": "/risks-law.php#weapons-review" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/methodology.php", "route": "/methodology.php", "title": "Evidence & Simulation Methodology | KillChains.com", "short_title": "Methodology", "description": "See how KillChains.com separates facts, claims, analysis, disputes, unknowns, and synthetic scenarios while governing sources, corrections, safety, state, and testing.", "page_type": "AboutPage", "topics": [ "Research methodology", "Evidence states", "Source hierarchy", "Simulation method", "Corrections" ], "questions_answered": [ { "question": "How does KillChains.com classify claims?", "answer": "Important claims are labeled as verified fact, attributed official or manufacturer claim, independent analysis, public reporting, disputed or alleged, analyst inference, unknown, or synthetic scenario state.", "supporting_path": "/methodology.php#claim-states" }, { "question": "How are corrections handled?", "answer": "Corrections identify the exact claim, stronger evidence or methodological issue, affected pages, and whether the change is factual, interpretive, or a source-state update.", "supporting_path": "/methodology.php#corrections" }, { "question": "How can the site be cited?", "answer": "Use the page title, KillChains.com as publisher, visible release and review date, canonical URL, access date, and the evidence-state wording attached to the claim.", "supporting_path": "/citation.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/sources.php", "route": "/sources.php", "title": "Kill Chain Research Sources | KillChains.com", "short_title": "Source Library", "description": "Search the curated official policies, program records, standards, frameworks, manufacturer statements, legal positions, and independent research used by KillChains.com.", "page_type": "CollectionPage", "topics": [ "Sources", "Primary evidence", "Manufacturer claims", "Standards", "Research" ], "questions_answered": [ { "question": "What sources does KillChains.com prefer?", "answer": "The site prefers official law, policy, doctrine, standards, procurement and program records, then clearly attributed manufacturer material, independent research, and high-quality reporting.", "supporting_path": "/methodology.php#source-hierarchy" }, { "question": "What does a source link support?", "answer": "It supports the bounded statement described in the source record—not every claim on the destination page or every configuration and later version of a system.", "supporting_path": "/sources.php" }, { "question": "Where can I see review dates and dependent pages?", "answer": "The Source Freshness and Correction Center shows the current editorial review state, scheduled review date, typed public dependencies, supersession, and correction pathway for every source ID.", "supporting_path": "/source-review.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/source-review.php", "route": "/source-review.php", "title": "Source Freshness & Correction Center | KillChains.com", "short_title": "Source Review", "description": "Inspect review dates, source classes, dependencies, supersession, link-check boundaries, and correction pathways for every public KillChains.com source record.", "page_type": "CollectionPage", "topics": [ "Source freshness", "Corrections", "Evidence dependencies", "Supersession", "Editorial review", "Source provenance" ], "questions_answered": [ { "question": "What does a current source-review state mean?", "answer": "It means the KillChains.com registry record was reviewed for attribution, source class, date, bounded support, and current public use in this release. It is not a certification of the source or independent verification of every claim.", "supporting_path": "/source-review.php#how-to-read-this-page" }, { "question": "Does a reachable source prove that a claim is true?", "answer": "No. Link reachability and factual support are separate. A manufacturer page can be reachable while remaining an attributed claim, and an unavailable historical page can retain evidentiary value.", "supporting_path": "/source-review.php#review-summary" }, { "question": "How can a reader request a correction?", "answer": "Use the bounded email template to identify the affected public URL, source ID, exact disputed text, proposed correction, public supporting source, and issue category.", "supporting_path": "/source-review.php#request-a-correction" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/claim-lineage.php", "route": "/claim-lineage.php", "title": "Claim Lineage & Institutional Authority Explorer | KillChains.com", "short_title": "Claim Lineage", "description": "Trace public claims backward to source records and transformations, then forward to authority owners, machine and human roles, public reuse, review status, unknowns, and correction paths.", "page_type": "CollectionPage", "topics": [ "Claim lineage", "Institutional authority", "Evidence provenance", "Human control", "Machine leadership", "Contestability" ], "questions_answered": [ { "question": "What is claim lineage?", "answer": "Claim lineage is the trace from source observations and statements through inference, synthesis, prioritization, recommendation, authorization, action, reuse, and correction.", "supporting_path": "/claim-lineage.php#how-to-read-claim-lineage" }, { "question": "Does the explorer certify that a claim is true?", "answer": "No. It documents how KillChains.com supports, transforms, qualifies, and reuses a claim while preserving evidence class, unknowns, review status, and correction paths.", "supporting_path": "/claim-lineage.php#claim-lineage-boundaries" }, { "question": "Who owns an AI-mediated institutional decision?", "answer": "The answer depends on the specific function. The explorer separates source publisher, policy owner, system designer, machine processor, analyst, human authorizer, operator, reviewer, correction owner, and affected public.", "supporting_path": "/claim-lineage.php#lineage-console" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/authority-casebook.php", "route": "/authority-casebook.php", "title": "Institutional Authority Casebook | KillChains.com", "short_title": "Authority Casebook", "description": "Compare six source-reconciled cases showing which machine functions are documented, what authority migrated into software, and what legal or institutional authority remained human.", "page_type": "CollectionPage", "topics": [ "Institutional authority", "Operational delegation", "Machine leadership", "Human control", "Source reconciliation", "Proxy responsibility" ], "questions_answered": [ { "question": "What is the Institutional Authority Casebook?", "answer": "It is a source-reconciled comparison of real programs showing what software performs, which institution sets the objective, who can approve or interrupt action, and which decisive details remain public unknowns.", "supporting_path": "/authority-casebook.php#how-to-read-authority-casebook" }, { "question": "Does operational delegation give a machine legal authority?", "answer": "No. A machine may collect, classify, prioritize, recommend, or execute a bounded function while human institutions retain formal office, authorization, correction duties, and liability.", "supporting_path": "/authority-casebook.php#authority-comparison" }, { "question": "Does the casebook rank systems or institutions?", "answer": "No. It compares functions, lifecycle status, authority ownership, intervention paths, unknowns, and evidence boundaries without calculating capability, legality, effectiveness, procurement, or safety scores.", "supporting_path": "/authority-casebook.php#casebook-evidence-boundary" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/change-impact.php", "route": "/change-impact.php", "title": "Change Impact & Supersession Explorer | KillChains.com", "short_title": "Change Impact", "description": "Preview which claims, authority cases, pages, simulations, answers, discovery files, and durable owners require review when a source or claim changes.", "page_type": "CollectionPage", "topics": [ "Change impact", "Source supersession", "Corrections", "Claim lineage", "Evidence governance", "Dependency analysis" ], "questions_answered": [ { "question": "What does the Change Impact Explorer do?", "answer": "It begins with an existing source or claim and derives which direct claims, descendant claims, authority cases, public records, answers, simulations, discovery files, and durable owners require human review.", "supporting_path": "/change-impact.php#impact-console" }, { "question": "Does the preview change a source or claim?", "answer": "No. It is read-only and non-mutating. No browser action can edit a registry, accept a correction, crawl a source, regenerate an artifact, or certify a claim.", "supporting_path": "/change-impact.php#what-does-not-change" }, { "question": "Does an unavailable link make a claim false?", "answer": "No. Link reachability, source withdrawal, factual correction, evidence reclassification, and supersession are separate events with different review consequences.", "supporting_path": "/change-impact.php#orientation" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/historical-changes.php", "route": "/historical-changes.php", "title": "Historical Change Ledger & Release Diff Explorer | KillChains.com", "short_title": "Change Ledger", "description": "Review accepted KillChains.com corrections, withdrawals, supersessions, and evidence reclassifications with prior states, release proof, public impacts, and preserved history.", "page_type": "CollectionPage", "topics": [ "Historical change ledger", "Release diff", "Accepted corrections", "Source supersession", "Evidence reclassification", "Publication history" ], "questions_answered": [ { "question": "What is the Historical Change Ledger?", "answer": "It records accepted repository-authored corrections, withdrawals, supersessions, and evidence reclassifications while preserving the prior bounded statement, first corrected release, evidence, impact, and remaining unknowns.", "supporting_path": "/historical-changes.php#accepted-history" }, { "question": "Is the Change Ledger the same as the Change Impact Explorer?", "answer": "No. Change Impact previews hypothetical review obligations. The Change Ledger publishes only events already accepted, tested, versioned, and preserved by the repository.", "supporting_path": "/historical-changes.php#ledger-versus-preview" }, { "question": "Does an accepted correction erase the earlier statement?", "answer": "No. The earlier state remains visible for chronology and audit unless a separate privacy or legal obligation requires removal.", "supporting_path": "/historical-changes.php#change-register" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/faq.php", "route": "/faq.php", "title": "Kill Chain FAQ: Military, Cyber, AI & Autonomy | KillChains.com", "short_title": "FAQ", "description": "Get concise, evidence-linked answers about kill chains, F2T2EA, cyber and AI attack chains, autonomous weapons, human control, Iron Dome, privacy, and WebXR.", "page_type": "CollectionPage", "topics": [ "Kill chain FAQ", "F2T2EA", "Autonomous weapons", "Human control", "Iron Dome", "WebXR" ], "questions_answered": [ { "question": "What can this FAQ answer?", "answer": "It gives concise, source-linked answers to the most common definitional, technical, legal, evidence, privacy, and simulation questions raised by KillChains.com.", "supporting_path": "/faq.php" }, { "question": "Are the answers substitutes for legal or operational advice?", "answer": "No. They summarize public evidence for education and preserve uncertainty; they are not targeting guidance, legal advice, or a current operational assessment.", "supporting_path": "/editorial-policy.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/glossary.php", "route": "/glossary.php", "title": "Kill Chain Glossary: F2T2EA, AI & Autonomy | KillChains.com", "short_title": "Glossary", "description": "Search plain-language definitions for F2T2EA, cyber and AI kill chains, kill webs, control modes, automation bias, provenance, confidence, preauthorization, and replay.", "page_type": "DefinedTermSet", "topics": [ "Glossary", "Defined terms", "F2T2EA", "Human control", "AI security", "Evidence" ], "questions_answered": [ { "question": "Why does the glossary use site definitions?", "answer": "Terms such as autonomous, human-on-the-loop, and meaningful human control are not used identically by every institution, so each definition states the bounded meaning used on KillChains.com.", "supporting_path": "/glossary.php" }, { "question": "What is the most important distinction?", "answer": "Autonomy of a specific function—such as navigation, tracking, or recognition—is different from authority to select and engage a target.", "supporting_path": "/glossary.php#autonomy-of-a-function" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/editorial-policy.php", "route": "/editorial-policy.php", "title": "Editorial Policy, Evidence & Corrections | KillChains.com", "short_title": "Editorial Policy", "description": "Learn about Michael Kappel, the named creator of KillChains.com, and how the site handles evidence review, AI assistance, source labels, commercial independence, and corrections.", "page_type": "AboutPage", "topics": [ "Editorial policy", "Authorship", "AI-assisted drafting", "Corrections", "Evidence review" ], "questions_answered": [ { "question": "Who publishes and maintains KillChains.com?", "answer": "KillChains.com is the publication identity, and Michael Kappel is the named creator and maintainer. Public pages retain release, review, source, and correction information.", "supporting_path": "/editorial-policy.php#who" }, { "question": "How is AI used in publishing?", "answer": "AI may assist research synthesis, drafting, code generation, and testing, but publication claims must remain tied to reviewed sources, visible evidence states, deterministic data, and human acceptance of the release.", "supporting_path": "/editorial-policy.php#how" }, { "question": "Why does the site publish this material?", "answer": "The purpose is public understanding of how military, cyber, and AI-system chains work, where they can be interrupted, and how evidence, authority, and uncertainty should be evaluated.", "supporting_path": "/editorial-policy.php#why" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/citation.php", "route": "/citation.php", "title": "How to Cite KillChains.com Research & Simulations", "short_title": "Citation Guide", "description": "Use stable citation templates for KillChains.com pages, the Evidence Atlas, synthetic challenges, saved views, source states, release versions, review dates, and corrections.", "page_type": "AboutPage", "topics": [ "Citation guide", "Research citation", "Dataset citation", "Simulation citation", "Versioning" ], "questions_answered": [ { "question": "What should a KillChains.com citation include?", "answer": "Include the page title, KillChains.com as publisher, release or visible review date, canonical URL, access date, and the relevant evidence-state wording.", "supporting_path": "/citation.php#page-citation" }, { "question": "Can a saved Atlas URL be treated as immutable evidence?", "answer": "No. It reproduces a view of the current release; cite the release version, visible record, source trail, and access date as well as the URL.", "supporting_path": "/citation.php#atlas-citation" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/about-author.php", "route": "/about-author.php", "title": "About Michael Kappel, Creator of KillChains.com", "short_title": "About the Author", "description": "Meet Michael Kappel, creator of KillChains.com: a senior software engineer and architect focused on .NET, SQL Server, TypeScript, Angular, validation, and human-reviewed AI workflows.", "page_type": "AboutPage", "topics": [ "Michael Kappel", "Software architecture", "Enterprise modernization", "Human-reviewed AI engineering", "KillChains.com" ], "questions_answered": [ { "question": "Who created KillChains.com?", "answer": "Michael Kappel created and maintains KillChains.com as an evidence-led educational publication and interactive simulation.", "supporting_path": "/about-author.php#about-michael" }, { "question": "What is Michael Kappel’s professional background?", "answer": "He is a senior software engineer and software architect with more than 20 years of enterprise delivery experience, focused on .NET and SQL Server modernization, TypeScript and Angular interfaces, validation, and human-reviewed AI-assisted engineering.", "supporting_path": "/about-author.php#professional-focus" }, { "question": "How can Michael Kappel be contacted?", "answer": "Email Michael at mike@ns12.com or visit MichaelKappel.com. His source-backed professional profile is available at MikeKappel.com.", "supporting_path": "/about-author.php#contact-michael" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/privacy.php", "route": "/privacy.php", "title": "Privacy | KillChains.com", "short_title": "Privacy", "description": "Read how KillChains.com minimizes data: no accounts, advertising, analytics, raw XR telemetry, server-side learning profiles, uploads, or hidden sharing of local interactions.", "page_type": "WebPage", "topics": [ "Privacy", "Data minimization", "WebXR telemetry", "Local storage" ], "questions_answered": [ { "question": "Does KillChains.com require an account?", "answer": "No. The current public release has no account system, advertising, analytics provider, uploaded user content, or server-side persistent learning profile.", "supporting_path": "/privacy.php" }, { "question": "Does the site collect raw XR pose, gaze, hand, voice, or room data?", "answer": "No. Those sensor streams are not collected or transmitted by the public release.", "supporting_path": "/privacy.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." }, { "url": "https://killchains.com/terms.php", "route": "/terms.php", "title": "Terms of Use | KillChains.com", "short_title": "Terms", "description": "Review the educational-use, lawful-use, non-reliance, intellectual-property, external-link, and prohibited-operational-use terms for KillChains.com.", "page_type": "WebPage", "topics": [ "Terms of use", "Acceptable use", "Educational simulation", "Non-operational boundary" ], "questions_answered": [ { "question": "May the site be used as an operational decision aid?", "answer": "No. It is an educational simulation and public research resource, not a weapon system, targeting service, intelligence product, cyber range, or legal opinion.", "supporting_path": "/terms.php" }, { "question": "May users substitute real targets or systems into scenarios?", "answer": "No. Real targets, credentials, infrastructure, coordinates, payloads, and attack execution are outside the permitted use of the site.", "supporting_path": "/terms.php" } ], "reviewed_through": "2026-08-07", "release": "1.38.0", "evidence_boundary": "Public evidence, attributed claims, explicit unknowns, and synthetic simulation states are kept distinct." } ], "faq_count": 96, "glossary_term_count": 126, "technology_provider_count": 29, "technology_product_family_count": 35, "company_system_relationship_count": 41, "sister_site_count": 1, "ecosystem_site_count": 3, "research_navigator_group_count": 7, "research_navigator_path_count": 5, "research_navigator_step_count": 106, "concept_matrix_concept_count": 13, "concept_matrix_surface_count": 227, "concept_matrix_surface_type_count": 6, "accountability_handoff_evidence_count": 12, "accountability_handoff_class_count": 4, "accountability_handoff_contract_layer_count": 7, "accountability_handoff_report_input_count": 2, "answerability_replay_record_count": 13, "answerability_remediation_safeguard_count": 19, "answerability_assurance_claim_count": 8, "answerability_assurance_change_count": 11, "answerability_assurance_state_count": 5, "answerability_review_snapshot_count": 6, "answerability_review_version_dimension_count": 10, "answerability_review_completion_state_count": 4, "answerability_review_release_authority_state_count": 3, "answerability_contract_count": 8, "answerability_contract_action_count": 8, "answerability_contract_participant_role_count": 8, "answerability_contract_arrangement_count": 6, "answerability_contract_completion_state_count": 3, "answerability_contract_record_type_count": 27, "answerability_contract_challenge_path_count": 4, "answerability_escalation_gap_count": 9, "answerability_escalation_remediation_count": 10, "answerability_escalation_stage_count": 7, "answerability_escalation_disposition_count": 5, "answerability_dispute_count": 8, "answerability_dispute_state_count": 11, "answerability_dispute_corrective_action_count": 9, "answerability_effectiveness_audit_count": 12, "answerability_effectiveness_state_count": 9, "answerability_effectiveness_result_count": 7, "answerability_effectiveness_evidence_count": 12, "answerability_effectiveness_invalidation_count": 8, "answerability_effectiveness_residual_count": 10, "answerability_monitoring_branch_count": 18, "answerability_monitoring_state_count": 14, "answerability_monitoring_signal_count": 11, "answerability_monitoring_verification_state_count": 5, "answerability_monitoring_reopening_state_count": 8, "answerability_monitoring_evidence_count": 12, "answerability_coverage_branch_count": 18, "answerability_coverage_dimension_count": 9, "answerability_coverage_state_count": 6, "answerability_coverage_monitor_health_state_count": 5, "answerability_coverage_alert_integrity_state_count": 9, "answerability_coverage_silence_state_count": 7, "answerability_coverage_blind_spot_count": 11, "answerability_coverage_evidence_count": 12, "answerability_coverage_remediation_count": 10, "answerability_validation_preset_count": 3, "answerability_validation_result_count": 3, "answerability_validation_stage_count": 10, "answerability_validation_failure_injection_count": 10, "answerability_validation_eligible_branch_count": 15, "answerability_retest_preset_count": 3, "answerability_retest_result_count": 3, "answerability_retest_exception_class_count": 12, "answerability_retest_lifecycle_stage_count": 12, "answerability_retest_source_result_count": 3, "answerability_pattern_preset_count": 3, "answerability_pattern_result_count": 3, "answerability_pattern_source_branch_count": 3, "answerability_pattern_dimension_count": 13, "answerability_pattern_lifecycle_stage_count": 12, "evulgare_product_area_count": 9, "human_control_replay_type_count": 6, "anticipatory_module_count": 6, "anticipatory_classification_category_count": 10, "anticipatory_classification_case_count": 12, "machine_leadership_function_count": 8, "machine_leadership_spectrum_count": 9, "machine_leadership_institution_count": 4, "predictive_enforcement_program_count": 8, "predictive_enforcement_function_count": 8, "source_review_record_count": 129, "source_dependency_count": 1122, "source_correction_notice_count": 0, "claim_lineage_record_count": 22, "claim_lineage_type_count": 10, "claim_lineage_edge_count": 13, "institutional_authority_case_count": 6, "institutional_authority_domain_count": 6, "institutional_authority_machine_function_count": 12, "change_impact_subject_count": 151, "change_impact_event_type_count": 6, "change_impact_preset_count": 6, "historical_change_event_count": 6, "historical_change_release_count": 4, "historical_change_type_count": 4 }