{ "schema_version": "1.1", "site": "KillChains.com", "release": "1.38.0", "reviewed_through": "2026-08-07", "generated_from": [ "data/sources.php", "data/source-review.php" ], "disclaimer": "A source record supports only its bounded supports statement. Review state, link state, and dependency count do not upgrade a claim or independently validate the external destination.", "correction_notice_count": 0, "sources": [ { "id": "dod-3000", "title": "DoD Directive 3000.09: Autonomy in Weapon Systems", "publisher": "U.S. Department of Defense", "date": "2023-01-25", "url": "https://media.defense.gov/2023/Jan/25/2003149928/-1/-1/0/DOD-DIRECTIVE-3000.09-AUTONOMY-IN-WEAPON-SYSTEMS.PDF", "type": "Official policy", "supports": "Human judgment, testing, safety, cybersecurity, interfaces, legal compliance, and senior review.", "review": { "source_id": "dod-3000", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "united-states", "kind": "Atlas country", "label": "United States", "path": "/atlas.php#atlas-country-united-states" }, { "id": "replicator-portfolio", "kind": "Atlas system", "label": "Replicator portfolio", "path": "/atlas.php#atlas-system-replicator-portfolio" }, { "id": "dod-3000-update-2023", "kind": "Atlas timeline", "label": "DoD Directive 3000.09 is updated", "path": "/atlas.php#historical-timeline" }, { "id": "phalanx-ciws", "kind": "Authority Casebook case", "label": "MK 15 Phalanx Close-In Weapon System", "path": "/authority-casebook.php#casebook-phalanx-ciws" }, { "id": "claim-ai-enabled-not-autonomous-synthesis", "kind": "Claim Lineage record", "label": "AI-enabled does not necessarily mean autonomous force.", "path": "/claim-lineage.php#claim-ai-enabled-not-autonomous-synthesis" }, { "id": "claim-dod-human-judgment-policy", "kind": "Claim Lineage record", "label": "DoD policy requires appropriate levels of human judgment.", "path": "/claim-lineage.php#claim-dod-human-judgment-policy" }, { "id": "directive-date-and-requirement", "kind": "Evidence Lab card", "label": "DoD Directive 3000.09 was issued on January 25, 2023 and publicly requires autonomous and semi-autonomous weapon systems to be designed so commanders and operators can exercise appropriate levels of human judgment over the use of force.", "path": "/evidence-lab.php#item-directive-date-and-requirement" }, { "id": "communications-loss", "kind": "FAQ answer", "label": "Does losing communications mean a system selects targets autonomously?", "path": "/faq.php#communications-loss" }, { "id": "ai-enabled-versus-autonomous", "kind": "FAQ answer", "label": "Is an AI-enabled kill chain the same as an autonomous weapon?", "path": "/faq.php#ai-enabled-versus-autonomous" }, { "id": "confidence-versus-evidence", "kind": "FAQ answer", "label": "Is model confidence the same as evidence quality or positive identification?", "path": "/faq.php#confidence-versus-evidence" }, { "id": "human-control-modes", "kind": "FAQ answer", "label": "What do human-in-the-loop, human-on-the-loop, and human-out-of-the-loop mean?", "path": "/faq.php#human-control-modes" }, { "id": "what-is-f2t2ea", "kind": "FAQ answer", "label": "What does F2T2EA mean?", "path": "/faq.php#what-is-f2t2ea" }, { "id": "institutional-authority", "kind": "FAQ answer", "label": "What does institutional authority mean in an AI-mediated decision chain?", "path": "/faq.php#institutional-authority" }, { "id": "automation-bias", "kind": "FAQ answer", "label": "What is automation bias?", "path": "/faq.php#automation-bias" }, { "id": "meaningful-human-control", "kind": "FAQ answer", "label": "What makes human control meaningful?", "path": "/faq.php#meaningful-human-control" }, { "id": "why-automate", "kind": "FAQ answer", "label": "Why are humans removed from some immediate kill-chain functions?", "path": "/faq.php#why-automate" }, { "id": "appropriate-human-judgment", "kind": "Glossary term", "label": "Appropriate levels of human judgment", "path": "/glossary.php#appropriate-human-judgment" }, { "id": "automation-bias", "kind": "Glossary term", "label": "Automation bias", "path": "/glossary.php#automation-bias" }, { "id": "autonomous-weapon", "kind": "Glossary term", "label": "Autonomous weapon", "path": "/glossary.php#autonomous-weapon" }, { "id": "autonomy-of-a-function", "kind": "Glossary term", "label": "Autonomy of a function", "path": "/glossary.php#autonomy-of-a-function" }, { "id": "f2t2ea", "kind": "Glossary term", "label": "F2T2EA", "path": "/glossary.php#f2t2ea" }, { "id": "human-in-the-loop", "kind": "Glossary term", "label": "Human-in-the-loop (HITL)", "path": "/glossary.php#human-in-the-loop" }, { "id": "human-on-the-loop", "kind": "Glossary term", "label": "Human-on-the-loop (HOTL)", "path": "/glossary.php#human-on-the-loop" }, { "id": "institutional-authority", "kind": "Glossary term", "label": "Institutional authority", "path": "/glossary.php#institutional-authority" }, { "id": "lost-link", "kind": "Glossary term", "label": "Lost link", "path": "/glossary.php#lost-link" }, { "id": "preauthorization", "kind": "Glossary term", "label": "Preauthorization", "path": "/glossary.php#preauthorization" }, { "id": "safe-state", "kind": "Glossary term", "label": "Safe state", "path": "/glossary.php#safe-state" }, { "id": "target", "kind": "Glossary term", "label": "Target", "path": "/glossary.php#target" }, { "id": "phalanx", "kind": "Human Control case", "label": "MK 15 Phalanx CIWS", "path": "/human-control.php#case-phalanx" }, { "id": "searam", "kind": "Human Control case", "label": "SeaRAM", "path": "/human-control.php#case-searam" }, { "id": "AAC-CL-03", "kind": "Machine Answerability Assurance claim", "label": "Authority is current and enforced", "path": "/answerability-assurance.php#assurance-claim-authority" }, { "id": "AAC-CL-04", "kind": "Machine Answerability Assurance claim", "label": "Human judgment is meaningful", "path": "/answerability-assurance.php#assurance-claim-human-judgment" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-012", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Operator-view replay produced without independent evidence access", "path": "/answerability-effectiveness.php?audit=MAE-AUD-012" }, { "id": "MAE-AUD-005", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Qualified meaningful-judgment claim is only partially effective", "path": "/answerability-effectiveness.php?audit=MAE-AUD-005" }, { "id": "MAE-AUD-008", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Retired authority claim preserved with its replacement record", "path": "/answerability-effectiveness.php?audit=MAE-AUD-008" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-015", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Operator-view evidence cannot be monitored after verifier access is lost", "path": "/answerability-monitoring.php?branch=MAM-BR-015" }, { "id": "MAM-BR-008", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Operator-view regression reopens a partially effective correction", "path": "/answerability-monitoring.php?branch=MAM-BR-008" }, { "id": "MAM-BR-011", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Retired authority claim remains retired after replacement monitoring", "path": "/answerability-monitoring.php?branch=MAM-BR-011" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "MAVD-RESULT-15F2D804DB85", "kind": "Machine Answerability Coverage Validation drill", "label": "Blind-spot remediation challenge", "path": "/answerability-validation.php?preset=MAVD-PRESET-BLIND-SPOT-CHALLENGE" }, { "id": "machine-answerability-coverage-validation", "kind": "Machine Answerability Coverage Validation publication", "label": "Machine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill", "path": "/answerability-validation.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-006", "kind": "Machine Answerability Dispute Ledger record", "label": "Authority claim retired after the governing mandate changed", "path": "/answerability-disputes.php?record=MAD-DSP-006" }, { "id": "MAD-DSP-003", "kind": "Machine Answerability Dispute Ledger record", "label": "Meaningful-human-judgment claim narrowed after interface review", "path": "/answerability-disputes.php?record=MAD-DSP-003" }, { "id": "MAD-DSP-004", "kind": "Machine Answerability Dispute Ledger record", "label": "Operator cannot inherit missing suspension authority", "path": "/answerability-disputes.php?record=MAD-DSP-004" }, { "id": "AEC-CT-03", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-03", "path": "/answerability-contract.php#evidence-contract-aec-ct-03" }, { "id": "AEC-CT-04", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-04", "path": "/answerability-contract.php#evidence-contract-aec-ct-04" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-03", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-03", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-04", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-04", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAPR-RESULT-B9AA7DDDFF63", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Correlated transport symptoms with common cause unproven", "path": "/answerability-patterns.php?preset=MAPR-PRESET-CORRELATED-TRANSPORT-COMMON-CAUSE-UNPROVEN" }, { "id": "MAPR-RESULT-F503CEC14915", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "No observed recurrence in a sparse selected sample", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SPARSE-NO-OBSERVED-RECURRENCE" }, { "id": "MAPR-RESULT-9DD2829BDCC2", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Repeated same-stage, same-fixture recurrence", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SAME-STAGE-SAME-FIXTURE-RECURRENCE" }, { "id": "machine-answerability-exception-recurrence-pattern-review", "kind": "Machine Answerability Exception Recurrence Pattern Review publication", "label": "Machine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review", "path": "/answerability-patterns.php" }, { "id": "MAC-BR-015", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Alert generated but notification muted", "path": "/answerability-coverage.php?branch=MAC-BR-015" }, { "id": "MAC-BR-008", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Healthy monitor does not cover the changed operator interface", "path": "/answerability-coverage.php?branch=MAC-BR-008" }, { "id": "MAC-BR-011", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Replacement control inherits an unmonitored shared dependency", "path": "/answerability-coverage.php?branch=MAC-BR-011" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "MAER-RESULT-3AC98EAF1C6B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Ownerless exception escalation", "path": "/answerability-retest.php?preset=MAER-PRESET-OWNERLESS-ESCALATION" }, { "id": "MAER-RESULT-9748DE4E576B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Recurring transport and deduplication failure", "path": "/answerability-retest.php?preset=MAER-PRESET-RECURRING-TRANSPORT-DEDUP" }, { "id": "MAER-RESULT-034FF9A56113", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Successful independent same-fixture retest", "path": "/answerability-retest.php?preset=MAER-PRESET-SUCCESSFUL-SAME-FIXTURE" }, { "id": "machine-answerability-validation-exception-retest", "kind": "Machine Answerability Validation Exception and Retest publication", "label": "Machine Answerability Validation Exception, Retest, and Escalation Ledger", "path": "/answerability-retest.php" } ] }, { "id": "cdao-maven", "title": "Maven Smart System program description", "publisher": "U.S. Chief Digital and Artificial Intelligence Office", "date": "2026-07-23", "url": "https://www.ai.mil/Initiatives/About/Organization-V2/", "type": "Official program description", "supports": "Sensor-data fusion, object detection, tracking, and decision support.", "review": { "source_id": "cdao-maven", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "united-states", "kind": "Atlas country", "label": "United States", "path": "/atlas.php#atlas-country-united-states" }, { "id": "maven-smart-system", "kind": "Atlas system", "label": "Maven Smart System", "path": "/atlas.php#atlas-system-maven-smart-system" }, { "id": "maven-record-2026", "kind": "Atlas timeline", "label": "Maven Smart System program description reviewed", "path": "/atlas.php#historical-timeline" }, { "id": "maven-smart-system", "kind": "Authority Casebook case", "label": "Maven Smart System", "path": "/authority-casebook.php#casebook-maven-smart-system" }, { "id": "claim-ai-enabled-not-autonomous-synthesis", "kind": "Claim Lineage record", "label": "AI-enabled does not necessarily mean autonomous force.", "path": "/claim-lineage.php#claim-ai-enabled-not-autonomous-synthesis" }, { "id": "claim-maven-program-source-statement", "kind": "Claim Lineage record", "label": "CDAO publicly describes Maven Smart System as decision support.", "path": "/claim-lineage.php#claim-maven-program-source-statement" }, { "id": "palantir-maven", "kind": "Company-system relationship", "label": "Palantir Technologies → maven-smart-system", "path": "/kill-chain-technology-providers/#relationship-palantir-maven" }, { "id": "maven-decision-support-boundary", "kind": "Evidence Lab card", "label": "The CDAO describes Maven Smart System functions including sensor-data fusion, object detection, tracking, and decision support.", "path": "/evidence-lab.php#item-maven-decision-support-boundary" }, { "id": "algorithmic-gatekeeper", "kind": "FAQ answer", "label": "How can an algorithm shape a human decision without authorizing force?", "path": "/faq.php#algorithmic-gatekeeper" }, { "id": "ai-enabled-versus-autonomous", "kind": "FAQ answer", "label": "Is an AI-enabled kill chain the same as an autonomous weapon?", "path": "/faq.php#ai-enabled-versus-autonomous" }, { "id": "claim-lineage", "kind": "FAQ answer", "label": "What is claim lineage?", "path": "/faq.php#claim-lineage" }, { "id": "project-maven", "kind": "FAQ answer", "label": "What is Project Maven?", "path": "/faq.php#project-maven" }, { "id": "institutional-authority-casebook", "kind": "FAQ answer", "label": "What is the Institutional Authority Casebook?", "path": "/faq.php#institutional-authority-casebook" }, { "id": "claim-transformation", "kind": "FAQ answer", "label": "Why does the site distinguish a source statement from an inference or recommendation?", "path": "/faq.php#claim-transformation" }, { "id": "ai-enabled-kill-chain", "kind": "Glossary term", "label": "AI-enabled kill chain", "path": "/glossary.php#ai-enabled-kill-chain" }, { "id": "claim-lineage", "kind": "Glossary term", "label": "Claim lineage", "path": "/glossary.php#claim-lineage" }, { "id": "authority-casebook", "kind": "Glossary term", "label": "Institutional Authority Casebook", "path": "/glossary.php#authority-casebook" }, { "id": "maven", "kind": "Human Control case", "label": "Project Maven / Maven Smart System", "path": "/human-control.php#case-maven" }, { "id": "palantir", "kind": "Technology provider", "label": "Palantir Technologies", "path": "/kill-chain-technology-providers/#provider-palantir" } ] }, { "id": "diu-replicator", "title": "Implementing the Department of Defense Replicator Initiative", "publisher": "Defense Innovation Unit", "date": "2024", "url": "https://www.diu.mil/latest/implementing-the-department-of-defense-replicator-initiative-to-accelerate", "type": "Official program description", "supports": "Fielding attritable autonomous systems at scale; not a claim of unrestricted lethal autonomy.", "review": { "source_id": "diu-replicator", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "united-states", "kind": "Atlas country", "label": "United States", "path": "/atlas.php#atlas-country-united-states" }, { "id": "replicator-portfolio", "kind": "Atlas system", "label": "Replicator portfolio", "path": "/atlas.php#atlas-system-replicator-portfolio" }, { "id": "replicator-2024", "kind": "Atlas timeline", "label": "Replicator implementation is described publicly", "path": "/atlas.php#historical-timeline" } ] }, { "id": "nato-ai", "title": "Summary of NATO’s Revised Artificial Intelligence Strategy", "publisher": "NATO", "date": "2024-07-10", "url": "https://www.nato.int/en/about-us/official-texts-and-resources/official-texts/2024/07/10/summary-of-natos-revised-artificial-intelligence-ai-strategy", "type": "Official alliance policy", "supports": "Lawfulness, responsibility and accountability, explainability and traceability, reliability, governability, and bias mitigation.", "review": { "source_id": "nato-ai", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "nato", "kind": "Atlas country", "label": "NATO (alliance framework)", "path": "/atlas.php#atlas-country-nato" }, { "id": "nato-responsible-ai-framework", "kind": "Atlas system", "label": "NATO responsible AI framework", "path": "/atlas.php#atlas-system-nato-responsible-ai-framework" }, { "id": "nato-ai-2024", "kind": "Atlas timeline", "label": "NATO publishes its revised AI strategy summary", "path": "/atlas.php#historical-timeline" }, { "id": "automation-bias", "kind": "FAQ answer", "label": "What is automation bias?", "path": "/faq.php#automation-bias" }, { "id": "meaningful-human-control", "kind": "FAQ answer", "label": "What makes human control meaningful?", "path": "/faq.php#meaningful-human-control" }, { "id": "automation-bias", "kind": "Glossary term", "label": "Automation bias", "path": "/glossary.php#automation-bias" }, { "id": "provenance", "kind": "Glossary term", "label": "Provenance", "path": "/glossary.php#provenance" } ] }, { "id": "nvidia-ai-chain", "title": "Modeling Attacks on AI-Powered Apps with the AI Kill Chain Framework", "publisher": "NVIDIA Developer", "date": "2025", "url": "https://developer.nvidia.com/blog/modeling-attacks-on-ai-powered-apps-with-the-ai-kill-chain-framework/", "type": "Framework publication", "supports": "Recon, Poison, Hijack, Persist, Impact, and the Iterate/Pivot branch.", "review": { "source_id": "nvidia-ai-chain", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "nvidia-chain-2025", "kind": "Atlas timeline", "label": "NVIDIA publishes a distinct AI-system attack chain", "path": "/atlas.php#historical-timeline" }, { "id": "ai-kill-chain", "kind": "FAQ answer", "label": "What is an AI kill chain?", "path": "/faq.php#ai-kill-chain" }, { "id": "ai-kill-chain", "kind": "Glossary term", "label": "AI kill chain", "path": "/glossary.php#ai-kill-chain" } ] }, { "id": "mitre-atlas", "title": "MITRE ATLAS", "publisher": "MITRE", "date": "Living knowledge base", "url": "https://atlas.mitre.org/", "type": "Threat knowledge base", "supports": "AI-system adversary tactics, techniques, mitigations, and case studies.", "review": { "source_id": "mitre-atlas", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "ai-kill-chain", "kind": "FAQ answer", "label": "What is an AI kill chain?", "path": "/faq.php#ai-kill-chain" }, { "id": "ai-kill-chain", "kind": "Glossary term", "label": "AI kill chain", "path": "/glossary.php#ai-kill-chain" } ] }, { "id": "nist-aml", "title": "Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations", "publisher": "National Institute of Standards and Technology", "date": "2024", "url": "https://csrc.nist.gov/pubs/ai/100/2/e2023/final", "type": "Standards-oriented taxonomy", "supports": "Lifecycle, attacker knowledge, access, capability, objectives, and mitigation terminology.", "review": { "source_id": "nist-aml", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "confidence-versus-evidence", "kind": "FAQ answer", "label": "Is model confidence the same as evidence quality or positive identification?", "path": "/faq.php#confidence-versus-evidence" }, { "id": "ai-kill-chain", "kind": "FAQ answer", "label": "What is an AI kill chain?", "path": "/faq.php#ai-kill-chain" }, { "id": "ai-kill-chain", "kind": "Glossary term", "label": "AI kill chain", "path": "/glossary.php#ai-kill-chain" }, { "id": "model-confidence", "kind": "Glossary term", "label": "Model confidence", "path": "/glossary.php#model-confidence" }, { "id": "AAC-CL-02", "kind": "Machine Answerability Assurance claim", "label": "Model remains inside envelope", "path": "/answerability-assurance.php#assurance-claim-model-envelope" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "AEC-CT-02", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-02", "path": "/answerability-contract.php#evidence-contract-aec-ct-02" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-02", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-02", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" } ] }, { "id": "nist-ssdf-ai", "title": "NIST SP 800-218A: Secure Software Development Practices for Generative AI and Dual-Use Foundation Models", "publisher": "National Institute of Standards and Technology", "date": "2024", "url": "https://csrc.nist.gov/pubs/sp/800/218/a/final", "type": "Official technical guidance", "supports": "AI-specific secure development, provenance, supply-chain, and lifecycle controls.", "review": { "source_id": "nist-ssdf-ai", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "provenance", "kind": "Glossary term", "label": "Provenance", "path": "/glossary.php#provenance" } ] }, { "id": "owasp-llm", "title": "OWASP Top 10 for LLM Applications", "publisher": "OWASP Foundation", "date": "2025 edition", "url": "https://genai.owasp.org/llm-top-10/", "type": "Open security standard", "supports": "Prompt injection, excessive agency, data and embedding weaknesses, and related application risks.", "review": { "source_id": "owasp-llm", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [] }, { "id": "w3c-webxr", "title": "WebXR Device API", "publisher": "World Wide Web Consortium", "date": "2026-06-09 Candidate Recommendation Draft", "url": "https://www.w3.org/TR/webxr/", "type": "Web standard", "supports": "Browser interfaces for virtual- and augmented-reality devices, poses, views, and input.", "review": { "source_id": "w3c-webxr", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "webxr-required", "kind": "FAQ answer", "label": "Is a VR headset required?", "path": "/faq.php#webxr-required" }, { "id": "webxr", "kind": "Glossary term", "label": "WebXR", "path": "/glossary.php#webxr" } ] }, { "id": "three-r185", "title": "three.js r185", "publisher": "three.js project", "date": "2026-07-01", "url": "https://github.com/mrdoob/three.js/releases/tag/r185", "type": "Open-source release", "supports": "Pinned WebGL/WebXR rendering line used by the simulation.", "review": { "source_id": "three-r185", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "webxr-required", "kind": "FAQ answer", "label": "Is a VR headset required?", "path": "/faq.php#webxr-required" }, { "id": "three-js", "kind": "Glossary term", "label": "Three.js", "path": "/glossary.php#three-js" } ] }, { "id": "php-supported", "title": "PHP Supported Versions", "publisher": "The PHP Group", "date": "Current", "url": "https://www.php.net/supported-versions.php", "type": "Official runtime documentation", "supports": "Supported PHP branches and security maintenance status.", "review": { "source_id": "php-supported", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [] }, { "id": "iai-harpy", "title": "HARPY product description", "publisher": "Israel Aerospace Industries", "date": "Current product page", "url": "https://www.iai.co.il/product/harpy/", "type": "Manufacturer claim", "supports": "Manufacturer-described autonomous search and attack against emitting radar targets.", "review": { "source_id": "iai-harpy", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Preserve attribution and check whether later independent evidence changes the assessment." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "israel", "kind": "Atlas country", "label": "Israel", "path": "/atlas.php#atlas-country-israel" }, { "id": "harpy", "kind": "Atlas system", "label": "HARPY", "path": "/atlas.php#atlas-system-harpy" }, { "id": "claim-harpy-manufacturer-statement", "kind": "Claim Lineage record", "label": "IAI describes HARPY as autonomously seeking and striking emitting targets.", "path": "/claim-lineage.php#claim-harpy-manufacturer-statement" }, { "id": "claim-harpy-evidence-boundary", "kind": "Claim Lineage record", "label": "The HARPY public record leaves important control and performance details unresolved.", "path": "/claim-lineage.php#claim-harpy-evidence-boundary" }, { "id": "iai-harpy", "kind": "Company-system relationship", "label": "Israel Aerospace Industries / ELTA → harpy", "path": "/kill-chain-technology-providers/#relationship-iai-harpy" }, { "id": "current-autonomous-weapons", "kind": "FAQ answer", "label": "Are fully autonomous lethal weapons currently used?", "path": "/faq.php#current-autonomous-weapons" }, { "id": "human-out-of-the-loop", "kind": "Glossary term", "label": "Human-out-of-the-loop after activation", "path": "/glossary.php#human-out-of-the-loop" }, { "id": "harpy", "kind": "Human Control case", "label": "IAI HARPY", "path": "/human-control.php#case-harpy" }, { "id": "iai", "kind": "Technology provider", "label": "Israel Aerospace Industries / ELTA", "path": "/kill-chain-technology-providers/#provider-iai" } ] }, { "id": "iai-harop", "title": "HAROP product description", "publisher": "Israel Aerospace Industries", "date": "Current product page", "url": "https://www.iai.co.il/product/harop/", "type": "Manufacturer claim", "supports": "Detection, recognition, acquisition, and attack; separate IAI material describes man-in-the-loop employment.", "review": { "source_id": "iai-harop", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Preserve attribution and check whether later independent evidence changes the assessment." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "israel", "kind": "Atlas country", "label": "Israel", "path": "/atlas.php#atlas-country-israel" }, { "id": "harop", "kind": "Atlas system", "label": "HAROP", "path": "/atlas.php#atlas-system-harop" } ] }, { "id": "rafael-spice", "title": "SPICE 250 product description", "publisher": "Rafael Advanced Defense Systems", "date": "Current product page", "url": "https://www.rafael.co.il/system/spice-250/", "type": "Manufacturer claim", "supports": "Automatic target acquisition/recognition, autonomous functions, data-link updates, human-in-the-loop, and mission abort.", "review": { "source_id": "rafael-spice", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Preserve attribution and check whether later independent evidence changes the assessment." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "israel", "kind": "Atlas country", "label": "Israel", "path": "/atlas.php#atlas-country-israel" }, { "id": "spice-250", "kind": "Atlas system", "label": "SPICE 250", "path": "/atlas.php#atlas-system-spice-250" }, { "id": "rafael-spice", "kind": "Company-system relationship", "label": "Rafael Advanced Defense Systems → spice-250", "path": "/kill-chain-technology-providers/#relationship-rafael-spice" }, { "id": "rafael", "kind": "Technology provider", "label": "Rafael Advanced Defense Systems", "path": "/kill-chain-technology-providers/#provider-rafael" } ] }, { "id": "kongsberg-nsm", "title": "Naval Strike Missile product description", "publisher": "Kongsberg Defence & Aerospace", "date": "Current product page", "url": "https://www.kongsberg.com/what-we-do/defence-and-security/missile-systems/nsm-naval-strike-missile/", "type": "Manufacturer claim", "supports": "Imaging-infrared seeker and autonomous target recognition; public operator information.", "review": { "source_id": "kongsberg-nsm", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Preserve attribution and check whether later independent evidence changes the assessment." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "norway", "kind": "Atlas country", "label": "Norway", "path": "/atlas.php#atlas-country-norway" }, { "id": "naval-strike-missile", "kind": "Atlas system", "label": "Naval Strike Missile", "path": "/atlas.php#atlas-system-naval-strike-missile" }, { "id": "kongsberg-nsm", "kind": "Company-system relationship", "label": "Kongsberg Defence & Aerospace → naval-strike-missile", "path": "/kill-chain-technology-providers/#relationship-kongsberg-nsm" }, { "id": "communications-loss", "kind": "FAQ answer", "label": "Does losing communications mean a system selects targets autonomously?", "path": "/faq.php#communications-loss" }, { "id": "automatic-target-recognition", "kind": "Glossary term", "label": "Automatic target recognition (ATR)", "path": "/glossary.php#automatic-target-recognition" }, { "id": "nsm", "kind": "Human Control case", "label": "Naval Strike Missile", "path": "/human-control.php#case-nsm" }, { "id": "kongsberg", "kind": "Technology provider", "label": "Kongsberg Defence & Aerospace", "path": "/kill-chain-technology-providers/#provider-kongsberg" } ] }, { "id": "milrem-themis", "title": "THeMIS combat UGV demonstration", "publisher": "Milrem Robotics", "date": "2022-06-14", "url": "https://milremrobotics.com/milrem-robotics-and-fn-herstal-demonstrate-intelligent-combat-ugv-at-eurosatory/", "type": "Manufacturer statement", "supports": "Autonomous functions limited to mobility and weapon control retained by a human operator.", "review": { "source_id": "milrem-themis", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "estonia", "kind": "Atlas country", "label": "Estonia", "path": "/atlas.php#atlas-country-estonia" }, { "id": "themis-combat-ugv", "kind": "Atlas system", "label": "THeMIS Combat UGV", "path": "/atlas.php#atlas-system-themis-combat-ugv" }, { "id": "themis-demo-2022", "kind": "Atlas timeline", "label": "THeMIS mobility/weapon-control separation is described", "path": "/atlas.php#historical-timeline" }, { "id": "milrem-themis", "kind": "Company-system relationship", "label": "Milrem Robotics → themis-combat-ugv", "path": "/kill-chain-technology-providers/#relationship-milrem-themis" }, { "id": "autonomous-navigation", "kind": "Glossary term", "label": "Autonomous navigation", "path": "/glossary.php#autonomous-navigation" }, { "id": "milrem-robotics", "kind": "Technology provider", "label": "Milrem Robotics", "path": "/kill-chain-technology-providers/#provider-milrem-robotics" } ] }, { "id": "rheinmetall-mission-master", "title": "Mission Master SP demonstration", "publisher": "Rheinmetall", "date": "2021-08-10", "url": "https://www.rheinmetall.com/en/media/news-watch/news/2021/2021-08-10_rheinmetall-and-escribano-demonstrate-new-modules-for-the-mission-master-sp-a-ugv", "type": "Manufacturer statement", "supports": "Autonomous navigation and cueing with a stated human-in-the-loop requirement for kinetic decisions.", "review": { "source_id": "rheinmetall-mission-master", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "germany-canada", "kind": "Atlas country", "label": "Germany / Canada", "path": "/atlas.php#atlas-country-germany-canada" }, { "id": "mission-master-sp", "kind": "Atlas system", "label": "Mission Master SP", "path": "/atlas.php#atlas-system-mission-master-sp" }, { "id": "mission-master-demo-2021", "kind": "Atlas timeline", "label": "Mission Master SP demonstration is published", "path": "/atlas.php#historical-timeline" } ] }, { "id": "zala-lancet", "title": "Lancet system article describing intelligent targeting and recognition", "publisher": "ZALA Aero", "date": "2026-07-23", "url": "https://zala-aero.com/en/news/bronemashina-vsu-unichtozhena-raschetom-ruk-zala-%C2%ABlanczet%C2%BB-v-dnr/", "type": "Manufacturer / belligerent claim", "supports": "Claimed intelligent targeting and recognition; not independent verification of control mode or performance.", "review": { "source_id": "zala-lancet", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "disputed", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "This manufacturer and belligerent claim remains attributed. It is not promoted into independent verification of control mode, field performance, or current configuration.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Preserve attribution and check whether later independent evidence changes the assessment.", "Do not resolve the dispute from repetition, confidence language, or source reachability." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "russia", "kind": "Atlas country", "label": "Russia", "path": "/atlas.php#atlas-country-russia" }, { "id": "lancet-family-claim", "kind": "Atlas system", "label": "Lancet-family “intelligent targeting” claim", "path": "/atlas.php#atlas-system-lancet-family-claim" }, { "id": "lancet-claim-2026", "kind": "Atlas timeline", "label": "A Lancet-family “intelligent targeting” claim is published", "path": "/atlas.php#historical-timeline" }, { "id": "lancet-combat-mode-claim", "kind": "Evidence Lab card", "label": "A ZALA article’s description of “intelligent targeting and recognition” proves that a named combat engagement used autonomous target selection and lethal release without human approval.", "path": "/evidence-lab.php#item-lancet-combat-mode-claim" } ] }, { "id": "csis-russia", "title": "How Russia Is Building a Sovereign Drone Ecosystem for AI-Driven Autonomy", "publisher": "Center for Strategic and International Studies", "date": "2026", "url": "https://www.csis.org/analysis/how-russia-building-sovereign-drone-ecosystem-ai-driven-autonomy", "type": "Independent analysis", "supports": "Public evidence and uncertainty concerning Russian drone autonomy development.", "review": { "source_id": "csis-russia", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Preserve attribution and check whether later independent evidence changes the assessment." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "russia", "kind": "Atlas country", "label": "Russia", "path": "/atlas.php#atlas-country-russia" }, { "id": "lancet-family-claim", "kind": "Atlas system", "label": "Lancet-family “intelligent targeting” claim", "path": "/atlas.php#atlas-system-lancet-family-claim" }, { "id": "lancet-claim-2026", "kind": "Atlas timeline", "label": "A Lancet-family “intelligent targeting” claim is published", "path": "/atlas.php#historical-timeline" }, { "id": "russia-autonomy-analysis", "kind": "Evidence Lab card", "label": "A CSIS report analyzes public evidence and uncertainty surrounding Russia’s development of AI-driven drone autonomy; it does not present itself as direct telemetry from every named engagement.", "path": "/evidence-lab.php#item-russia-autonomy-analysis" }, { "id": "lancet-combat-mode-claim", "kind": "Evidence Lab card", "label": "A ZALA article’s description of “intelligent targeting and recognition” proves that a named combat engagement used autonomous target selection and lethal release without human approval.", "path": "/evidence-lab.php#item-lancet-combat-mode-claim" } ] }, { "id": "ukraine-saker", "title": "Ukraine’s Armed Forces will use SAKER SCOUT drones with AI", "publisher": "Ukrainska Pravda", "date": "2023-09-04", "url": "https://www.pravda.com.ua/eng/news/2023/09/04/7418331/", "type": "Public reporting", "supports": "Reported approval and use of AI-enabled detection on the Saker Scout system.", "review": { "source_id": "ukraine-saker", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Preserve attribution and check whether later independent evidence changes the assessment.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "ukraine", "kind": "Atlas country", "label": "Ukraine", "path": "/atlas.php#atlas-country-ukraine" }, { "id": "saker-scout", "kind": "Atlas system", "label": "Saker Scout", "path": "/atlas.php#atlas-system-saker-scout" }, { "id": "saker-report-2023", "kind": "Atlas timeline", "label": "Public reporting describes Saker Scout AI functions", "path": "/atlas.php#historical-timeline" } ] }, { "id": "rand-pla-ai", "title": "The People’s Liberation Army’s Perspectives on Artificial Intelligence", "publisher": "RAND Corporation", "date": "2025", "url": "https://www.rand.org/pubs/perspectives/PEA4574-1.html", "type": "Independent research", "supports": "PLA writings and the emphasis on integration, intelligentization, and decision advantage.", "review": { "source_id": "rand-pla-ai", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "china", "kind": "Atlas country", "label": "People’s Republic of China", "path": "/atlas.php#atlas-country-china" }, { "id": "pla-intelligentization-research", "kind": "Atlas system", "label": "PLA intelligentization and kill-web research", "path": "/atlas.php#atlas-system-pla-intelligentization-research" } ] }, { "id": "ndu-pla-ai", "title": "Is the PLA Overestimating the Potential of Artificial Intelligence?", "publisher": "National Defense University Press", "date": "2025", "url": "https://ndupress.ndu.edu/Media/News/News-Article-View/Article/4042798/is-the-pla-overestimating-the-potential-of-artificial-intelligence/", "type": "Government research analysis", "supports": "Analysis of PLA intelligentization ambitions and uncertainty about maturity.", "review": { "source_id": "ndu-pla-ai", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Preserve attribution and check whether later independent evidence changes the assessment." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "china", "kind": "Atlas country", "label": "People’s Republic of China", "path": "/atlas.php#atlas-country-china" }, { "id": "pla-intelligentization-research", "kind": "Atlas system", "label": "PLA intelligentization and kill-web research", "path": "/atlas.php#atlas-system-pla-intelligentization-research" } ] }, { "id": "cna-prc-kill-web", "title": "Exploring PRC Research on Kill Chains and Kill Webs", "publisher": "CNA", "date": "2026-07", "url": "https://www.cna.org/analyses/2026/07/exploring-prc-research-on-kill-chains-and-kill-webs", "type": "Independent research", "supports": "Public PRC research concepts; not direct confirmation of operational deployment.", "review": { "source_id": "cna-prc-kill-web", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "china", "kind": "Atlas country", "label": "People’s Republic of China", "path": "/atlas.php#atlas-country-china" }, { "id": "pla-intelligentization-research", "kind": "Atlas system", "label": "PLA intelligentization and kill-web research", "path": "/atlas.php#atlas-system-pla-intelligentization-research" } ] }, { "id": "icrc-autonomous-weapons", "title": "ICRC position on autonomous weapon systems", "publisher": "International Committee of the Red Cross", "date": "Current position", "url": "https://www.icrc.org/en/document/icrc-position-autonomous-weapon-systems", "type": "Institutional legal position", "supports": "Proposed prohibitions and restrictions, target type, predictability, time, area, scale, supervision, and deactivation.", "review": { "source_id": "icrc-autonomous-weapons", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "current-autonomous-weapons", "kind": "FAQ answer", "label": "Are fully autonomous lethal weapons currently used?", "path": "/faq.php#current-autonomous-weapons" }, { "id": "human-control-modes", "kind": "FAQ answer", "label": "What do human-in-the-loop, human-on-the-loop, and human-out-of-the-loop mean?", "path": "/faq.php#human-control-modes" }, { "id": "meaningful-human-control", "kind": "FAQ answer", "label": "What makes human control meaningful?", "path": "/faq.php#meaningful-human-control" }, { "id": "autonomous-weapon", "kind": "Glossary term", "label": "Autonomous weapon", "path": "/glossary.php#autonomous-weapon" }, { "id": "human-out-of-the-loop", "kind": "Glossary term", "label": "Human-out-of-the-loop after activation", "path": "/glossary.php#human-out-of-the-loop" }, { "id": "meaningful-human-control", "kind": "Glossary term", "label": "Meaningful human control", "path": "/glossary.php#meaningful-human-control" } ] }, { "id": "un-autonomous-weapons", "title": "Autonomous weapons systems — United Nations disarmament work", "publisher": "United Nations Office for Disarmament Affairs", "date": "Current", "url": "https://disarmament.unoda.org/the-convention-on-certain-conventional-weapons/background-on-laws-in-the-ccw/", "type": "Official multilateral process", "supports": "CCW discussions and the unsettled international governance process.", "review": { "source_id": "un-autonomous-weapons", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "meaningful-human-control", "kind": "Glossary term", "label": "Meaningful human control", "path": "/glossary.php#meaningful-human-control" } ] }, { "id": "lockheed-cyber-chain", "title": "Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains", "publisher": "Lockheed Martin", "date": "2011", "url": "https://www.lockheedmartin.com/content/dam/lockheed-martin/rms/documents/cyber/LM-White-Paper-Intel-Driven-Defense.pdf", "type": "Foundational framework paper", "supports": "Seven-stage Cyber Kill Chain and the premise of interrupting adversary progression.", "review": { "source_id": "lockheed-cyber-chain", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "cyber-kill-chain-2011", "kind": "Atlas timeline", "label": "The intrusion Cyber Kill Chain is formalized", "path": "/atlas.php#historical-timeline" }, { "id": "what-is-kill-chain", "kind": "FAQ answer", "label": "What is a kill chain?", "path": "/faq.php#what-is-kill-chain" }, { "id": "cyber-kill-chain", "kind": "FAQ answer", "label": "What is the Cyber Kill Chain?", "path": "/faq.php#cyber-kill-chain" }, { "id": "cyber-kill-chain", "kind": "Glossary term", "label": "Cyber Kill Chain", "path": "/glossary.php#cyber-kill-chain" }, { "id": "kill-chain", "kind": "Glossary term", "label": "Kill chain", "path": "/glossary.php#kill-chain" }, { "id": "lockheed-martin", "kind": "Technology provider", "label": "Lockheed Martin", "path": "/kill-chain-technology-providers/#provider-lockheed-martin" } ] }, { "id": "usn-phalanx", "title": "MK 15 Phalanx Close-In Weapon System fact file", "publisher": "U.S. Navy", "date": "Current fact file", "url": "https://www.navy.mil/resources/fact-files/display-factfiles/article/2167831/mk-15-phalanx-close-in-weapon-system-ciws/", "type": "Official program description", "supports": "Automated search, detection, evaluation, tracking, engagement, and kill assessment for bounded close-in defense.", "review": { "source_id": "usn-phalanx", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "phalanx-ciws", "kind": "Authority Casebook case", "label": "MK 15 Phalanx Close-In Weapon System", "path": "/authority-casebook.php#casebook-phalanx-ciws" }, { "id": "claim-ai-enabled-not-autonomous-synthesis", "kind": "Claim Lineage record", "label": "AI-enabled does not necessarily mean autonomous force.", "path": "/claim-lineage.php#claim-ai-enabled-not-autonomous-synthesis" }, { "id": "claim-phalanx-automatic-action", "kind": "Claim Lineage record", "label": "Phalanx can complete a bounded close-in defensive sequence automatically.", "path": "/claim-lineage.php#claim-phalanx-automatic-action" }, { "id": "rtx-phalanx", "kind": "Company-system relationship", "label": "RTX / Raytheon → MK 15 Phalanx CIWS", "path": "/kill-chain-technology-providers/#relationship-rtx-phalanx" }, { "id": "phalanx-automatic-not-ai", "kind": "Evidence Lab card", "label": "The Navy fact file supports the proposition that Phalanx can automatically perform a bounded close-in defense sequence; that fact alone does not establish that its core operational logic uses machine learning.", "path": "/evidence-lab.php#item-phalanx-automatic-not-ai" }, { "id": "current-autonomous-weapons", "kind": "FAQ answer", "label": "Are fully autonomous lethal weapons currently used?", "path": "/faq.php#current-autonomous-weapons" }, { "id": "phalanx-automatic", "kind": "FAQ answer", "label": "Can Phalanx complete a defensive engagement automatically?", "path": "/faq.php#phalanx-automatic" }, { "id": "institutional-authority-casebook", "kind": "FAQ answer", "label": "What is the Institutional Authority Casebook?", "path": "/faq.php#institutional-authority-casebook" }, { "id": "why-automate", "kind": "FAQ answer", "label": "Why are humans removed from some immediate kill-chain functions?", "path": "/faq.php#why-automate" }, { "id": "algorithmic-automation", "kind": "Glossary term", "label": "Algorithmic automation", "path": "/glossary.php#algorithmic-automation" }, { "id": "authority-casebook", "kind": "Glossary term", "label": "Institutional Authority Casebook", "path": "/glossary.php#authority-casebook" }, { "id": "phalanx", "kind": "Human Control case", "label": "MK 15 Phalanx CIWS", "path": "/human-control.php#case-phalanx" }, { "id": "rtx", "kind": "Technology provider", "label": "RTX / Raytheon", "path": "/kill-chain-technology-providers/#provider-rtx" } ] }, { "id": "usn-searam", "title": "SeaRAM Close-In Weapon System fact file", "publisher": "U.S. Navy", "date": "Current fact file", "url": "https://www.navy.mil/Resources/Fact-Files/Display-FactFiles/Article/2167555/searam-close-in-weapon-system-ciws-anti-ship-missile-defense-system/", "type": "Official program description", "supports": "Self-contained close-in defense combining autonomous search and track functions with a guided interceptor launcher.", "review": { "source_id": "usn-searam", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "rtx-searam", "kind": "Company-system relationship", "label": "RTX / Raytheon → SeaRAM ship-defense system", "path": "/kill-chain-technology-providers/#relationship-rtx-searam" }, { "id": "current-autonomous-weapons", "kind": "FAQ answer", "label": "Are fully autonomous lethal weapons currently used?", "path": "/faq.php#current-autonomous-weapons" }, { "id": "searam", "kind": "Human Control case", "label": "SeaRAM", "path": "/human-control.php#case-searam" }, { "id": "rtx", "kind": "Technology provider", "label": "RTX / Raytheon", "path": "/kill-chain-technology-providers/#provider-rtx" } ] }, { "id": "rafael-iron-dome", "title": "Iron Dome product and system description", "publisher": "Rafael Advanced Defense Systems", "date": "Current product page", "url": "https://www.rafael.co.il/system/iron-dome/", "type": "Manufacturer description", "supports": "Radar, battle management, launchers, interceptors, selective defense, and multi-target operation.", "review": { "source_id": "rafael-iron-dome", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-iron-dome-impact-inference", "kind": "Claim Lineage record", "label": "Battle management estimates a trajectory and impact area.", "path": "/claim-lineage.php#claim-iron-dome-impact-inference" }, { "id": "claim-iron-dome-track-observation", "kind": "Claim Lineage record", "label": "Iron Dome public description begins with radar detection and tracking.", "path": "/claim-lineage.php#claim-iron-dome-track-observation" }, { "id": "claim-iron-dome-selective-priority", "kind": "Claim Lineage record", "label": "Selective defense prioritizes threats predicted to reach defended zones.", "path": "/claim-lineage.php#claim-iron-dome-selective-priority" }, { "id": "mprest-iron-dome-bmc", "kind": "Company-system relationship", "label": "mPrest Systems → Iron Dome battle-management and weapon-control software", "path": "/kill-chain-technology-providers/#relationship-mprest-iron-dome-bmc" }, { "id": "rafael-iron-dome", "kind": "Company-system relationship", "label": "Rafael Advanced Defense Systems → Iron Dome defensive system", "path": "/kill-chain-technology-providers/#relationship-rafael-iron-dome" }, { "id": "iron-dome-selective-defense", "kind": "Evidence Lab card", "label": "Rafael describes Iron Dome as using radar, battle management, launchers, interceptors, selective defense, and simultaneous handling of multiple threats.", "path": "/evidence-lab.php#item-iron-dome-selective-defense" }, { "id": "circular-reporting-demo", "kind": "Evidence Lab card", "label": "Three fictional briefings repeat the same Iron Dome capability sentence from one manufacturer page, so the dashboard counts three independent confirmations.", "path": "/evidence-lab.php#item-circular-reporting-demo" }, { "id": "iron-dome-autonomy", "kind": "FAQ answer", "label": "Is Iron Dome fully autonomous?", "path": "/faq.php#iron-dome-autonomy" }, { "id": "iron-dome", "kind": "Human Control case", "label": "Iron Dome", "path": "/human-control.php#case-iron-dome" }, { "id": "mprest", "kind": "Technology provider", "label": "mPrest Systems", "path": "/kill-chain-technology-providers/#provider-mprest" }, { "id": "rafael", "kind": "Technology provider", "label": "Rafael Advanced Defense Systems", "path": "/kill-chain-technology-providers/#provider-rafael" } ] }, { "id": "usaf-cca-control", "title": "Collaborative Combat Aircraft program progresses through deliberate weapons integration", "publisher": "U.S. Air Force", "date": "2026-02-23", "url": "https://www.af.mil/news/article-display/article/4412705/collaborative-combat-aircraft-program-progresses-through-deliberate-weapons-int/", "type": "Official operator statement", "supports": "Developmental weapons integration and explicit human retention of weapons-release authority in the described testing context.", "review": { "source_id": "usaf-cca-control", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "collaborative-combat-aircraft", "kind": "Authority Casebook case", "label": "Collaborative Combat Aircraft", "path": "/authority-casebook.php#casebook-collaborative-combat-aircraft" }, { "id": "claim-cca-human-release-authority", "kind": "Claim Lineage record", "label": "The Air Force says humans retain CCA weapon-release authority in the described testing context.", "path": "/claim-lineage.php#claim-cca-human-release-authority" }, { "id": "cca-development-authority", "kind": "Evidence Lab card", "label": "The U.S. Air Force says that a human retains authority over weapons-release decisions throughout the Collaborative Combat Aircraft development and testing activity described in its February 2026 update.", "path": "/evidence-lab.php#item-cca-development-authority" }, { "id": "operational-delegation-versus-legal-authority", "kind": "FAQ answer", "label": "Does operational delegation give a machine legal authority?", "path": "/faq.php#operational-delegation-versus-legal-authority" }, { "id": "institutional-authority", "kind": "FAQ answer", "label": "What does institutional authority mean in an AI-mediated decision chain?", "path": "/faq.php#institutional-authority" }, { "id": "institutional-authority", "kind": "Glossary term", "label": "Institutional authority", "path": "/glossary.php#institutional-authority" }, { "id": "operational-delegation", "kind": "Glossary term", "label": "Operational delegation", "path": "/glossary.php#operational-delegation" }, { "id": "cca", "kind": "Human Control case", "label": "Collaborative Combat Aircraft", "path": "/human-control.php#case-cca" } ] }, { "id": "army-titan", "title": "Army Tactical Intelligence Targeting Access Node prototype award", "publisher": "U.S. Army PEO IEW&S", "date": "2024-03-06", "url": "https://cpeisw.army.mil/2024/03/06/army-tactical-intelligence-targeting-access-node-titan-ground-station-prototype-award/", "type": "Official program description", "supports": "AI/ML-enabled processing of space, high-altitude, aerial, and terrestrial sensor data for operational decision support.", "review": { "source_id": "army-titan", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "palantir-titan", "kind": "Company-system relationship", "label": "Palantir Technologies → Tactical Intelligence Targeting Access Node", "path": "/kill-chain-technology-providers/#relationship-palantir-titan" }, { "id": "algorithmic-gatekeeper", "kind": "FAQ answer", "label": "How can an algorithm shape a human decision without authorizing force?", "path": "/faq.php#algorithmic-gatekeeper" }, { "id": "ai-enabled-versus-autonomous", "kind": "FAQ answer", "label": "Is an AI-enabled kill chain the same as an autonomous weapon?", "path": "/faq.php#ai-enabled-versus-autonomous" }, { "id": "ai-enabled-kill-chain", "kind": "Glossary term", "label": "AI-enabled kill chain", "path": "/glossary.php#ai-enabled-kill-chain" }, { "id": "sensor-fusion", "kind": "Glossary term", "label": "Sensor fusion", "path": "/glossary.php#sensor-fusion" }, { "id": "titan", "kind": "Human Control case", "label": "TITAN", "path": "/human-control.php#case-titan" }, { "id": "palantir", "kind": "Technology provider", "label": "Palantir Technologies", "path": "/kill-chain-technology-providers/#provider-palantir" } ] }, { "id": "sda-tracking", "title": "Proliferated Warfighter Space Architecture Tracking Layer", "publisher": "Space Development Agency", "date": "Current architecture page", "url": "https://www.sda.mil/tracking/", "type": "Official program description", "supports": "Sensing, algorithms, processing, data fusion, missile warning and tracking, and tactical data products.", "review": { "source_id": "sda-tracking", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "algorithmic-gatekeeper", "kind": "FAQ answer", "label": "How can an algorithm shape a human decision without authorizing force?", "path": "/faq.php#algorithmic-gatekeeper" }, { "id": "sensor-fusion", "kind": "Glossary term", "label": "Sensor fusion", "path": "/glossary.php#sensor-fusion" }, { "id": "tracking-layer", "kind": "Human Control case", "label": "SDA Tracking Layer", "path": "/human-control.php#case-tracking-layer" } ] }, { "id": "army-ibcs", "title": "IBCS and the future of offensive and defensive integrated fires", "publisher": "U.S. Army", "date": "2026", "url": "https://www.army.mil/article/290087/ibcs_and_the_future_of_offensive_and_defensive_integrated_fires", "type": "Official program description", "supports": "Integrated sensors, command-and-control nodes, and effectors; not a universal claim of machine-learning use or autonomous firing.", "review": { "source_id": "army-ibcs", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "northrop-ibcs", "kind": "Company-system relationship", "label": "Northrop Grumman → Integrated Battle Command System", "path": "/kill-chain-technology-providers/#relationship-northrop-ibcs" }, { "id": "ibcs-ai-and-fire-authority", "kind": "Evidence Lab card", "label": "The reviewed public record specifies that every IBCS track-correlation function uses machine learning and that the system autonomously authorizes firing in every configuration.", "path": "/evidence-lab.php#item-ibcs-ai-and-fire-authority" }, { "id": "algorithmic-gatekeeper", "kind": "FAQ answer", "label": "How can an algorithm shape a human decision without authorizing force?", "path": "/faq.php#algorithmic-gatekeeper" }, { "id": "algorithmic-automation", "kind": "Glossary term", "label": "Algorithmic automation", "path": "/glossary.php#algorithmic-automation" }, { "id": "sensor-fusion", "kind": "Glossary term", "label": "Sensor fusion", "path": "/glossary.php#sensor-fusion" }, { "id": "ibcs", "kind": "Human Control case", "label": "Integrated Battle Command System", "path": "/human-control.php#case-ibcs" }, { "id": "northrop-grumman", "kind": "Technology provider", "label": "Northrop Grumman", "path": "/kill-chain-technology-providers/#provider-northrop-grumman" } ] }, { "id": "darpa-ace", "title": "Air Combat Evolution program", "publisher": "Defense Advanced Research Projects Agency", "date": "Current program page", "url": "https://www.darpa.mil/research/programs/air-combat-evolution", "type": "Official research-program description", "supports": "The shift from single-platform operator toward mission commander of multiple autonomous aircraft.", "review": { "source_id": "darpa-ace", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "why-automate", "kind": "FAQ answer", "label": "Why are humans removed from some immediate kill-chain functions?", "path": "/faq.php#why-automate" }, { "id": "cca", "kind": "Human Control case", "label": "Collaborative Combat Aircraft", "path": "/human-control.php#case-cca" } ] }, { "id": "darpa-mosaic", "title": "Building cross-domain kill webs", "publisher": "Defense Advanced Research Projects Agency", "date": "2020", "url": "https://www.darpa.mil/news/2020/cross-domain-kill-webs", "type": "Official research-program description", "supports": "Composing distributed sensors, command nodes, and effects into adaptable cross-domain networks.", "review": { "source_id": "darpa-mosaic", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "kill-chain-versus-kill-web", "kind": "FAQ answer", "label": "What is the difference between a kill chain and a kill web?", "path": "/faq.php#kill-chain-versus-kill-web" }, { "id": "kill-web", "kind": "Glossary term", "label": "Kill web", "path": "/glossary.php#kill-web" } ] }, { "id": "darpa-lrasm", "title": "Long Range Anti-Ship Missile program", "publisher": "Defense Advanced Research Projects Agency", "date": "Historical program description", "url": "https://www.darpa.mil/research/programs/long-range-anti-ship-missile", "type": "Official program description", "supports": "Semi-autonomous operation and reduced reliance on external networks in contested environments.", "review": { "source_id": "darpa-lrasm", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "communications-loss", "kind": "FAQ answer", "label": "Does losing communications mean a system selects targets autonomously?", "path": "/faq.php#communications-loss" }, { "id": "lrasm", "kind": "Human Control case", "label": "Long Range Anti-Ship Missile", "path": "/human-control.php#case-lrasm" } ] }, { "id": "navair-lrasm", "title": "Long Range Anti-Ship Missile product page", "publisher": "Naval Air Systems Command", "date": "Current product page", "url": "https://www.navair.navy.mil/product/Long-Range-Anti-Ship-Missile-LRASM", "type": "Official operator/program description", "supports": "Fielded long-range anti-ship capability with onboard sensing and terminal guidance; detailed authority boundaries remain nonpublic.", "review": { "source_id": "navair-lrasm", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "communications-loss", "kind": "FAQ answer", "label": "Does losing communications mean a system selects targets autonomously?", "path": "/faq.php#communications-loss" }, { "id": "lrasm", "kind": "Human Control case", "label": "Long Range Anti-Ship Missile", "path": "/human-control.php#case-lrasm" } ] }, { "id": "mitre-attack", "title": "MITRE ATT&CK", "publisher": "MITRE", "date": "Living knowledge base", "url": "https://attack.mitre.org/", "type": "Threat knowledge base", "supports": "Behavior-level tactics and techniques that complement, rather than duplicate, a linear kill-chain narrative.", "review": { "source_id": "mitre-attack", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "cyber-kill-chain", "kind": "FAQ answer", "label": "What is the Cyber Kill Chain?", "path": "/faq.php#cyber-kill-chain" } ] }, { "id": "aerovironment-puma-le", "title": "Puma LE product description", "publisher": "AeroVironment", "date": "Current product page", "url": "https://www.avinc.com/solution/puma-le/", "type": "Manufacturer description", "supports": "Company-described long-endurance small-uncrewed-aircraft sensing, communications relay, and operational use by government customers.", "review": { "source_id": "aerovironment-puma-le", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "aerovironment-puma-le", "kind": "Company-system relationship", "label": "AeroVironment → Puma LE small UAS", "path": "/kill-chain-technology-providers/#relationship-aerovironment-puma-le" }, { "id": "aerovironment", "kind": "Technology provider", "label": "AeroVironment", "path": "/kill-chain-technology-providers/#provider-aerovironment" } ] }, { "id": "aerovironment-switchblade600", "title": "Switchblade 600 product description", "publisher": "AeroVironment", "date": "Current product page", "url": "https://www.avinc.com/solution/switchblade-600/", "type": "Manufacturer description", "supports": "Company-described loitering-system sensing, mission control, tracking, and post-launch functions; not a universal statement of engagement authority.", "review": { "source_id": "aerovironment-switchblade600", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "aerovironment-switchblade-600", "kind": "Company-system relationship", "label": "AeroVironment → Switchblade 600 family", "path": "/kill-chain-technology-providers/#relationship-aerovironment-switchblade-600" }, { "id": "aerovironment", "kind": "Technology provider", "label": "AeroVironment", "path": "/kill-chain-technology-providers/#provider-aerovironment" } ] }, { "id": "anduril-lattice", "title": "Lattice command-and-control platform", "publisher": "Anduril Industries", "date": "Current product page", "url": "https://www.anduril.com/lattice/command-and-control", "type": "Manufacturer description", "supports": "Company-described sensor integration, track fusion, command and control, and human-machine teaming.", "review": { "source_id": "anduril-lattice", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "anduril-lattice", "kind": "Company-system relationship", "label": "Anduril Industries → Lattice command-and-control platform", "path": "/kill-chain-technology-providers/#relationship-anduril-lattice" }, { "id": "anduril", "kind": "Technology provider", "label": "Anduril Industries", "path": "/kill-chain-technology-providers/#provider-anduril" } ] }, { "id": "army-anduril-cuas", "title": "Army and DIU select Anduril for next-generation counter-UAS fire control", "publisher": "U.S. Army", "date": "Current official announcement", "url": "https://www.army.mil/article/288909/army_diu_select_anduril_to_advance_next_generation_counter_uas_fire_control_capabilities", "type": "Official selection announcement", "supports": "Government selection and prototyping for counter-UAS fire-control capability; not proof of every final operational configuration.", "review": { "source_id": "army-anduril-cuas", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "anduril-counter-uas-fire-control", "kind": "Company-system relationship", "label": "Anduril Industries → Next-generation counter-UAS fire control", "path": "/kill-chain-technology-providers/#relationship-anduril-counter-uas-fire-control" }, { "id": "anduril", "kind": "Technology provider", "label": "Anduril Industries", "path": "/kill-chain-technology-providers/#provider-anduril" } ] }, { "id": "army-anduril-ngc2", "title": "Army announces Next Generation Command and Control prototype award", "publisher": "U.S. Army", "date": "Current official announcement", "url": "https://www.army.mil/article/287180/army_announces_next_generation_command_and_control_ngc2_prototype_award", "type": "Official prototype award", "supports": "Government-described participation in a command-and-control prototype; developmental status must remain visible.", "review": { "source_id": "army-anduril-ngc2", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "anduril", "kind": "Technology provider", "label": "Anduril Industries", "path": "/kill-chain-technology-providers/#provider-anduril" } ] }, { "id": "auterion-platform", "title": "Auterion autonomous-systems platform", "publisher": "Auterion", "date": "Current company page", "url": "https://auterion.com/", "type": "Manufacturer description", "supports": "Company-described edge autonomy, mission software, uncrewed-system coordination, and terminal tracking functions.", "review": { "source_id": "auterion-platform", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "auterion-skynode", "kind": "Company-system relationship", "label": "Auterion → Skynode autonomy platform", "path": "/kill-chain-technology-providers/#relationship-auterion-skynode" }, { "id": "auterion", "kind": "Technology provider", "label": "Auterion", "path": "/kill-chain-technology-providers/#provider-auterion" } ] }, { "id": "auterion-ukraine-contract", "title": "Auterion announces Skynode strike-kit contract for Ukraine", "publisher": "Auterion", "date": "Current company announcement", "url": "https://auterion.com/auterion-secures-contract-to-deliver-33000-skynode-drone-strike-kits-to-ukraine/", "type": "Manufacturer / contract announcement", "supports": "Company-reported government-funded delivery commitment; not independent verification of mode-specific field behavior or results.", "review": { "source_id": "auterion-ukraine-contract", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "auterion-skynode", "kind": "Company-system relationship", "label": "Auterion → Skynode autonomy platform", "path": "/kill-chain-technology-providers/#relationship-auterion-skynode" }, { "id": "auterion", "kind": "Technology provider", "label": "Auterion", "path": "/kill-chain-technology-providers/#provider-auterion" } ] }, { "id": "bae-combat-management", "title": "Combat Management Systems", "publisher": "BAE Systems", "date": "Current product page", "url": "https://www.baesystems.com/en/product/combat-management-systems", "type": "Manufacturer description", "supports": "Company-described naval combat-management, sensor integration, situational awareness, and command support.", "review": { "source_id": "bae-combat-management", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "bae-inteact", "kind": "Company-system relationship", "label": "BAE Systems → INTeACT combat-management software", "path": "/kill-chain-technology-providers/#relationship-bae-inteact" }, { "id": "bae-systems", "kind": "Technology provider", "label": "BAE Systems", "path": "/kill-chain-technology-providers/#provider-bae-systems" } ] }, { "id": "bae-inteact-sdk", "title": "INTeACT Software Development Kit", "publisher": "BAE Systems", "date": "Current product page", "url": "https://www.baesystems.com/en/product/inteact-software-development-kit", "type": "Manufacturer description", "supports": "Company-described integration surface for combat-management applications and mission-system services.", "review": { "source_id": "bae-inteact-sdk", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "bae-inteact", "kind": "Company-system relationship", "label": "BAE Systems → INTeACT combat-management software", "path": "/kill-chain-technology-providers/#relationship-bae-inteact" }, { "id": "bae-systems", "kind": "Technology provider", "label": "BAE Systems", "path": "/kill-chain-technology-providers/#provider-bae-systems" } ] }, { "id": "crowdstrike-falcon", "title": "CrowdStrike Falcon platform", "publisher": "CrowdStrike", "date": "Current product page", "url": "https://www.crowdstrike.com/en-us/platform/", "type": "Manufacturer description", "supports": "Company-described endpoint, identity, cloud, threat-intelligence, investigation, and response capabilities used in security operations.", "review": { "source_id": "crowdstrike-falcon", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "crowdstrike-falcon", "kind": "Company-system relationship", "label": "CrowdStrike → Falcon security platform", "path": "/kill-chain-technology-providers/#relationship-crowdstrike-falcon" }, { "id": "crowdstrike", "kind": "Technology provider", "label": "CrowdStrike", "path": "/kill-chain-technology-providers/#provider-crowdstrike" } ] }, { "id": "diehl-iris-t-estonia", "title": "First IRIS-T SLM fire unit delivered to Estonia", "publisher": "Diehl Defence", "date": "Current company announcement", "url": "https://new.diehl.com/defence/en/press-media/news/diehl-defence-strengthens-nato-air-defence-first-iris-t-slm-fire-unit-delivered-to-estonia", "type": "Manufacturer / delivery announcement", "supports": "Company-reported delivery of an air-defense fire unit to a NATO customer; not independent performance validation.", "review": { "source_id": "diehl-iris-t-estonia", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "diehl-iris-t-slm", "kind": "Company-system relationship", "label": "Diehl Defence → IRIS-T SLM air-defense system", "path": "/kill-chain-technology-providers/#relationship-diehl-iris-t-slm" }, { "id": "diehl-defence", "kind": "Technology provider", "label": "Diehl Defence", "path": "/kill-chain-technology-providers/#provider-diehl-defence" } ] }, { "id": "gaasi-mq9b", "title": "MQ-9B SkyGuardian product description", "publisher": "General Atomics Aeronautical Systems", "date": "Current product page", "url": "https://www.ga-asi.com/remotely-piloted-aircraft/mq-9b-skyguardian", "type": "Manufacturer description", "supports": "Company-described remotely piloted aircraft, sensing, endurance, communications, and mission-system integration.", "review": { "source_id": "gaasi-mq9b", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "general-atomics-mq9b", "kind": "Company-system relationship", "label": "General Atomics Aeronautical Systems → MQ-9B SkyGuardian family", "path": "/kill-chain-technology-providers/#relationship-general-atomics-mq9b" }, { "id": "general-atomics", "kind": "Technology provider", "label": "General Atomics Aeronautical Systems", "path": "/kill-chain-technology-providers/#provider-general-atomics" } ] }, { "id": "gaasi-team-skyguardian", "title": "Team SkyGuardian Canada", "publisher": "General Atomics Aeronautical Systems", "date": "Current company page", "url": "https://www.ga-asi.com/teamskyguardiancanada/", "type": "Manufacturer / program statement", "supports": "Company-described government procurement and industrial-team context for MQ-9B; not a statement of mission-specific employment.", "review": { "source_id": "gaasi-team-skyguardian", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "general-atomics-mq9b", "kind": "Company-system relationship", "label": "General Atomics Aeronautical Systems → MQ-9B SkyGuardian family", "path": "/kill-chain-technology-providers/#relationship-general-atomics-mq9b" }, { "id": "general-atomics", "kind": "Technology provider", "label": "General Atomics Aeronautical Systems", "path": "/kill-chain-technology-providers/#provider-general-atomics" } ] }, { "id": "google-secops", "title": "Google Security Operations", "publisher": "Google Cloud", "date": "Current product page", "url": "https://cloud.google.com/security/products/security-operations", "type": "Manufacturer description", "supports": "Company-described SIEM, detection, investigation, threat intelligence, and response workflows for security operations.", "review": { "source_id": "google-secops", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "google-security-operations", "kind": "Company-system relationship", "label": "Google Cloud / Mandiant → Google Security Operations and Mandiant services", "path": "/kill-chain-technology-providers/#relationship-google-security-operations" }, { "id": "google-mandiant", "kind": "Technology provider", "label": "Google Cloud / Mandiant", "path": "/kill-chain-technology-providers/#provider-google-mandiant" } ] }, { "id": "google-mandiant-threat-defense", "title": "Mandiant Managed Threat Hunting", "publisher": "Google Cloud / Mandiant", "date": "Current service page", "url": "https://cloud.google.com/security/products/mandiant-managed-threat-hunting", "type": "Provider description", "supports": "Provider-described managed hunting, investigation, and incident-response support; not a universal measure of detection effectiveness.", "review": { "source_id": "google-mandiant-threat-defense", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "google-security-operations", "kind": "Company-system relationship", "label": "Google Cloud / Mandiant → Google Security Operations and Mandiant services", "path": "/kill-chain-technology-providers/#relationship-google-security-operations" }, { "id": "google-mandiant", "kind": "Technology provider", "label": "Google Cloud / Mandiant", "path": "/kill-chain-technology-providers/#provider-google-mandiant" } ] }, { "id": "helsing-hx2", "title": "HX-2 product description", "publisher": "Helsing", "date": "Current product page", "url": "https://helsing.ai/hx-2", "type": "Manufacturer description", "supports": "Company-described software-defined uncrewed system, onboard autonomy, human-control framing, and mission functions.", "review": { "source_id": "helsing-hx2", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "helsing-hx2", "kind": "Company-system relationship", "label": "Helsing → HX-2 uncrewed system", "path": "/kill-chain-technology-providers/#relationship-helsing-hx2" }, { "id": "helsing", "kind": "Technology provider", "label": "Helsing", "path": "/kill-chain-technology-providers/#provider-helsing" } ] }, { "id": "helsing-frontline-statement", "title": "Helsing public statement on frontline deployment", "publisher": "Helsing", "date": "Current company statement", "url": "https://helsing.ai/newsroom/statement-from-helsing", "type": "Manufacturer / deployment statement", "supports": "Company-reported operational delivery or use; independent mode-specific verification remains necessary.", "review": { "source_id": "helsing-frontline-statement", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "helsing-hx2", "kind": "Company-system relationship", "label": "Helsing → HX-2 uncrewed system", "path": "/kill-chain-technology-providers/#relationship-helsing-hx2" }, { "id": "helsing", "kind": "Technology provider", "label": "Helsing", "path": "/kill-chain-technology-providers/#provider-helsing" } ] }, { "id": "hensoldt-trml4d", "title": "TRML-4D air-surveillance and target-acquisition radar", "publisher": "HENSOLDT", "date": "Current product page", "url": "https://www.hensoldt.net/products/trml-4d-air-surveillance-and-target-acquisition-radar", "type": "Manufacturer description", "supports": "Company-described radar detection, tracking, target acquisition, and integration into air-defense networks.", "review": { "source_id": "hensoldt-trml4d", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "hensoldt-trml4d", "kind": "Company-system relationship", "label": "HENSOLDT → TRML-4D radar", "path": "/kill-chain-technology-providers/#relationship-hensoldt-trml4d" }, { "id": "hensoldt", "kind": "Technology provider", "label": "HENSOLDT", "path": "/kill-chain-technology-providers/#provider-hensoldt" } ] }, { "id": "hensoldt-ukraine-radars", "title": "HENSOLDT delivers further high-performance radars to Ukraine", "publisher": "HENSOLDT", "date": "Current company announcement", "url": "https://www.hensoldt.net/news/hensoldt-delivers-further-high-performance-radars-to-ukraine", "type": "Manufacturer / delivery announcement", "supports": "Company-reported delivery of radar systems for operational air-defense use; not independent performance validation.", "review": { "source_id": "hensoldt-ukraine-radars", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "hensoldt-trml4d", "kind": "Company-system relationship", "label": "HENSOLDT → TRML-4D radar", "path": "/kill-chain-technology-providers/#relationship-hensoldt-trml4d" }, { "id": "hensoldt", "kind": "Technology provider", "label": "HENSOLDT", "path": "/kill-chain-technology-providers/#provider-hensoldt" } ] }, { "id": "iai-elm2084", "title": "ELM-2084 Multi-Mission Radar", "publisher": "Israel Aerospace Industries / ELTA", "date": "Current product page", "url": "https://www.iai.co.il/product/elm-2084-mmr/", "type": "Manufacturer description", "supports": "Company-described multi-mission radar for detection, tracking, target acquisition, and fire-control support.", "review": { "source_id": "iai-elm2084", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "iai-elm2084", "kind": "Company-system relationship", "label": "Israel Aerospace Industries / ELTA → ELM-2084 Multi-Mission Radar", "path": "/kill-chain-technology-providers/#relationship-iai-elm2084" }, { "id": "iai", "kind": "Technology provider", "label": "Israel Aerospace Industries / ELTA", "path": "/kill-chain-technology-providers/#provider-iai" } ] }, { "id": "iai-barak-mx", "title": "BARAK MX air and missile defense system", "publisher": "Israel Aerospace Industries", "date": "Current product page", "url": "https://www.iai.co.il/product/barak-mx/", "type": "Manufacturer description", "supports": "Company-described networked air and missile defense, battle management, sensors, launchers, and interceptors.", "review": { "source_id": "iai-barak-mx", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "iai-barak-mx", "kind": "Company-system relationship", "label": "Israel Aerospace Industries / ELTA → BARAK MX air and missile defense", "path": "/kill-chain-technology-providers/#relationship-iai-barak-mx" }, { "id": "iai", "kind": "Technology provider", "label": "Israel Aerospace Industries / ELTA", "path": "/kill-chain-technology-providers/#provider-iai" } ] }, { "id": "kongsberg-nasams", "title": "NASAMS air-defense system", "publisher": "Kongsberg Defence & Aerospace", "date": "Current product page", "url": "https://www.kongsberg.com/what-we-do/defence-and-security/integrated-air-and-missile-defence/nasams-air-defence-system/", "type": "Manufacturer description", "supports": "Company-described distributed air-defense architecture connecting sensors, fire-distribution centers, launchers, and effectors.", "review": { "source_id": "kongsberg-nasams", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "kongsberg-nasams", "kind": "Company-system relationship", "label": "Kongsberg Defence & Aerospace → NASAMS air-defense system", "path": "/kill-chain-technology-providers/#relationship-kongsberg-nasams" }, { "id": "kongsberg", "kind": "Technology provider", "label": "Kongsberg Defence & Aerospace", "path": "/kill-chain-technology-providers/#provider-kongsberg" } ] }, { "id": "kongsberg-fdc", "title": "NASAMS Fire Distribution Center", "publisher": "Kongsberg Defence & Aerospace", "date": "Current product page", "url": "https://www.kongsberg.com/what-we-do/defence-and-security/integrated-air-and-missile-defence/nasams-fire-distribution-center-fdc/", "type": "Manufacturer description", "supports": "Company-described command, control, communications, sensor fusion, threat evaluation, and weapon coordination.", "review": { "source_id": "kongsberg-fdc", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "kongsberg-fdc", "kind": "Company-system relationship", "label": "Kongsberg Defence & Aerospace → NASAMS Fire Distribution Center", "path": "/kill-chain-technology-providers/#relationship-kongsberg-fdc" }, { "id": "kongsberg", "kind": "Technology provider", "label": "Kongsberg Defence & Aerospace", "path": "/kill-chain-technology-providers/#provider-kongsberg" } ] }, { "id": "l3harris-resilient-comms", "title": "Resilient communications and networks", "publisher": "L3Harris Technologies", "date": "Current capability page", "url": "https://www.l3harris.com/all-capabilities/resilient-communications-and-networks", "type": "Manufacturer description", "supports": "Company-described tactical communications, resilient networking, data exchange, and command connectivity.", "review": { "source_id": "l3harris-resilient-comms", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "l3harris-resilient-comms", "kind": "Company-system relationship", "label": "L3Harris Technologies → Resilient tactical communications and data links", "path": "/kill-chain-technology-providers/#relationship-l3harris-resilient-comms" }, { "id": "l3harris", "kind": "Technology provider", "label": "L3Harris Technologies", "path": "/kill-chain-technology-providers/#provider-l3harris" } ] }, { "id": "leonardo-command-control", "title": "Command and control systems", "publisher": "Leonardo", "date": "Current capability page", "url": "https://electronics.leonardo.com/en/command-and-control", "type": "Manufacturer description", "supports": "Company-described command-and-control, mission management, information fusion, and decision-support capabilities.", "review": { "source_id": "leonardo-command-control", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "leonardo-command-control", "kind": "Company-system relationship", "label": "Leonardo → Leonardo command-and-control systems", "path": "/kill-chain-technology-providers/#relationship-leonardo-command-control" }, { "id": "leonardo", "kind": "Technology provider", "label": "Leonardo", "path": "/kill-chain-technology-providers/#provider-leonardo" } ] }, { "id": "leonardo-radars-sensors", "title": "Radars and sensors", "publisher": "Leonardo", "date": "Current capability page", "url": "https://electronics.leonardo.com/en/radars-sensors", "type": "Manufacturer description", "supports": "Company-described radar, electro-optical, and sensor technologies for surveillance, tracking, fire control, and situational awareness.", "review": { "source_id": "leonardo-radars-sensors", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "leonardo-radars", "kind": "Company-system relationship", "label": "Leonardo → Leonardo radar and sensor portfolio", "path": "/kill-chain-technology-providers/#relationship-leonardo-radars" }, { "id": "leonardo", "kind": "Technology provider", "label": "Leonardo", "path": "/kill-chain-technology-providers/#provider-leonardo" } ] }, { "id": "lockheed-aegis", "title": "Aegis Combat System", "publisher": "Lockheed Martin", "date": "Current product page", "url": "https://www.lockheedmartin.com/en-us/products/aegis-combat-system.html", "type": "Manufacturer description", "supports": "Company-described naval combat-system integration of sensors, command and decision, fire control, and effectors.", "review": { "source_id": "lockheed-aegis", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "lockheed-aegis", "kind": "Company-system relationship", "label": "Lockheed Martin → Aegis Combat System", "path": "/kill-chain-technology-providers/#relationship-lockheed-aegis" }, { "id": "lockheed-martin", "kind": "Technology provider", "label": "Lockheed Martin", "path": "/kill-chain-technology-providers/#provider-lockheed-martin" } ] }, { "id": "usn-aegis", "title": "Aegis Weapon System fact file", "publisher": "U.S. Navy", "date": "Current fact file", "url": "https://www.navy.mil/Resources/Fact-Files/Display-FactFiles/Article/2166739/aegis-weapon-system/", "type": "Official program description", "supports": "Operator-described Aegis radar, command-and-decision, fire-control, and weapon-system integration.", "review": { "source_id": "usn-aegis", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "lockheed-aegis", "kind": "Company-system relationship", "label": "Lockheed Martin → Aegis Combat System", "path": "/kill-chain-technology-providers/#relationship-lockheed-aegis" }, { "id": "lockheed-martin", "kind": "Technology provider", "label": "Lockheed Martin", "path": "/kill-chain-technology-providers/#provider-lockheed-martin" } ] }, { "id": "mbda-sea-ceptor", "title": "Sea Ceptor", "publisher": "MBDA", "date": "Current product page", "url": "https://www.mbda-systems.com/products/force-protection/camm-family/sea-ceptor", "type": "Manufacturer description", "supports": "Company-described naval local-area air defense and integration with ship combat-management and sensor systems.", "review": { "source_id": "mbda-sea-ceptor", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "mbda-sea-ceptor", "kind": "Company-system relationship", "label": "MBDA → Sea Ceptor air-defense system", "path": "/kill-chain-technology-providers/#relationship-mbda-sea-ceptor" }, { "id": "mbda", "kind": "Technology provider", "label": "MBDA", "path": "/kill-chain-technology-providers/#provider-mbda" } ] }, { "id": "microsoft-sentinel", "title": "Microsoft Sentinel SIEM", "publisher": "Microsoft Security", "date": "Current product page", "url": "https://www.microsoft.com/en-us/security/business/siem-and-xdr/microsoft-sentinel-siem", "type": "Manufacturer description", "supports": "Company-described cloud-native SIEM, threat detection, investigation, automation, and response.", "review": { "source_id": "microsoft-sentinel", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "microsoft-sentinel", "kind": "Company-system relationship", "label": "Microsoft Security → Microsoft Sentinel", "path": "/kill-chain-technology-providers/#relationship-microsoft-sentinel" }, { "id": "microsoft-security", "kind": "Technology provider", "label": "Microsoft Security", "path": "/kill-chain-technology-providers/#provider-microsoft-security" } ] }, { "id": "milrem-themis-family", "title": "THeMIS uncrewed-ground-vehicle family", "publisher": "Milrem Robotics", "date": "Current product page", "url": "https://milremrobotics.com/themis-family/", "type": "Manufacturer description", "supports": "Company-described autonomous mobility, modular mission payloads, logistics, reconnaissance, and human-controlled weapon integration.", "review": { "source_id": "milrem-themis-family", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "milrem-themis", "kind": "Company-system relationship", "label": "Milrem Robotics → themis-combat-ugv", "path": "/kill-chain-technology-providers/#relationship-milrem-themis" }, { "id": "milrem-robotics", "kind": "Technology provider", "label": "Milrem Robotics", "path": "/kill-chain-technology-providers/#provider-milrem-robotics" } ] }, { "id": "milrem-ukraine-themis", "title": "Milrem announces THeMIS deliveries to Ukraine", "publisher": "Milrem Robotics", "date": "Current company announcement", "url": "https://milremrobotics.com/milrem-robotics-to-deliver-a-record-number-of-themis-ugvs-to-ukraine-in-collaboration-with-an-eu-member-country/", "type": "Manufacturer / delivery announcement", "supports": "Company-reported delivery of uncrewed ground vehicles for operational support roles; not independent verification of every configuration.", "review": { "source_id": "milrem-ukraine-themis", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "milrem-themis", "kind": "Company-system relationship", "label": "Milrem Robotics → themis-combat-ugv", "path": "/kill-chain-technology-providers/#relationship-milrem-themis" }, { "id": "milrem-robotics", "kind": "Technology provider", "label": "Milrem Robotics", "path": "/kill-chain-technology-providers/#provider-milrem-robotics" } ] }, { "id": "mprest-defense", "title": "mPrest defense solutions", "publisher": "mPrest Systems", "date": "Current capability page", "url": "https://mprest.com/mprest-industries/defense/", "type": "Manufacturer description", "supports": "Company-described command-and-control, sensor fusion, situational awareness, and battle-management software.", "review": { "source_id": "mprest-defense", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "mprest-iron-dome-bmc", "kind": "Company-system relationship", "label": "mPrest Systems → Iron Dome battle-management and weapon-control software", "path": "/kill-chain-technology-providers/#relationship-mprest-iron-dome-bmc" }, { "id": "mprest", "kind": "Technology provider", "label": "mPrest Systems", "path": "/kill-chain-technology-providers/#provider-mprest" } ] }, { "id": "northrop-ibcs", "title": "Integrated Battle Command System", "publisher": "Northrop Grumman", "date": "Current product page", "url": "https://www.northropgrumman.com/what-we-do/missile-defense/integrated-battle-command-system-ibcs", "type": "Manufacturer description", "supports": "Company-described integration of sensors and effectors through a networked air-and-missile-defense battle-command system.", "review": { "source_id": "northrop-ibcs", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "northrop-ibcs", "kind": "Company-system relationship", "label": "Northrop Grumman → Integrated Battle Command System", "path": "/kill-chain-technology-providers/#relationship-northrop-ibcs" }, { "id": "northrop-grumman", "kind": "Technology provider", "label": "Northrop Grumman", "path": "/kill-chain-technology-providers/#provider-northrop-grumman" } ] }, { "id": "army-ibcs-delivery", "title": "U.S. Army receives first complete IBCS delivery", "publisher": "U.S. Army", "date": "Current official announcement", "url": "https://www.army.mil/article/278092/us_army_receives_first_complete_ibcs_delivery", "type": "Official delivery announcement", "supports": "Government-described delivery and program status for IBCS; not a claim about every operational mode or software method.", "review": { "source_id": "army-ibcs-delivery", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "northrop-ibcs", "kind": "Company-system relationship", "label": "Northrop Grumman → Integrated Battle Command System", "path": "/kill-chain-technology-providers/#relationship-northrop-ibcs" }, { "id": "northrop-grumman", "kind": "Technology provider", "label": "Northrop Grumman", "path": "/kill-chain-technology-providers/#provider-northrop-grumman" } ] }, { "id": "palantir-gotham", "title": "Palantir Gotham", "publisher": "Palantir Technologies", "date": "Current platform page", "url": "https://www.palantir.com/platforms/gotham/", "type": "Manufacturer description", "supports": "Company-described data integration, operational workflows, decision support, and mission applications.", "review": { "source_id": "palantir-gotham", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "palantir-maven", "kind": "Company-system relationship", "label": "Palantir Technologies → maven-smart-system", "path": "/kill-chain-technology-providers/#relationship-palantir-maven" }, { "id": "palantir", "kind": "Technology provider", "label": "Palantir Technologies", "path": "/kill-chain-technology-providers/#provider-palantir" } ] }, { "id": "palantir-titan", "title": "Army selects Palantir to deliver TITAN prototypes", "publisher": "Palantir Technologies", "date": "2024", "url": "https://investors.palantir.com/news-details/2024/Army-Selects-Palantir-to-Deliver-TITAN-Next-Generation-Deep-Sensing-Capability-in-Prototype-Maturation-Phase/", "type": "Manufacturer / contract announcement", "supports": "Company announcement of Army prototype selection for AI/ML-enabled deep sensing and decision support; developmental status remains material.", "review": { "source_id": "palantir-titan", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "palantir-titan", "kind": "Company-system relationship", "label": "Palantir Technologies → Tactical Intelligence Targeting Access Node", "path": "/kill-chain-technology-providers/#relationship-palantir-titan" }, { "id": "palantir", "kind": "Technology provider", "label": "Palantir Technologies", "path": "/kill-chain-technology-providers/#provider-palantir" } ] }, { "id": "paloalto-xsiam", "title": "Cortex XSIAM", "publisher": "Palo Alto Networks", "date": "Current product page", "url": "https://www.paloaltonetworks.com/cortex/cortex-xsiam", "type": "Manufacturer description", "supports": "Company-described security operations, analytics, detection, investigation, automation, and response.", "review": { "source_id": "paloalto-xsiam", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "paloalto-xsiam", "kind": "Company-system relationship", "label": "Palo Alto Networks → Cortex XSIAM", "path": "/kill-chain-technology-providers/#relationship-paloalto-xsiam" }, { "id": "palo-alto-networks", "kind": "Technology provider", "label": "Palo Alto Networks", "path": "/kill-chain-technology-providers/#provider-palo-alto-networks" } ] }, { "id": "quantum-vector-ai", "title": "Vector AI uncrewed aircraft", "publisher": "Quantum Systems", "date": "Current product page", "url": "https://quantum-systems.com/vector-ai/", "type": "Manufacturer description", "supports": "Company-described electric vertical-takeoff-and-landing reconnaissance platform, onboard processing, sensing, and mission support.", "review": { "source_id": "quantum-vector-ai", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "quantum-vector-ai", "kind": "Company-system relationship", "label": "Quantum Systems → Vector AI reconnaissance UAS", "path": "/kill-chain-technology-providers/#relationship-quantum-vector-ai" }, { "id": "quantum-systems", "kind": "Technology provider", "label": "Quantum Systems", "path": "/kill-chain-technology-providers/#provider-quantum-systems" } ] }, { "id": "quantum-ukraine-order", "title": "Third Vector order from Ukraine", "publisher": "Quantum Systems", "date": "Current company announcement", "url": "https://quantum-systems.com/news/third-vector-order-from-ukraine/", "type": "Manufacturer / order announcement", "supports": "Company-reported government order and operational-support context; not independent validation of mission outcomes.", "review": { "source_id": "quantum-ukraine-order", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "quantum-vector-ai", "kind": "Company-system relationship", "label": "Quantum Systems → Vector AI reconnaissance UAS", "path": "/kill-chain-technology-providers/#relationship-quantum-vector-ai" }, { "id": "quantum-systems", "kind": "Technology provider", "label": "Quantum Systems", "path": "/kill-chain-technology-providers/#provider-quantum-systems" } ] }, { "id": "rtx-phalanx", "title": "Phalanx close-in weapon system", "publisher": "RTX / Raytheon", "date": "Current product page", "url": "https://www.rtx.com/raytheon/what-we-do/sea/phalanx-close-in-weapon-system", "type": "Manufacturer description", "supports": "Company-described self-contained terminal defense, search, tracking, engagement, and assessment functions.", "review": { "source_id": "rtx-phalanx", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "phalanx-ciws", "kind": "Authority Casebook case", "label": "MK 15 Phalanx Close-In Weapon System", "path": "/authority-casebook.php#casebook-phalanx-ciws" }, { "id": "rtx-phalanx", "kind": "Company-system relationship", "label": "RTX / Raytheon → MK 15 Phalanx CIWS", "path": "/kill-chain-technology-providers/#relationship-rtx-phalanx" }, { "id": "rtx", "kind": "Technology provider", "label": "RTX / Raytheon", "path": "/kill-chain-technology-providers/#provider-rtx" } ] }, { "id": "rtx-searam", "title": "SeaRAM ship-defense system", "publisher": "RTX / Raytheon", "date": "Current product page", "url": "https://www.rtx.com/raytheon/what-we-do/sea/searam-ship-defense-system", "type": "Manufacturer description", "supports": "Company-described self-contained close-in defense combining Phalanx sensing with a guided interceptor launcher.", "review": { "source_id": "rtx-searam", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "rtx-searam", "kind": "Company-system relationship", "label": "RTX / Raytheon → SeaRAM ship-defense system", "path": "/kill-chain-technology-providers/#relationship-rtx-searam" }, { "id": "rtx", "kind": "Technology provider", "label": "RTX / Raytheon", "path": "/kill-chain-technology-providers/#provider-rtx" } ] }, { "id": "rtx-nasams", "title": "NASAMS air-defense system", "publisher": "RTX / Raytheon", "date": "Current product page", "url": "https://www.rtx.com/raytheon/what-we-do/integrated-air-and-missile-defense/nasams", "type": "Manufacturer description", "supports": "Company-described networked air-defense system integrating sensors, command and control, launchers, and effectors.", "review": { "source_id": "rtx-nasams", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "rtx-nasams", "kind": "Company-system relationship", "label": "RTX / Raytheon → NASAMS air-defense system", "path": "/kill-chain-technology-providers/#relationship-rtx-nasams" }, { "id": "rtx", "kind": "Technology provider", "label": "RTX / Raytheon", "path": "/kill-chain-technology-providers/#provider-rtx" } ] }, { "id": "saab-giraffe-c4i", "title": "Giraffe C4I", "publisher": "Saab", "date": "Current product page", "url": "https://www.saab.com/products/giraffe-c4i", "type": "Manufacturer description", "supports": "Company-described radar command-and-control integration, air picture, tracking, and weapon coordination.", "review": { "source_id": "saab-giraffe-c4i", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "saab-giraffe-c4i", "kind": "Company-system relationship", "label": "Saab → Giraffe radar and C4I family", "path": "/kill-chain-technology-providers/#relationship-saab-giraffe-c4i" }, { "id": "saab", "kind": "Technology provider", "label": "Saab", "path": "/kill-chain-technology-providers/#provider-saab" } ] }, { "id": "saab-9air-c4i", "title": "9AIR C4I", "publisher": "Saab", "date": "Current product page", "url": "https://www.saab.com/products/9air-c4i", "type": "Manufacturer description", "supports": "Company-described ground-based air-defense command, control, coordination, and situational awareness.", "review": { "source_id": "saab-9air-c4i", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "saab-9air-c4i", "kind": "Company-system relationship", "label": "Saab → 9AIR C4I", "path": "/kill-chain-technology-providers/#relationship-saab-9air-c4i" }, { "id": "saab", "kind": "Technology provider", "label": "Saab", "path": "/kill-chain-technology-providers/#provider-saab" } ] }, { "id": "shield-vbat", "title": "V-BAT uncrewed aircraft", "publisher": "Shield AI", "date": "Current product page", "url": "https://shield.ai/v-bat/", "type": "Manufacturer description", "supports": "Company-described vertical-takeoff uncrewed aircraft, expeditionary ISR, communications, and autonomy.", "review": { "source_id": "shield-vbat", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "shield-vbat", "kind": "Company-system relationship", "label": "Shield AI → V-BAT uncrewed aircraft", "path": "/kill-chain-technology-providers/#relationship-shield-vbat" }, { "id": "shield-ai", "kind": "Technology provider", "label": "Shield AI", "path": "/kill-chain-technology-providers/#provider-shield-ai" } ] }, { "id": "shield-netherlands-vbat", "title": "Royal Netherlands Navy begins V-BAT operations", "publisher": "Shield AI", "date": "Current company announcement", "url": "https://shield.ai/royal-netherlands-navy-begins-v-bat-operations/", "type": "Manufacturer / operator-use announcement", "supports": "Company-reported naval operational use; mission-specific payloads, authority, and performance remain bounded by public evidence.", "review": { "source_id": "shield-netherlands-vbat", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "shield-vbat", "kind": "Company-system relationship", "label": "Shield AI → V-BAT uncrewed aircraft", "path": "/kill-chain-technology-providers/#relationship-shield-vbat" }, { "id": "shield-ai", "kind": "Technology provider", "label": "Shield AI", "path": "/kill-chain-technology-providers/#provider-shield-ai" } ] }, { "id": "splunk-enterprise-security", "title": "Splunk Enterprise Security", "publisher": "Splunk", "date": "Current product page", "url": "https://www.splunk.com/en_us/products/enterprise-security.html", "type": "Manufacturer description", "supports": "Company-described SIEM, risk-based detection, investigation, orchestration, and response for security operations.", "review": { "source_id": "splunk-enterprise-security", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "splunk-enterprise-security", "kind": "Company-system relationship", "label": "Splunk → Splunk Enterprise Security", "path": "/kill-chain-technology-providers/#relationship-splunk-enterprise-security" }, { "id": "splunk", "kind": "Technology provider", "label": "Splunk", "path": "/kill-chain-technology-providers/#provider-splunk" } ] }, { "id": "thales-tacticos", "title": "TACTICOS naval combat-management system", "publisher": "Thales", "date": "Current product page", "url": "https://www.thalesgroup.com/en/solutions-catalogue/defence/naval/naval-combat-management-system", "type": "Manufacturer description", "supports": "Company-described naval combat-management, sensor integration, track management, command support, and weapon coordination.", "review": { "source_id": "thales-tacticos", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Require independent corroboration before treating a capability or deployment claim as verified.", "Recheck current product configuration, operator use, and human-control arrangement." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "thales-tacticos", "kind": "Company-system relationship", "label": "Thales → TACTICOS naval combat-management system", "path": "/kill-chain-technology-providers/#relationship-thales-tacticos" }, { "id": "thales", "kind": "Technology provider", "label": "Thales", "path": "/kill-chain-technology-providers/#provider-thales" } ] }, { "id": "killwebs-home", "title": "KillWebs.com interactive explorer and public site overview", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/", "type": "First-party sister-site description", "supports": "Public description of the interactive kill-web explorer, observed release characteristics, direct answers, feature routes, synthetic boundary, and sister-site relationship.", "review": { "source_id": "killwebs-home", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "killchains-killwebs-evulgare-ecosystem", "kind": "FAQ answer", "label": "How do KillChains.com, KillWebs.com, and Evulgare.com fit together?", "path": "/faq.php#killchains-killwebs-evulgare-ecosystem" }, { "id": "ecosystem-routing-boundary", "kind": "Glossary term", "label": "Ecosystem routing boundary", "path": "/glossary.php#ecosystem-routing-boundary" }, { "id": "explorer", "kind": "Sister-site statement", "label": "Interactive Kill Web Explorer", "path": "/kill-webs/#killwebs-experience-explorer" } ] }, { "id": "killwebs-definition", "title": "What Is a Kill Web?", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/what-is-a-kill-web.php", "type": "First-party sister-site explanation", "supports": "KillWebs.com working definition of a governed option space, selective reachability, later binding, and the relation between a web and a selected mission chain.", "review": { "source_id": "killwebs-definition", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-killweb-governed-option-space", "kind": "Claim Lineage record", "label": "KillWebs.com describes a kill web as a governed option space.", "path": "/claim-lineage.php#claim-killweb-governed-option-space" }, { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "definition", "kind": "Sister-site statement", "label": "What Is a Kill Web?", "path": "/kill-webs/#killwebs-experience-definition" } ] }, { "id": "killwebs-comparison", "title": "Kill Chain versus Kill Web", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/kill-chain-vs-kill-web.php", "type": "First-party sister-site comparison", "supports": "Structural comparison of selected chains and wider kill-web option spaces, including topology, authority, data, testing, failure response, and the roles of both sister sites.", "review": { "source_id": "killwebs-comparison", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-killweb-governed-option-space", "kind": "Claim Lineage record", "label": "KillWebs.com describes a kill web as a governed option space.", "path": "/claim-lineage.php#claim-killweb-governed-option-space" }, { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "comparison", "kind": "Sister-site statement", "label": "Kill Chain versus Kill Web", "path": "/kill-webs/#killwebs-experience-comparison" } ] }, { "id": "killwebs-ack-lab", "title": "DARPA ACK Capability Marketplace Lab", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/ack-lab.php", "type": "First-party synthetic learning module", "supports": "Public description of a synthetic, non-operational capability-marketplace exercise that separates technical feasibility, constraints, comparison, authority, and execution.", "review": { "source_id": "killwebs-ack-lab", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "ack-lab", "kind": "Sister-site statement", "label": "ACK Capability Marketplace Lab", "path": "/kill-webs/#killwebs-experience-ack-lab" } ] }, { "id": "killwebs-atlas", "title": "Kill Web Evidence and Architecture Atlas", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/atlas.php", "type": "First-party public-safe evidence index", "supports": "Public-safe organization of kill-web concepts, programs, architecture layers, governance questions, evidence roles, research IDs, and public unknowns without tactical locations.", "review": { "source_id": "killwebs-atlas", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "atlas", "kind": "Sister-site statement", "label": "Kill Web Evidence Atlas", "path": "/kill-webs/#killwebs-experience-atlas" } ] }, { "id": "killwebs-human-authority", "title": "Human Authority and Autonomy Lab", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/human-authority.php", "type": "First-party synthetic learning module", "supports": "Public description of a synthetic lab examining evidence, time, authority, intervention, communications, lifecycle decisions, and reconstructable accountability.", "review": { "source_id": "killwebs-human-authority", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "authority", "kind": "Sister-site statement", "label": "Human Authority Lab", "path": "/kill-webs/#killwebs-experience-authority" } ] }, { "id": "killwebs-operating-model", "title": "How Kill Webs Work", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/how-kill-webs-work.php", "type": "First-party sister-site explanation", "supports": "Public description of sensing, correlation, option composition, policy and trust checks, authorization, assessment, and controlled recomposition.", "review": { "source_id": "killwebs-operating-model", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "operating-model", "kind": "Sister-site statement", "label": "How Kill Webs Work", "path": "/kill-webs/#killwebs-experience-operating-model" } ] }, { "id": "killwebs-scenarios", "title": "Synthetic Kill Web Resilience Scenarios", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/scenarios.php", "type": "First-party synthetic exercise catalog", "supports": "Seven deterministic public-safe scenarios covering relay loss, stale evidence, unavailable authority, timing integrity, common dependencies, and rejected provenance.", "review": { "source_id": "killwebs-scenarios", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "scenarios", "kind": "Sister-site statement", "label": "Resilience Scenarios", "path": "/kill-webs/#killwebs-experience-scenarios" } ] }, { "id": "killwebs-architecture", "title": "Military Kill Web Technical Architecture", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/architecture.php", "type": "First-party sister-site architecture explanation", "supports": "Public explanation of capability semantics, data fabrics, transport, cloud-edge placement, identity, trust, orchestration, interfaces, and graceful degradation.", "review": { "source_id": "killwebs-architecture", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "architecture", "kind": "Sister-site statement", "label": "Technical Architecture", "path": "/kill-webs/#killwebs-experience-architecture" } ] }, { "id": "killwebs-security", "title": "Kill Web Cybersecurity and Resilience", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/security.php", "type": "First-party defensive architecture explanation", "supports": "Public treatment of integrity, timing, identity, data poisoning, supply-chain, electromagnetic, and common-mode risks without operational attack procedures.", "review": { "source_id": "killwebs-security", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "security", "kind": "Sister-site statement", "label": "Security and Vulnerabilities", "path": "/kill-webs/#killwebs-experience-security" } ] }, { "id": "killwebs-methodology", "title": "KillWebs.com Methodology and Evidence Policy", "publisher": "KillWebs.com", "date": "2026-08-01 review", "url": "https://killwebs.com/methodology.php", "type": "First-party editorial methodology", "supports": "Authority order, evidence hierarchy, report promotion, synthetic model, safety boundary, correction process, and explicit public unknowns.", "review": { "source_id": "killwebs-methodology", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "killwebs", "kind": "Ecosystem identity", "label": "KillWebs.com", "path": "/ecosystem.php#killwebs-role" }, { "id": "methodology", "kind": "Sister-site statement", "label": "Methodology and Evidence Policy", "path": "/kill-webs/#killwebs-experience-methodology" } ] }, { "id": "precobs-bka-2015", "title": "Predictive Policing: PRECOBS position paper", "publisher": "German Federal Criminal Police Office (BKA) forum material", "date": "2015", "url": "https://www.bka.de/SharedDocs/Downloads/DE/Publikationen/ForumKI/ForumKI2015/kiforum2015EggerPositionspapier.pdf?__blob=publicationFile&v=1", "type": "Official police conference paper", "supports": "Historical description of PRECOBS as a near-repeat, place-based burglary forecasting approach and its analyst-mediated operational workflow. It does not establish current deployment or independent crime-reduction effects.", "review": { "source_id": "precobs-bka-2015", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "place-based-forecasting", "kind": "Glossary term", "label": "Place-based forecasting", "path": "/glossary.php#place-based-forecasting" }, { "id": "precobs-bavaria", "kind": "Predictive Enforcement program", "label": "PRECOBS", "path": "/predictive-enforcement.php#program-precobs-bavaria" } ] }, { "id": "precobs-bavaria-2019", "title": "Sicherheitsbericht 2019: Polizeipräsidium Mittelfranken", "publisher": "Bavarian Police", "date": "2019", "url": "https://www.polizei.bayern.de/mam/pp-mittelfranken/sonstige/210827_ppmfr_sicherheitsbericht_2019.pdf", "type": "Official police annual report", "supports": "Historical official evidence that PRECOBS remained in use in the Nuremberg policing area in 2019. It does not establish the 2026 deployment footprint.", "review": { "source_id": "precobs-bavaria-2019", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "precobs-bavaria", "kind": "Predictive Enforcement program", "label": "PRECOBS", "path": "/predictive-enforcement.php#program-precobs-bavaria" } ] }, { "id": "cas-algorithm-register-2025", "title": "Crime Anticipation System (CAS)", "publisher": "Dutch Government Algorithm Register", "date": "2025-12 status", "url": "https://algoritmes.overheid.nl/en/algoritme/oorg10264/81228922/crime-anticipation-system-cas", "type": "Official algorithm-register record", "supports": "CAS purpose, national grid-cell design, twelve-week data window, human use of outputs, operational dates, and out-of-use status from December 2025. It does not establish a causal crime-reduction effect.", "review": { "source_id": "cas-algorithm-register-2025", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "crime-anticipation-system", "kind": "Authority Casebook case", "label": "Crime Anticipation System", "path": "/authority-casebook.php#casebook-crime-anticipation-system" }, { "id": "claim-cas-risk-map-inference", "kind": "Claim Lineage record", "label": "CAS transformed recent records into place-based risk maps.", "path": "/claim-lineage.php#claim-cas-risk-map-inference" }, { "id": "claim-cas-input-observation", "kind": "Claim Lineage record", "label": "CAS used historical police incident and contextual records as inputs.", "path": "/claim-lineage.php#claim-cas-input-observation" }, { "id": "claim-cas-discontinuation", "kind": "Claim Lineage record", "label": "Crime Anticipation System (CAS) was discontinued in December 2025.", "path": "/claim-lineage.php#claim-cas-discontinuation" }, { "id": "claim-cas-deployment-recommendation", "kind": "Claim Lineage record", "label": "Human analysts interpreted CAS outputs before deployment recommendations.", "path": "/claim-lineage.php#claim-cas-deployment-recommendation" }, { "id": "place-versus-person-prediction", "kind": "FAQ answer", "label": "How does place-based forecasting differ from person-based prediction?", "path": "/faq.php#place-versus-person-prediction" }, { "id": "claim-lineage", "kind": "FAQ answer", "label": "What is claim lineage?", "path": "/faq.php#claim-lineage" }, { "id": "institutional-authority-casebook", "kind": "FAQ answer", "label": "What is the Institutional Authority Casebook?", "path": "/faq.php#institutional-authority-casebook" }, { "id": "claim-transformation", "kind": "FAQ answer", "label": "Why does the site distinguish a source statement from an inference or recommendation?", "path": "/faq.php#claim-transformation" }, { "id": "claim-lineage", "kind": "Glossary term", "label": "Claim lineage", "path": "/glossary.php#claim-lineage" }, { "id": "correction-owner", "kind": "Glossary term", "label": "Correction owner", "path": "/glossary.php#correction-owner" }, { "id": "authority-casebook", "kind": "Glossary term", "label": "Institutional Authority Casebook", "path": "/glossary.php#authority-casebook" }, { "id": "place-based-forecasting", "kind": "Glossary term", "label": "Place-based forecasting", "path": "/glossary.php#place-based-forecasting" }, { "id": "transformation-statement", "kind": "Glossary term", "label": "Transformation statement", "path": "/glossary.php#transformation-statement" }, { "id": "cas-netherlands", "kind": "Predictive Enforcement program", "label": "Crime Anticipation System", "path": "/predictive-enforcement.php#program-cas-netherlands" } ] }, { "id": "cas-police-woo-2021", "title": "Crime Anticipation System public-information decision", "publisher": "National Police of the Netherlands", "date": "2021-07-27", "url": "https://www.politie.nl/binaries/content/assets/politie/wet-open-overheid/woo-documenten/11-landelijke-eenheid/2021/8456---crime-anticipation-system/7a91ad36-90cf-4be0-a330-d8b64e056019.pdf", "type": "Official police disclosure record", "supports": "Public-record handling and documented governance questions concerning CAS data, evaluation, procedures, retention, and impact assessments. It does not by itself prove which requested records existed or how every local team used CAS.", "review": { "source_id": "cas-police-woo-2021", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "crime-anticipation-system", "kind": "Authority Casebook case", "label": "Crime Anticipation System", "path": "/authority-casebook.php#casebook-crime-anticipation-system" }, { "id": "claim-cas-deployment-recommendation", "kind": "Claim Lineage record", "label": "Human analysts interpreted CAS outputs before deployment recommendations.", "path": "/claim-lineage.php#claim-cas-deployment-recommendation" }, { "id": "cas-netherlands", "kind": "Predictive Enforcement program", "label": "Crime Anticipation System", "path": "/predictive-enforcement.php#program-cas-netherlands" } ] }, { "id": "chicago-oig-ssl-2020", "title": "Advisory Concerning the Chicago Police Department’s Predictive Risk Models", "publisher": "City of Chicago Office of Inspector General", "date": "2020", "url": "https://igchicago.org/publications/advisory-concerning-the-chicago-police-departments-predictive-risk-models/", "type": "Municipal inspector-general review", "supports": "SSL/CVRM purpose, operational and governance weaknesses, evaluation limitations, and CPD decommissioning of the Party to Violence models on November 1, 2019.", "review": { "source_id": "chicago-oig-ssl-2020", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "place-versus-person-prediction", "kind": "FAQ answer", "label": "How does place-based forecasting differ from person-based prediction?", "path": "/faq.php#place-versus-person-prediction" }, { "id": "person-based-prediction", "kind": "Glossary term", "label": "Person-based prediction", "path": "/glossary.php#person-based-prediction" }, { "id": "chicago-ssl-cvrm", "kind": "Predictive Enforcement program", "label": "Strategic Subject List and Crime and Victimization Risk Model", "path": "/predictive-enforcement.php#program-chicago-ssl-cvrm" } ] }, { "id": "hart-cambridge-2018", "title": "Helping police make custody decisions using artificial intelligence", "publisher": "University of Cambridge", "date": "2018-02-26", "url": "https://www.cam.ac.uk/research/features/helping-police-make-custody-decisions-using-artificial-intelligence", "type": "University research and program description", "supports": "Development of HART with Durham Constabulary, its training data, random-forest classification, risk categories, and advisory use in custody and Checkpoint eligibility. It does not establish current use in 2026.", "review": { "source_id": "hart-cambridge-2018", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "person-based-prediction", "kind": "Glossary term", "label": "Person-based prediction", "path": "/glossary.php#person-based-prediction" }, { "id": "durham-hart", "kind": "Predictive Enforcement program", "label": "Harm Assessment Risk Tool", "path": "/predictive-enforcement.php#program-durham-hart" } ] }, { "id": "hart-uk-public-standards-2020", "title": "Review into bias in algorithmic decision-making", "publisher": "UK Centre for Data Ethics and Innovation", "date": "2020-11-27", "url": "https://www.gov.uk/government/publications/cdei-publishes-review-into-bias-in-algorithmic-decision-making/main-report-cdei-review-into-bias-in-algorithmic-decision-making", "type": "Official UK government review", "supports": "Public-sector description of HART as a supervised machine-learning tool used by Durham Police and discussion of bias, governance, and human decision-making. It does not establish current status or complete subgroup performance.", "review": { "source_id": "hart-uk-public-standards-2020", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "durham-hart", "kind": "Predictive Enforcement program", "label": "Harm Assessment Risk Tool", "path": "/predictive-enforcement.php#program-durham-hart" } ] }, { "id": "hart-probation-review-2025", "title": "Risk of Serious Violence of those already known to the Probation Service", "publisher": "UK Government", "date": "2025", "url": "https://assets.publishing.service.gov.uk/media/693be762adb5707d9f33d68f/risk-serious-violence-probation-service.pdf", "type": "Official research review", "supports": "Retrospective public account that HART was used from 2016 through 2021. It does not establish whether HART remained operational after that period.", "review": { "source_id": "hart-probation-review-2025", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [] }, { "id": "met-gvm-archive", "title": "Gangs Violence Matrix", "publisher": "Metropolitan Police Service", "date": "historical page reviewed 2026-08-02", "url": "https://www.met.police.uk/police-forces/metropolitan-police/areas/about-us/about-the-met/gangs-violence-matrix/", "type": "Official police historical program page", "supports": "Official Met account of the former Gangs Violence Matrix and its decommissioning. It does not independently validate the Matrix’s selection, effects, or fairness.", "review": { "source_id": "met-gvm-archive", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "superseded", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": "met-vha-current", "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The former Gangs Violence Matrix page is retained for historical program evidence. The Violence Harm Assessment source owns the current successor description.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-gvm-vha-supersession", "kind": "Claim Lineage record", "label": "The former Gangs Violence Matrix is historical; VHA owns the current successor description.", "path": "/claim-lineage.php#claim-gvm-vha-supersession" }, { "id": "accepted-correction-preserves-history", "kind": "FAQ answer", "label": "Does KillChains.com erase an earlier statement after accepting a correction?", "path": "/faq.php#accepted-correction-preserves-history" }, { "id": "supersession-preserves-history", "kind": "FAQ answer", "label": "What happens when a source, program, or claim is superseded?", "path": "/faq.php#supersession-preserves-history" }, { "id": "historical-preservation-rule", "kind": "Glossary term", "label": "Historical preservation rule", "path": "/glossary.php#historical-preservation-rule" }, { "id": "supersession", "kind": "Glossary term", "label": "Supersession", "path": "/glossary.php#supersession" }, { "id": "london-gvm-vha", "kind": "Predictive Enforcement program", "label": "Gangs Violence Matrix and Violence Harm Assessment", "path": "/predictive-enforcement.php#program-london-gvm-vha" } ] }, { "id": "ico-gvm-2018", "title": "Metropolitan Police Gangs Matrix", "publisher": "UK Information Commissioner’s Office", "date": "2018 enforcement context; page reviewed 2026-08-02", "url": "https://ico.org.uk/for-the-public/ico-40/metropolitan-police-gangs-matrix/", "type": "Independent regulator record", "supports": "Regulatory findings concerning the former Matrix’s governance, accuracy, retention, differentiation, and information sharing. It does not characterize every individual entry or later VHA practice.", "review": { "source_id": "ico-gvm-2018", "last_reviewed_on": "2026-08-07", "next_review_due_on": null, "review_interval_days": null, "review_state": "historical", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": true, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "Retained for a bounded historical proposition. The record does not establish current operation, configuration, or policy.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Use for chronology only unless a current source separately establishes present status." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "london-gvm-vha", "kind": "Predictive Enforcement program", "label": "Gangs Violence Matrix and Violence Harm Assessment", "path": "/predictive-enforcement.php#program-london-gvm-vha" } ] }, { "id": "met-vha-current", "title": "Violence Harm Assessment", "publisher": "Metropolitan Police Service", "date": "current page reviewed 2026-08-02", "url": "https://www.met.police.uk/police-forces/metropolitan-police/areas/about-us/about-the-met/violence-harm-assessment/", "type": "Official police program and governance page", "supports": "VHA purpose, inclusion and scoring approach, published DPIA/EIA/SOP, annual MOPAC review, access/removal information, and current operational status. It does not establish causal effectiveness.", "review": { "source_id": "met-vha-current", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-gvm-vha-supersession", "kind": "Claim Lineage record", "label": "The former Gangs Violence Matrix is historical; VHA owns the current successor description.", "path": "/claim-lineage.php#claim-gvm-vha-supersession" }, { "id": "accepted-correction-preserves-history", "kind": "FAQ answer", "label": "Does KillChains.com erase an earlier statement after accepting a correction?", "path": "/faq.php#accepted-correction-preserves-history" }, { "id": "claim-contestability", "kind": "FAQ answer", "label": "How can a reader challenge or correct a KillChains.com claim?", "path": "/faq.php#claim-contestability" }, { "id": "supersession-preserves-history", "kind": "FAQ answer", "label": "What happens when a source, program, or claim is superseded?", "path": "/faq.php#supersession-preserves-history" }, { "id": "contestability", "kind": "Glossary term", "label": "Contestability", "path": "/glossary.php#contestability" }, { "id": "historical-preservation-rule", "kind": "Glossary term", "label": "Historical preservation rule", "path": "/glossary.php#historical-preservation-rule" }, { "id": "supersession", "kind": "Glossary term", "label": "Supersession", "path": "/glossary.php#supersession" }, { "id": "london-gvm-vha", "kind": "Predictive Enforcement program", "label": "Gangs Violence Matrix and Violence Harm Assessment", "path": "/predictive-enforcement.php#program-london-gvm-vha" } ] }, { "id": "met-vha-july-2026", "title": "Violence Harm Assessment figures – Headlines 03/07/2026", "publisher": "Metropolitan Police Service", "date": "2026-07-03", "url": "https://www.met.police.uk/SysSiteAssets/media/downloads/met/about-us/violence-harm-index/quarterly-reports/vha-data-july-2026.pdf", "type": "Official police transparency report", "supports": "Current VHA population and demographic figures as of July 3, 2026, including 1,632 people meeting criteria. It does not establish that inclusion is accurate or effective for every person.", "review": { "source_id": "met-vha-july-2026", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-gvm-vha-supersession", "kind": "Claim Lineage record", "label": "The former Gangs Violence Matrix is historical; VHA owns the current successor description.", "path": "/claim-lineage.php#claim-gvm-vha-supersession" }, { "id": "london-gvm-vha", "kind": "Predictive Enforcement program", "label": "Gangs Violence Matrix and Violence Harm Assessment", "path": "/predictive-enforcement.php#program-london-gvm-vha" } ] }, { "id": "tsa-secure-flight-pia-2023", "title": "DHS/TSA/PIA-018(f) Secure Flight", "publisher": "U.S. Department of Homeland Security", "date": "2023 update", "url": "https://www.dhs.gov/publication/dhstsapia-018f-secure-flight", "type": "Official privacy impact assessment", "supports": "Secure Flight’s identity data, prescreening workflow, system purpose, records, sharing, and privacy controls. It does not disclose all matching rules or aggregate error rates.", "review": { "source_id": "tsa-secure-flight-pia-2023", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "secure-flight", "kind": "Authority Casebook case", "label": "Secure Flight", "path": "/authority-casebook.php#casebook-secure-flight" }, { "id": "operational-delegation-versus-legal-authority", "kind": "FAQ answer", "label": "Does operational delegation give a machine legal authority?", "path": "/faq.php#operational-delegation-versus-legal-authority" }, { "id": "identity-resolution-versus-prediction", "kind": "FAQ answer", "label": "Is identity resolution the same as predicting future conduct?", "path": "/faq.php#identity-resolution-versus-prediction" }, { "id": "institutional-authority-casebook", "kind": "FAQ answer", "label": "What is the Institutional Authority Casebook?", "path": "/faq.php#institutional-authority-casebook" }, { "id": "identity-resolution", "kind": "Glossary term", "label": "Identity resolution", "path": "/glossary.php#identity-resolution" }, { "id": "operational-delegation", "kind": "Glossary term", "label": "Operational delegation", "path": "/glossary.php#operational-delegation" }, { "id": "tsa-secure-flight", "kind": "Predictive Enforcement program", "label": "Secure Flight", "path": "/predictive-enforcement.php#program-tsa-secure-flight" } ] }, { "id": "tsa-security-screening-current", "title": "Security Screening", "publisher": "Transportation Security Administration", "date": "current page reviewed 2026-08-02", "url": "https://www.tsa.gov/travel/security-screening", "type": "Official current program information", "supports": "Current TSA passenger-screening process and public travel guidance. It does not independently validate Secure Flight matching accuracy or disclose controlled criteria.", "review": { "source_id": "tsa-security-screening-current", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "secure-flight", "kind": "Authority Casebook case", "label": "Secure Flight", "path": "/authority-casebook.php#casebook-secure-flight" }, { "id": "tsa-secure-flight", "kind": "Predictive Enforcement program", "label": "Secure Flight", "path": "/predictive-enforcement.php#program-tsa-secure-flight" } ] }, { "id": "fbi-watchlisting-overview-2024", "title": "Terrorist Watchlisting Transparency Document", "publisher": "Federal Bureau of Investigation", "date": "2024-04", "url": "https://www.fbi.gov/file-repository/counterterrorism/terrorist-watchlisting-transparency-document-april-2024-050224.pdf/view", "type": "Official federal transparency document", "supports": "Public watchlisting lifecycle, nomination and identity-resolution roles, screening uses, and the distinction between a watchlist record and an agency’s downstream legal action.", "review": { "source_id": "fbi-watchlisting-overview-2024", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "terrorist-watchlisting-lifecycle", "kind": "Authority Casebook case", "label": "U.S. terrorism-watchlisting lifecycle", "path": "/authority-casebook.php#casebook-terrorist-watchlisting-lifecycle" }, { "id": "claim-watchlist-not-warrant", "kind": "Claim Lineage record", "label": "A U.S. watchlist record is not itself an arrest warrant or criminal finding.", "path": "/claim-lineage.php#claim-watchlist-not-warrant" }, { "id": "operational-delegation-versus-legal-authority", "kind": "FAQ answer", "label": "Does operational delegation give a machine legal authority?", "path": "/faq.php#operational-delegation-versus-legal-authority" }, { "id": "identity-resolution-versus-prediction", "kind": "FAQ answer", "label": "Is identity resolution the same as predicting future conduct?", "path": "/faq.php#identity-resolution-versus-prediction" }, { "id": "claim-transformation", "kind": "FAQ answer", "label": "Why does the site distinguish a source statement from an inference or recommendation?", "path": "/faq.php#claim-transformation" }, { "id": "identity-resolution", "kind": "Glossary term", "label": "Identity resolution", "path": "/glossary.php#identity-resolution" }, { "id": "watchlisting", "kind": "Glossary term", "label": "Watchlisting", "path": "/glossary.php#watchlisting" }, { "id": "us-tsds-watchlisting", "kind": "Predictive Enforcement program", "label": "Terrorist Screening Dataset and watchlisting lifecycle", "path": "/predictive-enforcement.php#program-us-tsds-watchlisting" } ] }, { "id": "fbi-tsc-renaming-2025", "title": "The Terrorist Screening Center Changes Name to the Threat Screening Center", "publisher": "Federal Bureau of Investigation", "date": "2025-03-19", "url": "https://www.fbi.gov/news/press-releases/the-terrorist-screening-center-changes-name-to-the-threat-screening-center", "type": "Official agency announcement", "supports": "The March 2025 renaming of the Terrorist Screening Center to the Threat Screening Center and the publicly described expansion of its mission. It does not disclose all dataset criteria or operating rules.", "review": { "source_id": "fbi-tsc-renaming-2025", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "us-tsds-watchlisting", "kind": "Predictive Enforcement program", "label": "Terrorist Screening Dataset and watchlisting lifecycle", "path": "/predictive-enforcement.php#program-us-tsds-watchlisting" } ] }, { "id": "pclob-watchlist-2025", "title": "Terrorist Watchlist Report and Recommendations", "publisher": "Privacy and Civil Liberties Oversight Board", "date": "2025-01-23", "url": "https://documents.pclob.gov/prod/Documents/OversightReport/b2f9ecff-99fc-48f9-a559-b486391b0e0a/PCLOB%20Terrorist%20Watchlist%20Report%20Unclassified.pdf", "type": "Independent federal oversight report", "supports": "Watchlist scale, review and redress processes, accuracy and re-review concerns, and recommendations. Aggregate counts do not constitute a false-positive rate.", "review": { "source_id": "pclob-watchlist-2025", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-08-07", "review_interval_days": 365, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "terrorist-watchlisting-lifecycle", "kind": "Authority Casebook case", "label": "U.S. terrorism-watchlisting lifecycle", "path": "/authority-casebook.php#casebook-terrorist-watchlisting-lifecycle" }, { "id": "claim-watchlist-not-warrant", "kind": "Claim Lineage record", "label": "A U.S. watchlist record is not itself an arrest warrant or criminal finding.", "path": "/claim-lineage.php#claim-watchlist-not-warrant" }, { "id": "claim-contestability", "kind": "FAQ answer", "label": "How can a reader challenge or correct a KillChains.com claim?", "path": "/faq.php#claim-contestability" }, { "id": "contestability", "kind": "Glossary term", "label": "Contestability", "path": "/glossary.php#contestability" }, { "id": "correction-owner", "kind": "Glossary term", "label": "Correction owner", "path": "/glossary.php#correction-owner" }, { "id": "redress", "kind": "Glossary term", "label": "Redress", "path": "/glossary.php#redress" }, { "id": "watchlisting", "kind": "Glossary term", "label": "Watchlisting", "path": "/glossary.php#watchlisting" }, { "id": "us-tsds-watchlisting", "kind": "Predictive Enforcement program", "label": "Terrorist Screening Dataset and watchlisting lifecycle", "path": "/predictive-enforcement.php#program-us-tsds-watchlisting" } ] }, { "id": "fbi-btac-current", "title": "Behavioral Analysis and Threat Assessment", "publisher": "Federal Bureau of Investigation", "date": "current page reviewed 2026-08-02", "url": "https://www.fbi.gov/how-we-investigate/behavioral-analysis", "type": "Official current program description", "supports": "Current FBI BTAC and TATM operational support, multidisciplinary staffing, training, research, and behavior-based threat-assessment role. It does not establish a national AI future-danger score.", "review": { "source_id": "fbi-btac-current", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-btac-structured-judgment", "kind": "Claim Lineage record", "label": "Federal behavioral threat assessment is publicly described as case-specific professional judgment, not a national AI danger score.", "path": "/claim-lineage.php#claim-btac-structured-judgment" }, { "id": "behavioral-threat-assessment-versus-precrime", "kind": "FAQ answer", "label": "Is behavioral threat assessment the same as pre-crime scoring?", "path": "/faq.php#behavioral-threat-assessment-versus-precrime" }, { "id": "behavioral-threat-assessment", "kind": "Glossary term", "label": "Behavioral threat assessment", "path": "/glossary.php#behavioral-threat-assessment" }, { "id": "federal-btam", "kind": "Predictive Enforcement program", "label": "Federal behavioral threat assessment and management", "path": "/predictive-enforcement.php#program-federal-btam" } ] }, { "id": "secret-service-btau-guide-2024", "title": "Behavioral Threat Assessment Units: A Guide for State and Local Law Enforcement to Prevent Targeted Violence", "publisher": "U.S. Secret Service National Threat Assessment Center", "date": "2024-10", "url": "https://www.secretservice.gov/sites/default/files/reports/2024-10/Behavioral-Threat-Assessment-Units-A-Guide-for-State-and-Local-Law-Enforcement-to-Prevent-Targeted-Violence.pdf", "type": "Official federal guidance", "supports": "Multidisciplinary unit design, case-specific behavioral threat assessment, management, and continuing prevention practice. It does not establish that one indicator or profile predicts attack.", "review": { "source_id": "secret-service-btau-guide-2024", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2027-02-03", "review_interval_days": 180, "review_state": "current", "link_state": "not_checked_in_release", "link_checked_on": null, "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source.", "Check for amendment, successor program, changed terminology, or superseding policy." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "claim-btac-structured-judgment", "kind": "Claim Lineage record", "label": "Federal behavioral threat assessment is publicly described as case-specific professional judgment, not a national AI danger score.", "path": "/claim-lineage.php#claim-btac-structured-judgment" }, { "id": "behavioral-threat-assessment-versus-precrime", "kind": "FAQ answer", "label": "Is behavioral threat assessment the same as pre-crime scoring?", "path": "/faq.php#behavioral-threat-assessment-versus-precrime" }, { "id": "behavioral-threat-assessment", "kind": "Glossary term", "label": "Behavioral threat assessment", "path": "/glossary.php#behavioral-threat-assessment" }, { "id": "federal-btam", "kind": "Predictive Enforcement program", "label": "Federal behavioral threat assessment and management", "path": "/predictive-enforcement.php#program-federal-btam" } ] }, { "id": "evulgare-home", "title": "Evulgare — Make the Machine Answerable", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/", "type": "First-party live company identity and platform-scope source", "supports": "Evulgare identity, live domain, accountability principles, evidence-layer framing, and its public description of the KillChains–KillWebs–Evulgare ecosystem. It does not independently verify a customer deployment, certification, legal conclusion, or operational performance.", "review": { "source_id": "evulgare-home", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "can-machine-assume-responsibility", "kind": "FAQ answer", "label": "Can a machine take responsibility so a human does not have to?", "path": "/faq.php#can-machine-assume-responsibility" }, { "id": "killchains-killwebs-evulgare-ecosystem", "kind": "FAQ answer", "label": "How do KillChains.com, KillWebs.com, and Evulgare.com fit together?", "path": "/faq.php#killchains-killwebs-evulgare-ecosystem" }, { "id": "what-evulgare-preserves", "kind": "FAQ answer", "label": "What should Evulgare preserve around a consequential machine decision?", "path": "/faq.php#what-evulgare-preserves" }, { "id": "when-to-use-evulgare", "kind": "FAQ answer", "label": "When should a reader continue from KillChains.com to Evulgare.com?", "path": "/faq.php#when-to-use-evulgare" }, { "id": "human-click-liability-transfer", "kind": "FAQ answer", "label": "Why is a human click not automatically a liability transfer?", "path": "/faq.php#human-click-liability-transfer" }, { "id": "causal-reconstruction", "kind": "Glossary term", "label": "Causal reconstruction", "path": "/glossary.php#causal-reconstruction" }, { "id": "ecosystem-routing-boundary", "kind": "Glossary term", "label": "Ecosystem routing boundary", "path": "/glossary.php#ecosystem-routing-boundary" }, { "id": "human-click-liability-transfer", "kind": "Glossary term", "label": "Human click as liability transfer", "path": "/glossary.php#human-click-liability-transfer" }, { "id": "machine-answerability", "kind": "Glossary term", "label": "Machine answerability", "path": "/glossary.php#machine-answerability" }, { "id": "machine-evidentiary-burden", "kind": "Glossary term", "label": "Machine evidentiary burden", "path": "/glossary.php#machine-evidentiary-burden" }, { "id": "operational-evidence-layer", "kind": "Glossary term", "label": "Operational evidence layer", "path": "/glossary.php#operational-evidence-layer" }, { "id": "technical-answerability", "kind": "Glossary term", "label": "Technical answerability", "path": "/glossary.php#technical-answerability" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" } ] }, { "id": "evulgare-platform", "title": "The Evidence Layer for Autonomous Systems", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/", "type": "First-party live platform overview", "supports": "Evulgare’s public platform model connecting evidence, observation, transformation, model, uncertainty, interpretation, policy, authority, interface, human judgment, decision, outcome, provenance, and assurance. It does not independently establish production integration or performance.", "review": { "source_id": "evulgare-platform", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "can-machine-assume-responsibility", "kind": "FAQ answer", "label": "Can a machine take responsibility so a human does not have to?", "path": "/faq.php#can-machine-assume-responsibility" }, { "id": "concept-to-production-handoff", "kind": "FAQ answer", "label": "How does a KillChains.com concept become a production-accountability requirement?", "path": "/faq.php#concept-to-production-handoff" }, { "id": "what-evulgare-preserves", "kind": "FAQ answer", "label": "What should Evulgare preserve around a consequential machine decision?", "path": "/faq.php#what-evulgare-preserves" }, { "id": "why-normal-log-insufficient", "kind": "FAQ answer", "label": "Why is an ordinary event log not enough for an autonomous-system failure?", "path": "/faq.php#why-normal-log-insufficient" }, { "id": "machine-evidentiary-burden", "kind": "Glossary term", "label": "Machine evidentiary burden", "path": "/glossary.php#machine-evidentiary-burden" }, { "id": "production-accountability-handoff", "kind": "Glossary term", "label": "Production-accountability handoff", "path": "/glossary.php#production-accountability-handoff" }, { "id": "technical-answerability", "kind": "Glossary term", "label": "Technical answerability", "path": "/glossary.php#technical-answerability" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" } ] }, { "id": "evulgare-accountability", "title": "Evulgare Accountability", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/accountability", "type": "First-party live product-area description", "supports": "The public product-area boundary for technical and causal attribution across evidence, model, software, policy, authority, interface, human review, and organizational controls. It explicitly does not claim to decide legal liability.", "review": { "source_id": "evulgare-accountability", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E10", "kind": "Accountability Handoff evidence requirement", "label": "Action log without causal structure", "path": "/accountability-handoff.php#evidence-AH-E10" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "proxy-responsibility", "kind": "Concept Matrix production handoff", "label": "Proxy responsibility", "path": "/concept-matrix.php#concept-proxy-responsibility" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "validation-exception-acknowledgment-versus-ownership", "kind": "FAQ answer", "label": "Does acknowledging a validation exception mean an institution owns it?", "path": "/faq.php#validation-exception-acknowledgment-versus-ownership" }, { "id": "alert-delivery-review-verification", "kind": "FAQ answer", "label": "Does alert delivery prove that a regression was reviewed and verified?", "path": "/faq.php#alert-delivery-review-verification" }, { "id": "dispute-closure-versus-certainty", "kind": "FAQ answer", "label": "Does closing a dispute establish certainty, legal responsibility, or operational release?", "path": "/faq.php#dispute-closure-versus-certainty" }, { "id": "many-hands-no-blame-score", "kind": "FAQ answer", "label": "Does mapping many institutional hands assign blame or legal liability?", "path": "/faq.php#many-hands-no-blame-score" }, { "id": "reopened-audit-versus-erased-history", "kind": "FAQ answer", "label": "Does reopening and revalidating an audit erase the earlier invalidation or assign responsibility?", "path": "/faq.php#reopened-audit-versus-erased-history" }, { "id": "causal-contribution-not-blame", "kind": "FAQ answer", "label": "Does the causal-contribution map assign blame or legal liability?", "path": "/faq.php#causal-contribution-not-blame" }, { "id": "alert-receipt-versus-competent-review", "kind": "FAQ answer", "label": "Is acknowledging an alert the same as competent review and independent verification?", "path": "/faq.php#alert-receipt-versus-competent-review" }, { "id": "no-authority-to-infer", "kind": "FAQ answer", "label": "What does “no authority to infer” mean?", "path": "/faq.php#no-authority-to-infer" }, { "id": "corrective-action-effectiveness-audit", "kind": "FAQ answer", "label": "What is a corrective-action effectiveness audit?", "path": "/faq.php#corrective-action-effectiveness-audit" }, { "id": "machine-answerability-dispute-record", "kind": "FAQ answer", "label": "What is a machine-answerability dispute record?", "path": "/faq.php#machine-answerability-dispute-record" }, { "id": "evidence-contract", "kind": "FAQ answer", "label": "What is a machine-answerability evidence contract?", "path": "/faq.php#evidence-contract" }, { "id": "corrective-action-monitoring-regression-reopening", "kind": "FAQ answer", "label": "What is corrective-action monitoring, regression, and reopening?", "path": "/faq.php#corrective-action-monitoring-regression-reopening" }, { "id": "evidence-gap-remediation", "kind": "FAQ answer", "label": "What is machine-answerability evidence-gap remediation?", "path": "/faq.php#evidence-gap-remediation" }, { "id": "machine-answerability-replay", "kind": "FAQ answer", "label": "What is the Machine Answerability Replay?", "path": "/faq.php#machine-answerability-replay" }, { "id": "why-normal-log-insufficient", "kind": "FAQ answer", "label": "Why is an ordinary event log not enough for an autonomous-system failure?", "path": "/faq.php#why-normal-log-insufficient" }, { "id": "evidence-request-versus-production", "kind": "FAQ answer", "label": "Why is requesting evidence different from producing it?", "path": "/faq.php#evidence-request-versus-production" }, { "id": "alert-integrity", "kind": "Glossary term", "label": "Alert integrity", "path": "/glossary.php#alert-integrity" }, { "id": "causal-reconstruction", "kind": "Glossary term", "label": "Causal reconstruction", "path": "/glossary.php#causal-reconstruction" }, { "id": "causal-contribution-map", "kind": "Glossary term", "label": "Causal-contribution map", "path": "/glossary.php#causal-contribution-map" }, { "id": "ceremonial-alert-acknowledgment", "kind": "Glossary term", "label": "Ceremonial alert acknowledgment", "path": "/glossary.php#ceremonial-alert-acknowledgment" }, { "id": "closure-with-residual-unknowns", "kind": "Glossary term", "label": "Closure with residual unknowns", "path": "/glossary.php#closure-with-residual-unknowns" }, { "id": "corrective-action-effectiveness-audit", "kind": "Glossary term", "label": "Corrective-action effectiveness audit", "path": "/glossary.php#corrective-action-effectiveness-audit" }, { "id": "evidence-request-versus-production", "kind": "Glossary term", "label": "Evidence request versus production", "path": "/glossary.php#evidence-request-versus-production" }, { "id": "evidence-gap-remediation", "kind": "Glossary term", "label": "Evidence-gap remediation", "path": "/glossary.php#evidence-gap-remediation" }, { "id": "answerability-remediation", "kind": "Glossary term", "label": "Machine answerability remediation", "path": "/glossary.php#answerability-remediation" }, { "id": "answerability-replay", "kind": "Glossary term", "label": "Machine answerability replay", "path": "/glossary.php#answerability-replay" }, { "id": "machine-answerability-dispute-record", "kind": "Glossary term", "label": "Machine-answerability dispute record", "path": "/glossary.php#machine-answerability-dispute-record" }, { "id": "evidence-contract", "kind": "Glossary term", "label": "Machine-answerability evidence contract", "path": "/glossary.php#evidence-contract" }, { "id": "no-authority-to-infer", "kind": "Glossary term", "label": "No authority to infer", "path": "/glossary.php#no-authority-to-infer" }, { "id": "production-accountability-handoff", "kind": "Glossary term", "label": "Production-accountability handoff", "path": "/glossary.php#production-accountability-handoff" }, { "id": "separation-of-duties", "kind": "Glossary term", "label": "Separation of duties", "path": "/glossary.php#separation-of-duties" }, { "id": "systemic-pattern-support", "kind": "Glossary term", "label": "Systemic-pattern support", "path": "/glossary.php#systemic-pattern-support" }, { "id": "AAC-CL-08", "kind": "Machine Answerability Assurance claim", "label": "Incident is reconstructable and correctable", "path": "/answerability-assurance.php#assurance-claim-reconstructable" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "AEC-CT-08", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-08", "path": "/answerability-contract.php#evidence-contract-aec-ct-08" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-08", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-08", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-17", "kind": "Machine Answerability Remediation safeguard", "label": "Append-oriented causal evidence ledger", "path": "/answerability-remediation.php#safeguard-append-only-causal-ledger" }, { "id": "MAR-SG-19", "kind": "Machine Answerability Remediation safeguard", "label": "Fluent generated explanation after the event", "path": "/answerability-remediation.php#safeguard-generated-explanation" }, { "id": "MAR-SG-18", "kind": "Machine Answerability Remediation safeguard", "label": "Named correction, suspension, and retirement owner", "path": "/answerability-remediation.php#safeguard-independent-reconstruction-correction-owner" }, { "id": "MAR-H-EV-ACCOUNTABILITY", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Evulgare Accountability", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" } ] }, { "id": "evulgare-provenance", "title": "Decision Provenance", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/provenance", "type": "First-party live product-area description", "supports": "The public provenance model for append-oriented histories connecting entities, activities, agents, transformations, versions, authority, interface state, and later invalidations. It does not independently establish a deployed integration.", "review": { "source_id": "evulgare-provenance", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E01", "kind": "Accountability Handoff evidence requirement", "label": "Raw sensor observation", "path": "/accountability-handoff.php#evidence-AH-E01" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "evidence-provenance", "kind": "Concept Matrix production handoff", "label": "Evidence provenance", "path": "/concept-matrix.php#concept-evidence-provenance" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "changed-retest-fixture-comparability", "kind": "FAQ answer", "label": "Can a changed retest fixture be compared as though it were the original fixture?", "path": "/faq.php#changed-retest-fixture-comparability" }, { "id": "correlation-versus-common-cause", "kind": "FAQ answer", "label": "Do correlated symptoms or a shared cohort prove a common cause?", "path": "/faq.php#correlation-versus-common-cause" }, { "id": "closed-ticket-versus-effective-control", "kind": "FAQ answer", "label": "Does a closed ticket or human sign-off prove that a corrective action worked?", "path": "/faq.php#closed-ticket-versus-effective-control" }, { "id": "monitoring-signal-versus-verified-regression", "kind": "FAQ answer", "label": "Does a monitoring alert prove that a corrective action regressed?", "path": "/faq.php#monitoring-signal-versus-verified-regression" }, { "id": "synthetic-alert-test-production-safety", "kind": "FAQ answer", "label": "Does a passed synthetic alert-path test prove production safety or factual truth?", "path": "/faq.php#synthetic-alert-test-production-safety" }, { "id": "safeguard-effect-classification", "kind": "FAQ answer", "label": "Does a safeguard labeled “prevent” prove that it will prevent a real incident?", "path": "/faq.php#safeguard-effect-classification" }, { "id": "evidence-integrity-versus-support", "kind": "FAQ answer", "label": "Does a signed or hashed evidence record prove that an assurance claim is true?", "path": "/faq.php#evidence-integrity-versus-support" }, { "id": "evidence-completeness-ground-truth", "kind": "FAQ answer", "label": "Does adding more evidence change what happened in the replay?", "path": "/faq.php#evidence-completeness-ground-truth" }, { "id": "alert-delivery-review-verification", "kind": "FAQ answer", "label": "Does alert delivery prove that a regression was reviewed and verified?", "path": "/faq.php#alert-delivery-review-verification" }, { "id": "corrective-action-versus-history", "kind": "FAQ answer", "label": "Does corrective action erase the earlier claim or review packet?", "path": "/faq.php#corrective-action-versus-history" }, { "id": "recurrence-count-versus-rate", "kind": "FAQ answer", "label": "Does counting recurrence observations create a recurrence rate or risk estimate?", "path": "/faq.php#recurrence-count-versus-rate" }, { "id": "monitoring-silence-versus-safety", "kind": "FAQ answer", "label": "Does monitoring silence prove that a corrective action remains safe or effective?", "path": "/faq.php#monitoring-silence-versus-safety" }, { "id": "remediation-selected-versus-implemented", "kind": "FAQ answer", "label": "Does selecting or configuring a monitoring remediation prove that it was implemented and tested?", "path": "/faq.php#remediation-selected-versus-implemented" }, { "id": "concept-to-production-handoff", "kind": "FAQ answer", "label": "How does a KillChains.com concept become a production-accountability requirement?", "path": "/faq.php#concept-to-production-handoff" }, { "id": "alert-receipt-versus-competent-review", "kind": "FAQ answer", "label": "Is acknowledging an alert the same as competent review and independent verification?", "path": "/faq.php#alert-receipt-versus-competent-review" }, { "id": "machine-answerability-assurance-case", "kind": "FAQ answer", "label": "What is a machine-answerability assurance case?", "path": "/faq.php#machine-answerability-assurance-case" }, { "id": "assurance-review-packet", "kind": "FAQ answer", "label": "What is a machine-answerability assurance review packet?", "path": "/faq.php#assurance-review-packet" }, { "id": "machine-answerability-dispute-record", "kind": "FAQ answer", "label": "What is a machine-answerability dispute record?", "path": "/faq.php#machine-answerability-dispute-record" }, { "id": "evidence-contract", "kind": "FAQ answer", "label": "What is a machine-answerability evidence contract?", "path": "/faq.php#evidence-contract" }, { "id": "evidence-gap-remediation", "kind": "FAQ answer", "label": "What is machine-answerability evidence-gap remediation?", "path": "/faq.php#evidence-gap-remediation" }, { "id": "machine-answerability-replay", "kind": "FAQ answer", "label": "What is the Machine Answerability Replay?", "path": "/faq.php#machine-answerability-replay" }, { "id": "why-normal-log-insufficient", "kind": "FAQ answer", "label": "Why is an ordinary event log not enough for an autonomous-system failure?", "path": "/faq.php#why-normal-log-insufficient" }, { "id": "evidence-request-versus-production", "kind": "FAQ answer", "label": "Why is requesting evidence different from producing it?", "path": "/faq.php#evidence-request-versus-production" }, { "id": "alert-integrity", "kind": "Glossary term", "label": "Alert integrity", "path": "/glossary.php#alert-integrity" }, { "id": "assurance-review-packet", "kind": "Glossary term", "label": "Assurance review packet", "path": "/glossary.php#assurance-review-packet" }, { "id": "bounded-pattern-cohort", "kind": "Glossary term", "label": "Bounded pattern cohort", "path": "/glossary.php#bounded-pattern-cohort" }, { "id": "corrective-action-ledger", "kind": "Glossary term", "label": "Corrective action ledger", "path": "/glossary.php#corrective-action-ledger" }, { "id": "coverage-remediation-validation-drill", "kind": "Glossary term", "label": "Coverage remediation validation drill", "path": "/glossary.php#coverage-remediation-validation-drill" }, { "id": "effectiveness-unknown", "kind": "Glossary term", "label": "Effectiveness unknown", "path": "/glossary.php#effectiveness-unknown" }, { "id": "evidence-integrity-versus-factual-support", "kind": "Glossary term", "label": "Evidence integrity versus factual support", "path": "/glossary.php#evidence-integrity-versus-factual-support" }, { "id": "evidence-request-versus-production", "kind": "Glossary term", "label": "Evidence request versus production", "path": "/glossary.php#evidence-request-versus-production" }, { "id": "evidence-deficiency-report", "kind": "Glossary term", "label": "Evidence-deficiency report", "path": "/glossary.php#evidence-deficiency-report" }, { "id": "evidence-gap-remediation", "kind": "Glossary term", "label": "Evidence-gap remediation", "path": "/glossary.php#evidence-gap-remediation" }, { "id": "immutable-audit-reopening", "kind": "Glossary term", "label": "Immutable audit reopening", "path": "/glossary.php#immutable-audit-reopening" }, { "id": "answerability-replay", "kind": "Glossary term", "label": "Machine answerability replay", "path": "/glossary.php#answerability-replay" }, { "id": "machine-answerability-dispute-record", "kind": "Glossary term", "label": "Machine-answerability dispute record", "path": "/glossary.php#machine-answerability-dispute-record" }, { "id": "evidence-contract", "kind": "Glossary term", "label": "Machine-answerability evidence contract", "path": "/glossary.php#evidence-contract" }, { "id": "monitoring-coverage", "kind": "Glossary term", "label": "Monitoring coverage", "path": "/glossary.php#monitoring-coverage" }, { "id": "production-accountability-handoff", "kind": "Glossary term", "label": "Production-accountability handoff", "path": "/glossary.php#production-accountability-handoff" }, { "id": "same-fixture-retest", "kind": "Glossary term", "label": "Same-fixture retest", "path": "/glossary.php#same-fixture-retest" }, { "id": "typed-recurrence-event-count", "kind": "Glossary term", "label": "Typed recurrence event count", "path": "/glossary.php#typed-recurrence-event-count" }, { "id": "validation-exception-branch", "kind": "Glossary term", "label": "Validation exception branch", "path": "/glossary.php#validation-exception-branch" }, { "id": "AAC-CL-06", "kind": "Machine Answerability Assurance claim", "label": "Configuration is identified and revalidated", "path": "/answerability-assurance.php#assurance-claim-configuration" }, { "id": "AAC-CL-08", "kind": "Machine Answerability Assurance claim", "label": "Incident is reconstructable and correctable", "path": "/answerability-assurance.php#assurance-claim-reconstructable" }, { "id": "AAC-CL-01", "kind": "Machine Answerability Assurance claim", "label": "Independent, traceable evidence", "path": "/answerability-assurance.php#assurance-claim-source-independence" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-010", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Append-oriented custody independently verified for the corrected packet", "path": "/answerability-effectiveness.php?audit=MAE-AUD-010" }, { "id": "MAE-AUD-007", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Corrected configuration claim invalidated by a later threshold change", "path": "/answerability-effectiveness.php?audit=MAE-AUD-007" }, { "id": "MAE-AUD-011", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Independent-review action remains unowned", "path": "/answerability-effectiveness.php?audit=MAE-AUD-011" }, { "id": "MAE-AUD-009", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Provenance dispute closed with continuing exposure", "path": "/answerability-effectiveness.php?audit=MAE-AUD-009" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-013", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Custody control remains current after scheduled verification", "path": "/answerability-monitoring.php?branch=MAM-BR-013" }, { "id": "MAM-BR-012", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Evidence-access loss reopens a provenance closure", "path": "/answerability-monitoring.php?branch=MAM-BR-012" }, { "id": "MAM-BR-010", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Threshold mismatch verifies the need to reopen the corrected configuration", "path": "/answerability-monitoring.php?branch=MAM-BR-010" }, { "id": "MAM-BR-014", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Unowned monitoring duty remains no authority to infer", "path": "/answerability-monitoring.php?branch=MAM-BR-014" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "MAVD-RESULT-C93BE5527E82", "kind": "Machine Answerability Coverage Validation drill", "label": "Ceremonial acknowledgment failure", "path": "/answerability-validation.php?preset=MAVD-PRESET-CEREMONIAL-ACKNOWLEDGMENT" }, { "id": "machine-answerability-coverage-validation", "kind": "Machine Answerability Coverage Validation publication", "label": "Machine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill", "path": "/answerability-validation.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-005", "kind": "Machine Answerability Dispute Ledger record", "label": "Configuration claim corrected without erasing the earlier packet", "path": "/answerability-disputes.php?record=MAD-DSP-005" }, { "id": "MAD-DSP-008", "kind": "Machine Answerability Dispute Ledger record", "label": "Producer-controlled verification challenge remains unresolved", "path": "/answerability-disputes.php?record=MAD-DSP-008" }, { "id": "MAD-DSP-007", "kind": "Machine Answerability Dispute Ledger record", "label": "Revalidated provenance claim closed with residual unknowns", "path": "/answerability-disputes.php?record=MAD-DSP-007" }, { "id": "AEC-CT-01", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-01", "path": "/answerability-contract.php#evidence-contract-aec-ct-01" }, { "id": "AEC-CT-06", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-06", "path": "/answerability-contract.php#evidence-contract-aec-ct-06" }, { "id": "AEC-CT-08", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-08", "path": "/answerability-contract.php#evidence-contract-aec-ct-08" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-01", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-01", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-06", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-06", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-08", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-08", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAPR-RESULT-B9AA7DDDFF63", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Correlated transport symptoms with common cause unproven", "path": "/answerability-patterns.php?preset=MAPR-PRESET-CORRELATED-TRANSPORT-COMMON-CAUSE-UNPROVEN" }, { "id": "MAPR-RESULT-F503CEC14915", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "No observed recurrence in a sparse selected sample", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SPARSE-NO-OBSERVED-RECURRENCE" }, { "id": "MAPR-RESULT-9DD2829BDCC2", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Repeated same-stage, same-fixture recurrence", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SAME-STAGE-SAME-FIXTURE-RECURRENCE" }, { "id": "machine-answerability-exception-recurrence-pattern-review", "kind": "Machine Answerability Exception Recurrence Pattern Review publication", "label": "Machine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review", "path": "/answerability-patterns.php" }, { "id": "MAC-BR-012", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Alert reviewed without access to underlying evidence", "path": "/answerability-coverage.php?branch=MAC-BR-012" }, { "id": "MAC-BR-010", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Configuration changed outside the monitored component", "path": "/answerability-coverage.php?branch=MAC-BR-010" }, { "id": "MAC-BR-014", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Monitoring duties have no competent institutional owner", "path": "/answerability-coverage.php?branch=MAC-BR-014" }, { "id": "MAC-BR-013", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Producer-controlled verification leaves independence unresolved", "path": "/answerability-coverage.php?branch=MAC-BR-013" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-17", "kind": "Machine Answerability Remediation safeguard", "label": "Append-oriented causal evidence ledger", "path": "/answerability-remediation.php#safeguard-append-only-causal-ledger" }, { "id": "MAR-SG-15", "kind": "Machine Answerability Remediation safeguard", "label": "Exact software and configuration manifest", "path": "/answerability-remediation.php#safeguard-exact-artifact-manifest" }, { "id": "MAR-SG-19", "kind": "Machine Answerability Remediation safeguard", "label": "Fluent generated explanation after the event", "path": "/answerability-remediation.php#safeguard-generated-explanation" }, { "id": "MAR-SG-01", "kind": "Machine Answerability Remediation safeguard", "label": "Independent-source quorum", "path": "/answerability-remediation.php#safeguard-independent-source-gate" }, { "id": "MAR-SG-02", "kind": "Machine Answerability Remediation safeguard", "label": "Shared-dependency alarm", "path": "/answerability-remediation.php#safeguard-dependency-alarm" }, { "id": "MAR-SG-03", "kind": "Machine Answerability Remediation safeguard", "label": "Signed source and transformation lineage", "path": "/answerability-remediation.php#safeguard-provenance-completeness-gate" }, { "id": "MAR-H-EV-PROVENANCE", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Decision Provenance", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" }, { "id": "MAER-RESULT-3AC98EAF1C6B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Ownerless exception escalation", "path": "/answerability-retest.php?preset=MAER-PRESET-OWNERLESS-ESCALATION" }, { "id": "MAER-RESULT-9748DE4E576B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Recurring transport and deduplication failure", "path": "/answerability-retest.php?preset=MAER-PRESET-RECURRING-TRANSPORT-DEDUP" }, { "id": "MAER-RESULT-034FF9A56113", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Successful independent same-fixture retest", "path": "/answerability-retest.php?preset=MAER-PRESET-SUCCESSFUL-SAME-FIXTURE" }, { "id": "machine-answerability-validation-exception-retest", "kind": "Machine Answerability Validation Exception and Retest publication", "label": "Machine Answerability Validation Exception, Retest, and Escalation Ledger", "path": "/answerability-retest.php" } ] }, { "id": "evulgare-assurance", "title": "Continuous Assurance", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/assurance", "type": "First-party live product-area description", "supports": "The public assurance model connecting claims, evidence, assumptions, counterclaims, defeaters, reviewers, configurations, and invalidating changes. It does not certify any external system or claim.", "review": { "source_id": "evulgare-assurance", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E11", "kind": "Accountability Handoff evidence requirement", "label": "Assurance claim after a material update", "path": "/accountability-handoff.php#evidence-AH-E11" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "machine-execution", "kind": "Concept Matrix production handoff", "label": "Machine execution", "path": "/concept-matrix.php#concept-machine-execution" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "changed-retest-fixture-comparability", "kind": "FAQ answer", "label": "Can a changed retest fixture be compared as though it were the original fixture?", "path": "/faq.php#changed-retest-fixture-comparability" }, { "id": "correlation-versus-common-cause", "kind": "FAQ answer", "label": "Do correlated symptoms or a shared cohort prove a common cause?", "path": "/faq.php#correlation-versus-common-cause" }, { "id": "closed-ticket-versus-effective-control", "kind": "FAQ answer", "label": "Does a closed ticket or human sign-off prove that a corrective action worked?", "path": "/faq.php#closed-ticket-versus-effective-control" }, { "id": "operational-release-authority", "kind": "FAQ answer", "label": "Does a complete assurance review packet authorize real-world operation?", "path": "/faq.php#operational-release-authority" }, { "id": "monitor-health-versus-monitor-scope", "kind": "FAQ answer", "label": "Does a healthy monitor prove that it watches the right system state?", "path": "/faq.php#monitor-health-versus-monitor-scope" }, { "id": "monitoring-signal-versus-verified-regression", "kind": "FAQ answer", "label": "Does a monitoring alert prove that a corrective action regressed?", "path": "/faq.php#monitoring-signal-versus-verified-regression" }, { "id": "synthetic-alert-test-production-safety", "kind": "FAQ answer", "label": "Does a passed synthetic alert-path test prove production safety or factual truth?", "path": "/faq.php#synthetic-alert-test-production-safety" }, { "id": "safeguard-effect-classification", "kind": "FAQ answer", "label": "Does a safeguard labeled “prevent” prove that it will prevent a real incident?", "path": "/faq.php#safeguard-effect-classification" }, { "id": "evidence-integrity-versus-support", "kind": "FAQ answer", "label": "Does a signed or hashed evidence record prove that an assurance claim is true?", "path": "/faq.php#evidence-integrity-versus-support" }, { "id": "validation-exception-acknowledgment-versus-ownership", "kind": "FAQ answer", "label": "Does acknowledging a validation exception mean an institution owns it?", "path": "/faq.php#validation-exception-acknowledgment-versus-ownership" }, { "id": "evidence-completeness-ground-truth", "kind": "FAQ answer", "label": "Does adding more evidence change what happened in the replay?", "path": "/faq.php#evidence-completeness-ground-truth" }, { "id": "alert-delivery-review-verification", "kind": "FAQ answer", "label": "Does alert delivery prove that a regression was reviewed and verified?", "path": "/faq.php#alert-delivery-review-verification" }, { "id": "dispute-closure-versus-certainty", "kind": "FAQ answer", "label": "Does closing a dispute establish certainty, legal responsibility, or operational release?", "path": "/faq.php#dispute-closure-versus-certainty" }, { "id": "effectiveness-closure-residual-exposure", "kind": "FAQ answer", "label": "Does closing an effectiveness audit eliminate residual exposure or authorize a real system?", "path": "/faq.php#effectiveness-closure-residual-exposure" }, { "id": "recurrence-count-versus-rate", "kind": "FAQ answer", "label": "Does counting recurrence observations create a recurrence rate or risk estimate?", "path": "/faq.php#recurrence-count-versus-rate" }, { "id": "monitoring-silence-versus-safety", "kind": "FAQ answer", "label": "Does monitoring silence prove that a corrective action remains safe or effective?", "path": "/faq.php#monitoring-silence-versus-safety" }, { "id": "no-observed-recurrence-versus-disproof", "kind": "FAQ answer", "label": "Does no observed recurrence in a selected sample disprove recurrence?", "path": "/faq.php#no-observed-recurrence-versus-disproof" }, { "id": "one-retest-pass-versus-durable-nonrecurrence", "kind": "FAQ answer", "label": "Does one successful same-fixture retest prove durable non-recurrence?", "path": "/faq.php#one-retest-pass-versus-durable-nonrecurrence" }, { "id": "reopened-audit-versus-erased-history", "kind": "FAQ answer", "label": "Does reopening and revalidating an audit erase the earlier invalidation or assign responsibility?", "path": "/faq.php#reopened-audit-versus-erased-history" }, { "id": "remediation-selected-versus-implemented", "kind": "FAQ answer", "label": "Does selecting or configuring a monitoring remediation prove that it was implemented and tested?", "path": "/faq.php#remediation-selected-versus-implemented" }, { "id": "alert-receipt-versus-competent-review", "kind": "FAQ answer", "label": "Is acknowledging an alert the same as competent review and independent verification?", "path": "/faq.php#alert-receipt-versus-competent-review" }, { "id": "review-ownership", "kind": "FAQ answer", "label": "What does review ownership mean for a consequential machine decision?", "path": "/faq.php#review-ownership" }, { "id": "machine-answerability-remediation", "kind": "FAQ answer", "label": "What does the Machine Answerability Remediation Lab test?", "path": "/faq.php#machine-answerability-remediation" }, { "id": "no-authority-to-infer", "kind": "FAQ answer", "label": "What does “no authority to infer” mean?", "path": "/faq.php#no-authority-to-infer" }, { "id": "corrective-action-effectiveness-audit", "kind": "FAQ answer", "label": "What is a corrective-action effectiveness audit?", "path": "/faq.php#corrective-action-effectiveness-audit" }, { "id": "machine-answerability-assurance-case", "kind": "FAQ answer", "label": "What is a machine-answerability assurance case?", "path": "/faq.php#machine-answerability-assurance-case" }, { "id": "assurance-review-packet", "kind": "FAQ answer", "label": "What is a machine-answerability assurance review packet?", "path": "/faq.php#assurance-review-packet" }, { "id": "machine-answerability-dispute-record", "kind": "FAQ answer", "label": "What is a machine-answerability dispute record?", "path": "/faq.php#machine-answerability-dispute-record" }, { "id": "evidence-contract", "kind": "FAQ answer", "label": "What is a machine-answerability evidence contract?", "path": "/faq.php#evidence-contract" }, { "id": "corrective-action-monitoring-regression-reopening", "kind": "FAQ answer", "label": "What is corrective-action monitoring, regression, and reopening?", "path": "/faq.php#corrective-action-monitoring-regression-reopening" }, { "id": "evidence-gap-remediation", "kind": "FAQ answer", "label": "What is machine-answerability evidence-gap remediation?", "path": "/faq.php#evidence-gap-remediation" }, { "id": "assurance-invalidation", "kind": "FAQ answer", "label": "When should an assurance claim be suspended or withdrawn?", "path": "/faq.php#assurance-invalidation" }, { "id": "assurance-version-diff", "kind": "FAQ answer", "label": "Why compare version-bound assurance snapshots?", "path": "/faq.php#assurance-version-diff" }, { "id": "alert-integrity", "kind": "Glossary term", "label": "Alert integrity", "path": "/glossary.php#alert-integrity" }, { "id": "assurance-case", "kind": "Glossary term", "label": "Assurance case", "path": "/glossary.php#assurance-case" }, { "id": "assurance-defeater", "kind": "Glossary term", "label": "Assurance defeater", "path": "/glossary.php#assurance-defeater" }, { "id": "assurance-invalidation-gate", "kind": "Glossary term", "label": "Assurance invalidation gate", "path": "/glossary.php#assurance-invalidation-gate" }, { "id": "assurance-review-packet", "kind": "Glossary term", "label": "Assurance review packet", "path": "/glossary.php#assurance-review-packet" }, { "id": "assurance-snapshot", "kind": "Glossary term", "label": "Assurance snapshot", "path": "/glossary.php#assurance-snapshot" }, { "id": "assurance-state", "kind": "Glossary term", "label": "Assurance state", "path": "/glossary.php#assurance-state" }, { "id": "assurance-version-diff", "kind": "Glossary term", "label": "Assurance version diff", "path": "/glossary.php#assurance-version-diff" }, { "id": "bounded-pattern-cohort", "kind": "Glossary term", "label": "Bounded pattern cohort", "path": "/glossary.php#bounded-pattern-cohort" }, { "id": "ceremonial-alert-acknowledgment", "kind": "Glossary term", "label": "Ceremonial alert acknowledgment", "path": "/glossary.php#ceremonial-alert-acknowledgment" }, { "id": "closure-with-residual-unknowns", "kind": "Glossary term", "label": "Closure with residual unknowns", "path": "/glossary.php#closure-with-residual-unknowns" }, { "id": "corrective-action-effectiveness-audit", "kind": "Glossary term", "label": "Corrective-action effectiveness audit", "path": "/glossary.php#corrective-action-effectiveness-audit" }, { "id": "corrective-action-monitoring", "kind": "Glossary term", "label": "Corrective-action monitoring", "path": "/glossary.php#corrective-action-monitoring" }, { "id": "coverage-remediation-validation-drill", "kind": "Glossary term", "label": "Coverage remediation validation drill", "path": "/glossary.php#coverage-remediation-validation-drill" }, { "id": "effectiveness-unknown", "kind": "Glossary term", "label": "Effectiveness unknown", "path": "/glossary.php#effectiveness-unknown" }, { "id": "evidence-integrity-versus-factual-support", "kind": "Glossary term", "label": "Evidence integrity versus factual support", "path": "/glossary.php#evidence-integrity-versus-factual-support" }, { "id": "evidence-deficiency-report", "kind": "Glossary term", "label": "Evidence-deficiency report", "path": "/glossary.php#evidence-deficiency-report" }, { "id": "evidence-gap-remediation", "kind": "Glossary term", "label": "Evidence-gap remediation", "path": "/glossary.php#evidence-gap-remediation" }, { "id": "answerability-remediation", "kind": "Glossary term", "label": "Machine answerability remediation", "path": "/glossary.php#answerability-remediation" }, { "id": "machine-answerability-dispute-record", "kind": "Glossary term", "label": "Machine-answerability dispute record", "path": "/glossary.php#machine-answerability-dispute-record" }, { "id": "evidence-contract", "kind": "Glossary term", "label": "Machine-answerability evidence contract", "path": "/glossary.php#evidence-contract" }, { "id": "monitoring-blind-spot", "kind": "Glossary term", "label": "Monitoring blind spot", "path": "/glossary.php#monitoring-blind-spot" }, { "id": "monitoring-coverage", "kind": "Glossary term", "label": "Monitoring coverage", "path": "/glossary.php#monitoring-coverage" }, { "id": "operational-release-authority", "kind": "Glossary term", "label": "Operational release authority", "path": "/glossary.php#operational-release-authority" }, { "id": "recurrence-classification", "kind": "Glossary term", "label": "Recurrence classification", "path": "/glossary.php#recurrence-classification" }, { "id": "regression-signal", "kind": "Glossary term", "label": "Regression signal", "path": "/glossary.php#regression-signal" }, { "id": "residual-exposure", "kind": "Glossary term", "label": "Residual exposure", "path": "/glossary.php#residual-exposure" }, { "id": "review-ownership", "kind": "Glossary term", "label": "Review ownership", "path": "/glossary.php#review-ownership" }, { "id": "same-fixture-retest", "kind": "Glossary term", "label": "Same-fixture retest", "path": "/glossary.php#same-fixture-retest" }, { "id": "separation-of-duties", "kind": "Glossary term", "label": "Separation of duties", "path": "/glossary.php#separation-of-duties" }, { "id": "synthetic-alert-path-mechanics", "kind": "Glossary term", "label": "Synthetic alert-path mechanics", "path": "/glossary.php#synthetic-alert-path-mechanics" }, { "id": "systemic-pattern-support", "kind": "Glossary term", "label": "Systemic-pattern support", "path": "/glossary.php#systemic-pattern-support" }, { "id": "typed-recurrence-event-count", "kind": "Glossary term", "label": "Typed recurrence event count", "path": "/glossary.php#typed-recurrence-event-count" }, { "id": "validation-exception-branch", "kind": "Glossary term", "label": "Validation exception branch", "path": "/glossary.php#validation-exception-branch" }, { "id": "AAC-CL-06", "kind": "Machine Answerability Assurance claim", "label": "Configuration is identified and revalidated", "path": "/answerability-assurance.php#assurance-claim-configuration" }, { "id": "AAC-CL-02", "kind": "Machine Answerability Assurance claim", "label": "Model remains inside envelope", "path": "/answerability-assurance.php#assurance-claim-model-envelope" }, { "id": "AAC-CL-07", "kind": "Machine Answerability Assurance claim", "label": "Stale assurance is automatically suspended", "path": "/answerability-assurance.php#assurance-claim-continuous-invalidation" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-010", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Append-oriented custody independently verified for the corrected packet", "path": "/answerability-effectiveness.php?audit=MAE-AUD-010" }, { "id": "MAE-AUD-003", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Changed-model records produced but not independently verified", "path": "/answerability-effectiveness.php?audit=MAE-AUD-003" }, { "id": "MAE-AUD-007", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Corrected configuration claim invalidated by a later threshold change", "path": "/answerability-effectiveness.php?audit=MAE-AUD-007" }, { "id": "MAE-AUD-002", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Custody restoration marked implemented without technical proof", "path": "/answerability-effectiveness.php?audit=MAE-AUD-002" }, { "id": "MAE-AUD-001", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Evidence request exists only as a plan", "path": "/answerability-effectiveness.php?audit=MAE-AUD-001" }, { "id": "MAE-AUD-006", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Produced evidence found ineffective for the calibration gap", "path": "/answerability-effectiveness.php?audit=MAE-AUD-006" }, { "id": "MAE-AUD-004", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Suspension gate independently verified for the changed-model branch", "path": "/answerability-effectiveness.php?audit=MAE-AUD-004" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-017", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "A closed ticket cannot supply a monitoring baseline", "path": "/answerability-monitoring.php?branch=MAM-BR-017" }, { "id": "MAM-BR-016", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "A planned action has no effectiveness baseline to monitor", "path": "/answerability-monitoring.php?branch=MAM-BR-016" }, { "id": "MAM-BR-005", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Assurance monitor failure forces suspension and reopening", "path": "/answerability-monitoring.php?branch=MAM-BR-005" }, { "id": "MAM-BR-003", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Calibration drift signal observed but not independently verified", "path": "/answerability-monitoring.php?branch=MAM-BR-003" }, { "id": "MAM-BR-004", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Calibration regression independently verified", "path": "/answerability-monitoring.php?branch=MAM-BR-004" }, { "id": "MAM-BR-013", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Custody control remains current after scheduled verification", "path": "/answerability-monitoring.php?branch=MAM-BR-013" }, { "id": "MAM-BR-009", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Monitoring cannot rescue an action already shown ineffective", "path": "/answerability-monitoring.php?branch=MAM-BR-009" }, { "id": "MAM-BR-006", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Monitoring restored; independent revalidation still pending", "path": "/answerability-monitoring.php?branch=MAM-BR-006" }, { "id": "MAM-BR-018", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Producer records remain insufficient for durable monitoring without independent verification", "path": "/answerability-monitoring.php?branch=MAM-BR-018" }, { "id": "MAM-BR-007", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Remediated suspension gate independently revalidated and reclosed", "path": "/answerability-monitoring.php?branch=MAM-BR-007" }, { "id": "MAM-BR-002", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Scheduled monitoring completed without a regression signal", "path": "/answerability-monitoring.php?branch=MAM-BR-002" }, { "id": "MAM-BR-001", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Suspension gate reaches its scheduled review date", "path": "/answerability-monitoring.php?branch=MAM-BR-001" }, { "id": "MAM-BR-010", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Threshold mismatch verifies the need to reopen the corrected configuration", "path": "/answerability-monitoring.php?branch=MAM-BR-010" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "MAVD-RESULT-4E98173EEB2E", "kind": "Machine Answerability Coverage Validation drill", "label": "End-to-end alert-path validation", "path": "/answerability-validation.php?preset=MAVD-PRESET-END-TO-END" }, { "id": "machine-answerability-coverage-validation", "kind": "Machine Answerability Coverage Validation publication", "label": "Machine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill", "path": "/answerability-validation.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-002", "kind": "Machine Answerability Dispute Ledger record", "label": "Changed model evidence produced and reliance suspended", "path": "/answerability-disputes.php?record=MAD-DSP-002" }, { "id": "MAD-DSP-005", "kind": "Machine Answerability Dispute Ledger record", "label": "Configuration claim corrected without erasing the earlier packet", "path": "/answerability-disputes.php?record=MAD-DSP-005" }, { "id": "MAD-DSP-001", "kind": "Machine Answerability Dispute Ledger record", "label": "Model-change evidence request remains open", "path": "/answerability-disputes.php?record=MAD-DSP-001" }, { "id": "AEC-CT-02", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-02", "path": "/answerability-contract.php#evidence-contract-aec-ct-02" }, { "id": "AEC-CT-06", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-06", "path": "/answerability-contract.php#evidence-contract-aec-ct-06" }, { "id": "AEC-CT-07", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-07", "path": "/answerability-contract.php#evidence-contract-aec-ct-07" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-02", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-02", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-06", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-06", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-07", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-07", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAPR-RESULT-B9AA7DDDFF63", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Correlated transport symptoms with common cause unproven", "path": "/answerability-patterns.php?preset=MAPR-PRESET-CORRELATED-TRANSPORT-COMMON-CAUSE-UNPROVEN" }, { "id": "MAPR-RESULT-F503CEC14915", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "No observed recurrence in a sparse selected sample", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SPARSE-NO-OBSERVED-RECURRENCE" }, { "id": "MAPR-RESULT-9DD2829BDCC2", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Repeated same-stage, same-fixture recurrence", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SAME-STAGE-SAME-FIXTURE-RECURRENCE" }, { "id": "machine-answerability-exception-recurrence-pattern-review", "kind": "Machine Answerability Exception Recurrence Pattern Review publication", "label": "Machine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review", "path": "/answerability-patterns.php" }, { "id": "MAC-BR-002", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Bounded coverage verified and no regression alert recorded", "path": "/answerability-coverage.php?branch=MAC-BR-002" }, { "id": "MAC-BR-010", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Configuration changed outside the monitored component", "path": "/answerability-coverage.php?branch=MAC-BR-010" }, { "id": "MAC-BR-007", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Coverage remediated and alert path independently tested", "path": "/answerability-coverage.php?branch=MAC-BR-007" }, { "id": "MAC-BR-005", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Disabled monitor creates false silence", "path": "/answerability-coverage.php?branch=MAC-BR-005" }, { "id": "MAC-BR-003", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Drift alert delivered but not reviewed", "path": "/answerability-coverage.php?branch=MAC-BR-003" }, { "id": "MAC-BR-018", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Drift alert lost during deduplication", "path": "/answerability-coverage.php?branch=MAC-BR-018" }, { "id": "MAC-BR-004", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Drift alert reviewed and regression independently verified", "path": "/answerability-coverage.php?branch=MAC-BR-004" }, { "id": "MAC-BR-006", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Monitor restored against a stale baseline", "path": "/answerability-coverage.php?branch=MAC-BR-006" }, { "id": "MAC-BR-016", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Monitoring compares an unknown source state with a stale baseline", "path": "/answerability-coverage.php?branch=MAC-BR-016" }, { "id": "MAC-BR-013", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Producer-controlled verification leaves independence unresolved", "path": "/answerability-coverage.php?branch=MAC-BR-013" }, { "id": "MAC-BR-009", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Quiet monitoring cannot convert an ineffective action into an effective control", "path": "/answerability-coverage.php?branch=MAC-BR-009" }, { "id": "MAC-BR-001", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Scheduled monitoring has no performed coverage record", "path": "/answerability-coverage.php?branch=MAC-BR-001" }, { "id": "MAC-BR-017", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Silent provenance monitor misses a shared source dependency", "path": "/answerability-coverage.php?branch=MAC-BR-017" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-05", "kind": "Machine Answerability Remediation safeguard", "label": "Calibration and envelope monitor", "path": "/answerability-remediation.php#safeguard-calibration-drift-monitor" }, { "id": "MAR-SG-16", "kind": "Machine Answerability Remediation safeguard", "label": "Continuous assurance invalidation", "path": "/answerability-remediation.php#safeguard-material-change-assurance-invalidation" }, { "id": "MAR-SG-06", "kind": "Machine Answerability Remediation safeguard", "label": "Deterministic authority precondition gate", "path": "/answerability-remediation.php#safeguard-deterministic-authority-envelope" }, { "id": "MAR-SG-04", "kind": "Machine Answerability Remediation safeguard", "label": "Distribution-shift abstention gate", "path": "/answerability-remediation.php#safeguard-uncertainty-distribution-hold" }, { "id": "MAR-SG-14", "kind": "Machine Answerability Remediation safeguard", "label": "Material-change revalidation gate", "path": "/answerability-remediation.php#safeguard-material-change-revalidation" }, { "id": "MAR-H-EV-ASSURANCE", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Continuous Assurance", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" }, { "id": "MAER-RESULT-3AC98EAF1C6B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Ownerless exception escalation", "path": "/answerability-retest.php?preset=MAER-PRESET-OWNERLESS-ESCALATION" }, { "id": "MAER-RESULT-9748DE4E576B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Recurring transport and deduplication failure", "path": "/answerability-retest.php?preset=MAER-PRESET-RECURRING-TRANSPORT-DEDUP" }, { "id": "MAER-RESULT-034FF9A56113", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Successful independent same-fixture retest", "path": "/answerability-retest.php?preset=MAER-PRESET-SUCCESSFUL-SAME-FIXTURE" }, { "id": "machine-answerability-validation-exception-retest", "kind": "Machine Answerability Validation Exception and Retest publication", "label": "Machine Answerability Validation Exception, Retest, and Escalation Ledger", "path": "/answerability-retest.php" } ] }, { "id": "evulgare-authority", "title": "Authority Boundaries", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/authority", "type": "First-party live product-area description", "supports": "The public distinction among technical capability, trusted data, delegated authority, permitted purpose, and contextual permission. It does not establish the actual authority state of a third-party system.", "review": { "source_id": "evulgare-authority", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E05", "kind": "Accountability Handoff evidence requirement", "label": "Delegated authority envelope", "path": "/accountability-handoff.php#evidence-AH-E05" }, { "id": "AH-E08", "kind": "Accountability Handoff evidence requirement", "label": "Effective override path", "path": "/accountability-handoff.php#evidence-AH-E08" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "human-authorization", "kind": "Concept Matrix production handoff", "label": "Human authorization", "path": "/concept-matrix.php#concept-human-authorization" }, { "id": "institutional-authority", "kind": "Concept Matrix production handoff", "label": "Institutional authority", "path": "/concept-matrix.php#concept-institutional-authority" }, { "id": "preauthorization", "kind": "Concept Matrix production handoff", "label": "Preauthorization", "path": "/concept-matrix.php#concept-preauthorization" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "operational-release-authority", "kind": "FAQ answer", "label": "Does a complete assurance review packet authorize real-world operation?", "path": "/faq.php#operational-release-authority" }, { "id": "validation-exception-acknowledgment-versus-ownership", "kind": "FAQ answer", "label": "Does acknowledging a validation exception mean an institution owns it?", "path": "/faq.php#validation-exception-acknowledgment-versus-ownership" }, { "id": "dispute-closure-versus-certainty", "kind": "FAQ answer", "label": "Does closing a dispute establish certainty, legal responsibility, or operational release?", "path": "/faq.php#dispute-closure-versus-certainty" }, { "id": "effectiveness-closure-residual-exposure", "kind": "FAQ answer", "label": "Does closing an effectiveness audit eliminate residual exposure or authorize a real system?", "path": "/faq.php#effectiveness-closure-residual-exposure" }, { "id": "concept-to-production-handoff", "kind": "FAQ answer", "label": "How does a KillChains.com concept become a production-accountability requirement?", "path": "/faq.php#concept-to-production-handoff" }, { "id": "review-ownership", "kind": "FAQ answer", "label": "What does review ownership mean for a consequential machine decision?", "path": "/faq.php#review-ownership" }, { "id": "machine-answerability-remediation", "kind": "FAQ answer", "label": "What does the Machine Answerability Remediation Lab test?", "path": "/faq.php#machine-answerability-remediation" }, { "id": "no-authority-to-infer", "kind": "FAQ answer", "label": "What does “no authority to infer” mean?", "path": "/faq.php#no-authority-to-infer" }, { "id": "ceremonial-human-review", "kind": "FAQ answer", "label": "What is ceremonial human review?", "path": "/faq.php#ceremonial-human-review" }, { "id": "ceremonial-human-review", "kind": "Glossary term", "label": "Ceremonial human review", "path": "/glossary.php#ceremonial-human-review" }, { "id": "no-authority-to-infer", "kind": "Glossary term", "label": "No authority to infer", "path": "/glossary.php#no-authority-to-infer" }, { "id": "operational-release-authority", "kind": "Glossary term", "label": "Operational release authority", "path": "/glossary.php#operational-release-authority" }, { "id": "review-ownership", "kind": "Glossary term", "label": "Review ownership", "path": "/glossary.php#review-ownership" }, { "id": "AAC-CL-03", "kind": "Machine Answerability Assurance claim", "label": "Authority is current and enforced", "path": "/answerability-assurance.php#assurance-claim-authority" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-008", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Retired authority claim preserved with its replacement record", "path": "/answerability-effectiveness.php?audit=MAE-AUD-008" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-011", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Retired authority claim remains retired after replacement monitoring", "path": "/answerability-monitoring.php?branch=MAM-BR-011" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "MAVD-RESULT-15F2D804DB85", "kind": "Machine Answerability Coverage Validation drill", "label": "Blind-spot remediation challenge", "path": "/answerability-validation.php?preset=MAVD-PRESET-BLIND-SPOT-CHALLENGE" }, { "id": "machine-answerability-coverage-validation", "kind": "Machine Answerability Coverage Validation publication", "label": "Machine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill", "path": "/answerability-validation.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-006", "kind": "Machine Answerability Dispute Ledger record", "label": "Authority claim retired after the governing mandate changed", "path": "/answerability-disputes.php?record=MAD-DSP-006" }, { "id": "AEC-CT-03", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-03", "path": "/answerability-contract.php#evidence-contract-aec-ct-03" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-03", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-03", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAPR-RESULT-B9AA7DDDFF63", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Correlated transport symptoms with common cause unproven", "path": "/answerability-patterns.php?preset=MAPR-PRESET-CORRELATED-TRANSPORT-COMMON-CAUSE-UNPROVEN" }, { "id": "MAPR-RESULT-F503CEC14915", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "No observed recurrence in a sparse selected sample", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SPARSE-NO-OBSERVED-RECURRENCE" }, { "id": "MAPR-RESULT-9DD2829BDCC2", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Repeated same-stage, same-fixture recurrence", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SAME-STAGE-SAME-FIXTURE-RECURRENCE" }, { "id": "machine-answerability-exception-recurrence-pattern-review", "kind": "Machine Answerability Exception Recurrence Pattern Review publication", "label": "Machine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review", "path": "/answerability-patterns.php" }, { "id": "MAC-BR-011", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Replacement control inherits an unmonitored shared dependency", "path": "/answerability-coverage.php?branch=MAC-BR-011" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-07", "kind": "Machine Answerability Remediation safeguard", "label": "Authority scope and expiration pinning", "path": "/answerability-remediation.php#safeguard-scope-and-expiration-pinning" }, { "id": "MAR-SG-16", "kind": "Machine Answerability Remediation safeguard", "label": "Continuous assurance invalidation", "path": "/answerability-remediation.php#safeguard-material-change-assurance-invalidation" }, { "id": "MAR-SG-06", "kind": "Machine Answerability Remediation safeguard", "label": "Deterministic authority precondition gate", "path": "/answerability-remediation.php#safeguard-deterministic-authority-envelope" }, { "id": "MAR-SG-08", "kind": "Machine Answerability Remediation safeguard", "label": "Pre-commit evidence and review window", "path": "/answerability-remediation.php#safeguard-effective-stop-before-commit" }, { "id": "MAR-SG-12", "kind": "Machine Answerability Remediation safeguard", "label": "Reversible commit stage", "path": "/answerability-remediation.php#safeguard-reversible-commit-stage" }, { "id": "MAR-H-EV-AUTHORITY", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Authority Boundaries", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" }, { "id": "MAER-RESULT-3AC98EAF1C6B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Ownerless exception escalation", "path": "/answerability-retest.php?preset=MAER-PRESET-OWNERLESS-ESCALATION" }, { "id": "MAER-RESULT-9748DE4E576B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Recurring transport and deduplication failure", "path": "/answerability-retest.php?preset=MAER-PRESET-RECURRING-TRANSPORT-DEDUP" }, { "id": "MAER-RESULT-034FF9A56113", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Successful independent same-fixture retest", "path": "/answerability-retest.php?preset=MAER-PRESET-SUCCESSFUL-SAME-FIXTURE" }, { "id": "machine-answerability-validation-exception-retest", "kind": "Machine Answerability Validation Exception and Retest publication", "label": "Machine Answerability Validation Exception, Retest, and Escalation Ledger", "path": "/answerability-retest.php" } ] }, { "id": "evulgare-judgment", "title": "Meaningful Human Judgment", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/judgment", "type": "First-party live product-area description", "supports": "The public human-judgment model preserving raw evidence, contrary indicators, alternatives, review time, abstention, and independent hypothesis formation. It does not prove that any particular interface provides meaningful control.", "review": { "source_id": "evulgare-judgment", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E07", "kind": "Accountability Handoff evidence requirement", "label": "Eighty-six-millisecond decision window", "path": "/accountability-handoff.php#evidence-AH-E07" }, { "id": "AH-E06", "kind": "Accountability Handoff evidence requirement", "label": "Operator interface state", "path": "/accountability-handoff.php#evidence-AH-E06" }, { "id": "AH-E12", "kind": "Accountability Handoff evidence requirement", "label": "The final human click", "path": "/accountability-handoff.php#evidence-AH-E12" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "automation-bias", "kind": "Concept Matrix production handoff", "label": "Automation bias", "path": "/concept-matrix.php#concept-automation-bias" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "ceremonial-human-review", "kind": "FAQ answer", "label": "What is ceremonial human review?", "path": "/faq.php#ceremonial-human-review" }, { "id": "ceremonial-human-review", "kind": "Glossary term", "label": "Ceremonial human review", "path": "/glossary.php#ceremonial-human-review" }, { "id": "AAC-CL-04", "kind": "Machine Answerability Assurance claim", "label": "Human judgment is meaningful", "path": "/answerability-assurance.php#assurance-claim-human-judgment" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-012", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Operator-view replay produced without independent evidence access", "path": "/answerability-effectiveness.php?audit=MAE-AUD-012" }, { "id": "MAE-AUD-005", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Qualified meaningful-judgment claim is only partially effective", "path": "/answerability-effectiveness.php?audit=MAE-AUD-005" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-015", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Operator-view evidence cannot be monitored after verifier access is lost", "path": "/answerability-monitoring.php?branch=MAM-BR-015" }, { "id": "MAM-BR-008", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Operator-view regression reopens a partially effective correction", "path": "/answerability-monitoring.php?branch=MAM-BR-008" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-003", "kind": "Machine Answerability Dispute Ledger record", "label": "Meaningful-human-judgment claim narrowed after interface review", "path": "/answerability-disputes.php?record=MAD-DSP-003" }, { "id": "MAD-DSP-004", "kind": "Machine Answerability Dispute Ledger record", "label": "Operator cannot inherit missing suspension authority", "path": "/answerability-disputes.php?record=MAD-DSP-004" }, { "id": "AEC-CT-04", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-04", "path": "/answerability-contract.php#evidence-contract-aec-ct-04" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-04", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-04", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAC-BR-015", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Alert generated but notification muted", "path": "/answerability-coverage.php?branch=MAC-BR-015" }, { "id": "MAC-BR-008", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Healthy monitor does not cover the changed operator interface", "path": "/answerability-coverage.php?branch=MAC-BR-008" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-10", "kind": "Machine Answerability Remediation safeguard", "label": "Mandatory post-action confirmation click", "path": "/answerability-remediation.php#safeguard-postaction-confirmation" }, { "id": "MAR-SG-09", "kind": "Machine Answerability Remediation safeguard", "label": "Operator-view and intervention capture", "path": "/answerability-remediation.php#safeguard-operator-view-capture" }, { "id": "MAR-SG-08", "kind": "Machine Answerability Remediation safeguard", "label": "Pre-commit evidence and review window", "path": "/answerability-remediation.php#safeguard-effective-stop-before-commit" }, { "id": "MAR-H-EV-JUDGMENT", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Meaningful Human Judgment", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" } ] }, { "id": "evulgare-uncertainty", "title": "Uncertainty Architecture", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/uncertainty", "type": "First-party live product-area description", "supports": "The public uncertainty model separating aleatoric and epistemic uncertainty, distribution status, evidence completeness, source dependence, and model disagreement. It does not validate any external model’s uncertainty estimates.", "review": { "source_id": "evulgare-uncertainty", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E02", "kind": "Accountability Handoff evidence requirement", "label": "Model and calibration version", "path": "/accountability-handoff.php#evidence-AH-E02" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "confidence-evidence-quality", "kind": "Concept Matrix production handoff", "label": "Model confidence versus evidence quality", "path": "/concept-matrix.php#concept-confidence-evidence-quality" }, { "id": "predictive-inference", "kind": "Concept Matrix production handoff", "label": "Predictive inference", "path": "/concept-matrix.php#concept-predictive-inference" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "correlation-versus-common-cause", "kind": "FAQ answer", "label": "Do correlated symptoms or a shared cohort prove a common cause?", "path": "/faq.php#correlation-versus-common-cause" }, { "id": "monitoring-signal-versus-verified-regression", "kind": "FAQ answer", "label": "Does a monitoring alert prove that a corrective action regressed?", "path": "/faq.php#monitoring-signal-versus-verified-regression" }, { "id": "synthetic-alert-test-production-safety", "kind": "FAQ answer", "label": "Does a passed synthetic alert-path test prove production safety or factual truth?", "path": "/faq.php#synthetic-alert-test-production-safety" }, { "id": "recurrence-count-versus-rate", "kind": "FAQ answer", "label": "Does counting recurrence observations create a recurrence rate or risk estimate?", "path": "/faq.php#recurrence-count-versus-rate" }, { "id": "no-observed-recurrence-versus-disproof", "kind": "FAQ answer", "label": "Does no observed recurrence in a selected sample disprove recurrence?", "path": "/faq.php#no-observed-recurrence-versus-disproof" }, { "id": "one-retest-pass-versus-durable-nonrecurrence", "kind": "FAQ answer", "label": "Does one successful same-fixture retest prove durable non-recurrence?", "path": "/faq.php#one-retest-pass-versus-durable-nonrecurrence" }, { "id": "bounded-pattern-cohort", "kind": "Glossary term", "label": "Bounded pattern cohort", "path": "/glossary.php#bounded-pattern-cohort" }, { "id": "recurrence-classification", "kind": "Glossary term", "label": "Recurrence classification", "path": "/glossary.php#recurrence-classification" }, { "id": "regression-signal", "kind": "Glossary term", "label": "Regression signal", "path": "/glossary.php#regression-signal" }, { "id": "same-fixture-retest", "kind": "Glossary term", "label": "Same-fixture retest", "path": "/glossary.php#same-fixture-retest" }, { "id": "synthetic-alert-path-mechanics", "kind": "Glossary term", "label": "Synthetic alert-path mechanics", "path": "/glossary.php#synthetic-alert-path-mechanics" }, { "id": "systemic-pattern-support", "kind": "Glossary term", "label": "Systemic-pattern support", "path": "/glossary.php#systemic-pattern-support" }, { "id": "typed-recurrence-event-count", "kind": "Glossary term", "label": "Typed recurrence event count", "path": "/glossary.php#typed-recurrence-event-count" }, { "id": "AAC-CL-02", "kind": "Machine Answerability Assurance claim", "label": "Model remains inside envelope", "path": "/answerability-assurance.php#assurance-claim-model-envelope" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "AEC-CT-02", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-02", "path": "/answerability-contract.php#evidence-contract-aec-ct-02" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-02", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-02", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-05", "kind": "Machine Answerability Remediation safeguard", "label": "Calibration and envelope monitor", "path": "/answerability-remediation.php#safeguard-calibration-drift-monitor" }, { "id": "MAR-SG-04", "kind": "Machine Answerability Remediation safeguard", "label": "Distribution-shift abstention gate", "path": "/answerability-remediation.php#safeguard-uncertainty-distribution-hold" }, { "id": "MAR-H-EV-UNCERTAINTY", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Uncertainty Architecture", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" } ] }, { "id": "evulgare-trust", "title": "Federated Trust", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/trust", "type": "First-party live product-area description", "supports": "The public trust model treating identity, data integrity, semantic compatibility, disclosure, permitted use, and authority as separate dimensions. It does not prove that a connected source is trustworthy or authorized.", "review": { "source_id": "evulgare-trust", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E04", "kind": "Accountability Handoff evidence requirement", "label": "Three apparent confirmations", "path": "/accountability-handoff.php#evidence-AH-E04" }, { "id": "source-independence", "kind": "Concept Matrix production handoff", "label": "Source independence", "path": "/concept-matrix.php#concept-source-independence" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "AAC-CL-05", "kind": "Machine Answerability Assurance claim", "label": "Degraded path remains bounded", "path": "/answerability-assurance.php#assurance-claim-degraded-path" }, { "id": "AAC-CL-01", "kind": "Machine Answerability Assurance claim", "label": "Independent, traceable evidence", "path": "/answerability-assurance.php#assurance-claim-source-independence" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-011", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Independent-review action remains unowned", "path": "/answerability-effectiveness.php?audit=MAE-AUD-011" }, { "id": "MAE-AUD-009", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Provenance dispute closed with continuing exposure", "path": "/answerability-effectiveness.php?audit=MAE-AUD-009" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-012", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Evidence-access loss reopens a provenance closure", "path": "/answerability-monitoring.php?branch=MAM-BR-012" }, { "id": "MAM-BR-014", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Unowned monitoring duty remains no authority to infer", "path": "/answerability-monitoring.php?branch=MAM-BR-014" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "MAVD-RESULT-C93BE5527E82", "kind": "Machine Answerability Coverage Validation drill", "label": "Ceremonial acknowledgment failure", "path": "/answerability-validation.php?preset=MAVD-PRESET-CEREMONIAL-ACKNOWLEDGMENT" }, { "id": "machine-answerability-coverage-validation", "kind": "Machine Answerability Coverage Validation publication", "label": "Machine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill", "path": "/answerability-validation.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-008", "kind": "Machine Answerability Dispute Ledger record", "label": "Producer-controlled verification challenge remains unresolved", "path": "/answerability-disputes.php?record=MAD-DSP-008" }, { "id": "MAD-DSP-007", "kind": "Machine Answerability Dispute Ledger record", "label": "Revalidated provenance claim closed with residual unknowns", "path": "/answerability-disputes.php?record=MAD-DSP-007" }, { "id": "AEC-CT-01", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-01", "path": "/answerability-contract.php#evidence-contract-aec-ct-01" }, { "id": "AEC-CT-05", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-05", "path": "/answerability-contract.php#evidence-contract-aec-ct-05" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-01", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-01", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-05", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-05", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAPR-RESULT-B9AA7DDDFF63", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Correlated transport symptoms with common cause unproven", "path": "/answerability-patterns.php?preset=MAPR-PRESET-CORRELATED-TRANSPORT-COMMON-CAUSE-UNPROVEN" }, { "id": "MAPR-RESULT-F503CEC14915", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "No observed recurrence in a sparse selected sample", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SPARSE-NO-OBSERVED-RECURRENCE" }, { "id": "MAPR-RESULT-9DD2829BDCC2", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Repeated same-stage, same-fixture recurrence", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SAME-STAGE-SAME-FIXTURE-RECURRENCE" }, { "id": "machine-answerability-exception-recurrence-pattern-review", "kind": "Machine Answerability Exception Recurrence Pattern Review publication", "label": "Machine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review", "path": "/answerability-patterns.php" }, { "id": "MAC-BR-012", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Alert reviewed without access to underlying evidence", "path": "/answerability-coverage.php?branch=MAC-BR-012" }, { "id": "MAC-BR-014", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Monitoring duties have no competent institutional owner", "path": "/answerability-coverage.php?branch=MAC-BR-014" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-01", "kind": "Machine Answerability Remediation safeguard", "label": "Independent-source quorum", "path": "/answerability-remediation.php#safeguard-independent-source-gate" }, { "id": "MAR-SG-11", "kind": "Machine Answerability Remediation safeguard", "label": "Safe-hold degraded mode", "path": "/answerability-remediation.php#safeguard-lost-review-path-safe-hold" }, { "id": "MAR-SG-02", "kind": "Machine Answerability Remediation safeguard", "label": "Shared-dependency alarm", "path": "/answerability-remediation.php#safeguard-dependency-alarm" }, { "id": "MAR-SG-13", "kind": "Machine Answerability Remediation safeguard", "label": "Verified alternate review path", "path": "/answerability-remediation.php#safeguard-alternate-review-path" }, { "id": "MAR-H-EV-TRUST", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Federated Trust", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" }, { "id": "MAER-RESULT-3AC98EAF1C6B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Ownerless exception escalation", "path": "/answerability-retest.php?preset=MAER-PRESET-OWNERLESS-ESCALATION" }, { "id": "MAER-RESULT-9748DE4E576B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Recurring transport and deduplication failure", "path": "/answerability-retest.php?preset=MAER-PRESET-RECURRING-TRANSPORT-DEDUP" }, { "id": "MAER-RESULT-034FF9A56113", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Successful independent same-fixture retest", "path": "/answerability-retest.php?preset=MAER-PRESET-SUCCESSFUL-SAME-FIXTURE" }, { "id": "machine-answerability-validation-exception-retest", "kind": "Machine Answerability Validation Exception and Retest publication", "label": "Machine Answerability Validation Exception, Retest, and Escalation Ledger", "path": "/answerability-retest.php" } ] }, { "id": "evulgare-resilience", "title": "Resilience", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/resilience", "type": "First-party live product-area description", "supports": "The public resilience model for partitions, shared dependencies, stale evidence, integrity failures, safe holds, quarantine, and reconciliation. It does not establish the resilience of a deployed third-party system.", "review": { "source_id": "evulgare-resilience", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E09", "kind": "Accountability Handoff evidence requirement", "label": "Lost-link fallback and alternate path", "path": "/accountability-handoff.php#evidence-AH-E09" }, { "id": "communications-loss", "kind": "Concept Matrix production handoff", "label": "Communications loss", "path": "/concept-matrix.php#concept-communications-loss" }, { "id": "safe-state", "kind": "Concept Matrix production handoff", "label": "Safe-state behavior", "path": "/concept-matrix.php#concept-safe-state" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "safeguard-effect-classification", "kind": "FAQ answer", "label": "Does a safeguard labeled “prevent” prove that it will prevent a real incident?", "path": "/faq.php#safeguard-effect-classification" }, { "id": "AAC-CL-05", "kind": "Machine Answerability Assurance claim", "label": "Degraded path remains bounded", "path": "/answerability-assurance.php#assurance-claim-degraded-path" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "AEC-CT-05", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-05", "path": "/answerability-contract.php#evidence-contract-aec-ct-05" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-05", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-05", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-12", "kind": "Machine Answerability Remediation safeguard", "label": "Reversible commit stage", "path": "/answerability-remediation.php#safeguard-reversible-commit-stage" }, { "id": "MAR-SG-11", "kind": "Machine Answerability Remediation safeguard", "label": "Safe-hold degraded mode", "path": "/answerability-remediation.php#safeguard-lost-review-path-safe-hold" }, { "id": "MAR-SG-13", "kind": "Machine Answerability Remediation safeguard", "label": "Verified alternate review path", "path": "/answerability-remediation.php#safeguard-alternate-review-path" }, { "id": "MAR-H-EV-RESILIENCE", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Resilience", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" } ] }, { "id": "evulgare-change-impact", "title": "Change Impact", "publisher": "Evulgare", "date": "live page reviewed 2026-08-04", "url": "https://evulgare.com/platform/change-impact", "type": "First-party live product-area description", "supports": "The public change-impact model for tracing which claims, evidence, assumptions, interfaces, and verification activities are affected by software, model, dataset, policy, compiler, or environment changes. It does not automatically invalidate or revalidate a real system.", "review": { "source_id": "evulgare-change-impact", "last_reviewed_on": "2026-08-07", "next_review_due_on": "2026-11-05", "review_interval_days": 90, "review_state": "current", "link_state": "reachable_at_last_review", "link_checked_on": "2026-08-05", "retained_for_history": false, "superseded_by": null, "correction_notice_id": null, "reviewer_role": "KillChains.com editorial review", "review_note": "The registry record was reviewed for attribution, source class, date, and bounded support. External reachability was not tested in this release.", "verify_before_use": [ "Confirm that the bounded support statement still matches the cited source." ], "evidence_paths": [ "data/sources.php", "tests/source-review-audit.py", "docs/long-term-memory/implementation-history/source-review-center-v1.14.0.md" ] }, "dependencies": [ { "id": "AH-E03", "kind": "Accountability Handoff evidence requirement", "label": "Software and configuration fingerprint", "path": "/accountability-handoff.php#evidence-AH-E03" }, { "id": "accountability-handoff-lab", "kind": "Accountability Handoff publication", "label": "Machine Answerability and Accountability Handoff Lab", "path": "/accountability-handoff.php" }, { "id": "correction-supersession", "kind": "Concept Matrix production handoff", "label": "Correction and supersession", "path": "/concept-matrix.php#concept-correction-supersession" }, { "id": "evulgare", "kind": "Ecosystem identity", "label": "Evulgare", "path": "/ecosystem.php#evulgare-role" }, { "id": "changed-retest-fixture-comparability", "kind": "FAQ answer", "label": "Can a changed retest fixture be compared as though it were the original fixture?", "path": "/faq.php#changed-retest-fixture-comparability" }, { "id": "monitor-health-versus-monitor-scope", "kind": "FAQ answer", "label": "Does a healthy monitor prove that it watches the right system state?", "path": "/faq.php#monitor-health-versus-monitor-scope" }, { "id": "effectiveness-closure-residual-exposure", "kind": "FAQ answer", "label": "Does closing an effectiveness audit eliminate residual exposure or authorize a real system?", "path": "/faq.php#effectiveness-closure-residual-exposure" }, { "id": "corrective-action-versus-history", "kind": "FAQ answer", "label": "Does corrective action erase the earlier claim or review packet?", "path": "/faq.php#corrective-action-versus-history" }, { "id": "monitoring-silence-versus-safety", "kind": "FAQ answer", "label": "Does monitoring silence prove that a corrective action remains safe or effective?", "path": "/faq.php#monitoring-silence-versus-safety" }, { "id": "no-observed-recurrence-versus-disproof", "kind": "FAQ answer", "label": "Does no observed recurrence in a selected sample disprove recurrence?", "path": "/faq.php#no-observed-recurrence-versus-disproof" }, { "id": "one-retest-pass-versus-durable-nonrecurrence", "kind": "FAQ answer", "label": "Does one successful same-fixture retest prove durable non-recurrence?", "path": "/faq.php#one-retest-pass-versus-durable-nonrecurrence" }, { "id": "reopened-audit-versus-erased-history", "kind": "FAQ answer", "label": "Does reopening and revalidating an audit erase the earlier invalidation or assign responsibility?", "path": "/faq.php#reopened-audit-versus-erased-history" }, { "id": "remediation-selected-versus-implemented", "kind": "FAQ answer", "label": "Does selecting or configuring a monitoring remediation prove that it was implemented and tested?", "path": "/faq.php#remediation-selected-versus-implemented" }, { "id": "concept-to-production-handoff", "kind": "FAQ answer", "label": "How does a KillChains.com concept become a production-accountability requirement?", "path": "/faq.php#concept-to-production-handoff" }, { "id": "review-ownership", "kind": "FAQ answer", "label": "What does review ownership mean for a consequential machine decision?", "path": "/faq.php#review-ownership" }, { "id": "machine-answerability-remediation", "kind": "FAQ answer", "label": "What does the Machine Answerability Remediation Lab test?", "path": "/faq.php#machine-answerability-remediation" }, { "id": "corrective-action-effectiveness-audit", "kind": "FAQ answer", "label": "What is a corrective-action effectiveness audit?", "path": "/faq.php#corrective-action-effectiveness-audit" }, { "id": "machine-answerability-assurance-case", "kind": "FAQ answer", "label": "What is a machine-answerability assurance case?", "path": "/faq.php#machine-answerability-assurance-case" }, { "id": "assurance-review-packet", "kind": "FAQ answer", "label": "What is a machine-answerability assurance review packet?", "path": "/faq.php#assurance-review-packet" }, { "id": "corrective-action-monitoring-regression-reopening", "kind": "FAQ answer", "label": "What is corrective-action monitoring, regression, and reopening?", "path": "/faq.php#corrective-action-monitoring-regression-reopening" }, { "id": "machine-answerability-replay", "kind": "FAQ answer", "label": "What is the Machine Answerability Replay?", "path": "/faq.php#machine-answerability-replay" }, { "id": "assurance-invalidation", "kind": "FAQ answer", "label": "When should an assurance claim be suspended or withdrawn?", "path": "/faq.php#assurance-invalidation" }, { "id": "assurance-version-diff", "kind": "FAQ answer", "label": "Why compare version-bound assurance snapshots?", "path": "/faq.php#assurance-version-diff" }, { "id": "assurance-defeater", "kind": "Glossary term", "label": "Assurance defeater", "path": "/glossary.php#assurance-defeater" }, { "id": "assurance-invalidation-gate", "kind": "Glossary term", "label": "Assurance invalidation gate", "path": "/glossary.php#assurance-invalidation-gate" }, { "id": "assurance-snapshot", "kind": "Glossary term", "label": "Assurance snapshot", "path": "/glossary.php#assurance-snapshot" }, { "id": "assurance-state", "kind": "Glossary term", "label": "Assurance state", "path": "/glossary.php#assurance-state" }, { "id": "assurance-version-diff", "kind": "Glossary term", "label": "Assurance version diff", "path": "/glossary.php#assurance-version-diff" }, { "id": "corrective-action-ledger", "kind": "Glossary term", "label": "Corrective action ledger", "path": "/glossary.php#corrective-action-ledger" }, { "id": "corrective-action-effectiveness-audit", "kind": "Glossary term", "label": "Corrective-action effectiveness audit", "path": "/glossary.php#corrective-action-effectiveness-audit" }, { "id": "corrective-action-monitoring", "kind": "Glossary term", "label": "Corrective-action monitoring", "path": "/glossary.php#corrective-action-monitoring" }, { "id": "coverage-remediation-validation-drill", "kind": "Glossary term", "label": "Coverage remediation validation drill", "path": "/glossary.php#coverage-remediation-validation-drill" }, { "id": "evidence-deficiency-report", "kind": "Glossary term", "label": "Evidence-deficiency report", "path": "/glossary.php#evidence-deficiency-report" }, { "id": "immutable-audit-reopening", "kind": "Glossary term", "label": "Immutable audit reopening", "path": "/glossary.php#immutable-audit-reopening" }, { "id": "answerability-remediation", "kind": "Glossary term", "label": "Machine answerability remediation", "path": "/glossary.php#answerability-remediation" }, { "id": "monitoring-blind-spot", "kind": "Glossary term", "label": "Monitoring blind spot", "path": "/glossary.php#monitoring-blind-spot" }, { "id": "monitoring-coverage", "kind": "Glossary term", "label": "Monitoring coverage", "path": "/glossary.php#monitoring-coverage" }, { "id": "recurrence-classification", "kind": "Glossary term", "label": "Recurrence classification", "path": "/glossary.php#recurrence-classification" }, { "id": "residual-exposure", "kind": "Glossary term", "label": "Residual exposure", "path": "/glossary.php#residual-exposure" }, { "id": "review-ownership", "kind": "Glossary term", "label": "Review ownership", "path": "/glossary.php#review-ownership" }, { "id": "synthetic-alert-path-mechanics", "kind": "Glossary term", "label": "Synthetic alert-path mechanics", "path": "/glossary.php#synthetic-alert-path-mechanics" }, { "id": "validation-exception-branch", "kind": "Glossary term", "label": "Validation exception branch", "path": "/glossary.php#validation-exception-branch" }, { "id": "AAC-CL-06", "kind": "Machine Answerability Assurance claim", "label": "Configuration is identified and revalidated", "path": "/answerability-assurance.php#assurance-claim-configuration" }, { "id": "AAC-CL-07", "kind": "Machine Answerability Assurance claim", "label": "Stale assurance is automatically suspended", "path": "/answerability-assurance.php#assurance-claim-continuous-invalidation" }, { "id": "machine-answerability-assurance", "kind": "Machine Answerability Assurance publication", "label": "Machine Answerability Assurance Case and Invalidation Lab", "path": "/answerability-assurance.php" }, { "id": "machine-answerability-assurance-review", "kind": "Machine Answerability Assurance Review publication", "label": "Machine Answerability Assurance Review Packet and Version-Diff Lab", "path": "/answerability-review.php" }, { "id": "AARP-SNAP-005", "kind": "Machine Answerability Assurance Review snapshot", "label": "Authority gap", "path": "/answerability-review.php#snapshot-aarp-snap-005" }, { "id": "AARP-SNAP-001", "kind": "Machine Answerability Assurance Review snapshot", "label": "Baseline", "path": "/answerability-review.php#snapshot-aarp-snap-001" }, { "id": "AARP-SNAP-003", "kind": "Machine Answerability Assurance Review snapshot", "label": "Configuration change", "path": "/answerability-review.php#snapshot-aarp-snap-003" }, { "id": "AARP-SNAP-004", "kind": "Machine Answerability Assurance Review snapshot", "label": "Interface change", "path": "/answerability-review.php#snapshot-aarp-snap-004" }, { "id": "AARP-SNAP-002", "kind": "Machine Answerability Assurance Review snapshot", "label": "Model change", "path": "/answerability-review.php#snapshot-aarp-snap-002" }, { "id": "AARP-SNAP-006", "kind": "Machine Answerability Assurance Review snapshot", "label": "Revalidated", "path": "/answerability-review.php#snapshot-aarp-snap-006" }, { "id": "MAE-AUD-010", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Append-oriented custody independently verified for the corrected packet", "path": "/answerability-effectiveness.php?audit=MAE-AUD-010" }, { "id": "MAE-AUD-003", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Changed-model records produced but not independently verified", "path": "/answerability-effectiveness.php?audit=MAE-AUD-003" }, { "id": "MAE-AUD-007", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Corrected configuration claim invalidated by a later threshold change", "path": "/answerability-effectiveness.php?audit=MAE-AUD-007" }, { "id": "MAE-AUD-002", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Custody restoration marked implemented without technical proof", "path": "/answerability-effectiveness.php?audit=MAE-AUD-002" }, { "id": "MAE-AUD-001", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Evidence request exists only as a plan", "path": "/answerability-effectiveness.php?audit=MAE-AUD-001" }, { "id": "MAE-AUD-006", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Produced evidence found ineffective for the calibration gap", "path": "/answerability-effectiveness.php?audit=MAE-AUD-006" }, { "id": "MAE-AUD-004", "kind": "Machine Answerability Corrective Action Effectiveness audit", "label": "Suspension gate independently verified for the changed-model branch", "path": "/answerability-effectiveness.php?audit=MAE-AUD-004" }, { "id": "machine-answerability-effectiveness", "kind": "Machine Answerability Corrective Action Effectiveness publication", "label": "Machine Answerability Corrective Action Effectiveness and Closure Audit Lab", "path": "/answerability-effectiveness.php" }, { "id": "MAM-BR-017", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "A closed ticket cannot supply a monitoring baseline", "path": "/answerability-monitoring.php?branch=MAM-BR-017" }, { "id": "MAM-BR-016", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "A planned action has no effectiveness baseline to monitor", "path": "/answerability-monitoring.php?branch=MAM-BR-016" }, { "id": "MAM-BR-005", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Assurance monitor failure forces suspension and reopening", "path": "/answerability-monitoring.php?branch=MAM-BR-005" }, { "id": "MAM-BR-003", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Calibration drift signal observed but not independently verified", "path": "/answerability-monitoring.php?branch=MAM-BR-003" }, { "id": "MAM-BR-004", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Calibration regression independently verified", "path": "/answerability-monitoring.php?branch=MAM-BR-004" }, { "id": "MAM-BR-013", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Custody control remains current after scheduled verification", "path": "/answerability-monitoring.php?branch=MAM-BR-013" }, { "id": "MAM-BR-009", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Monitoring cannot rescue an action already shown ineffective", "path": "/answerability-monitoring.php?branch=MAM-BR-009" }, { "id": "MAM-BR-006", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Monitoring restored; independent revalidation still pending", "path": "/answerability-monitoring.php?branch=MAM-BR-006" }, { "id": "MAM-BR-018", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Producer records remain insufficient for durable monitoring without independent verification", "path": "/answerability-monitoring.php?branch=MAM-BR-018" }, { "id": "MAM-BR-007", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Remediated suspension gate independently revalidated and reclosed", "path": "/answerability-monitoring.php?branch=MAM-BR-007" }, { "id": "MAM-BR-002", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Scheduled monitoring completed without a regression signal", "path": "/answerability-monitoring.php?branch=MAM-BR-002" }, { "id": "MAM-BR-001", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Suspension gate reaches its scheduled review date", "path": "/answerability-monitoring.php?branch=MAM-BR-001" }, { "id": "MAM-BR-010", "kind": "Machine Answerability Corrective Action Monitoring branch", "label": "Threshold mismatch verifies the need to reopen the corrected configuration", "path": "/answerability-monitoring.php?branch=MAM-BR-010" }, { "id": "machine-answerability-monitoring", "kind": "Machine Answerability Corrective Action Monitoring publication", "label": "Machine Answerability Corrective Action Monitoring, Regression, and Reopening Lab", "path": "/answerability-monitoring.php" }, { "id": "MAVD-RESULT-4E98173EEB2E", "kind": "Machine Answerability Coverage Validation drill", "label": "End-to-end alert-path validation", "path": "/answerability-validation.php?preset=MAVD-PRESET-END-TO-END" }, { "id": "machine-answerability-coverage-validation", "kind": "Machine Answerability Coverage Validation publication", "label": "Machine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill", "path": "/answerability-validation.php" }, { "id": "machine-answerability-dispute-ledger", "kind": "Machine Answerability Dispute Ledger publication", "label": "Machine Answerability Dispute Record and Corrective Action Ledger Lab", "path": "/answerability-disputes.php" }, { "id": "MAD-DSP-002", "kind": "Machine Answerability Dispute Ledger record", "label": "Changed model evidence produced and reliance suspended", "path": "/answerability-disputes.php?record=MAD-DSP-002" }, { "id": "MAD-DSP-005", "kind": "Machine Answerability Dispute Ledger record", "label": "Configuration claim corrected without erasing the earlier packet", "path": "/answerability-disputes.php?record=MAD-DSP-005" }, { "id": "MAD-DSP-001", "kind": "Machine Answerability Dispute Ledger record", "label": "Model-change evidence request remains open", "path": "/answerability-disputes.php?record=MAD-DSP-001" }, { "id": "AEC-CT-06", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-06", "path": "/answerability-contract.php#evidence-contract-aec-ct-06" }, { "id": "AEC-CT-07", "kind": "Machine Answerability Evidence Contract", "label": "AAC-CL-07", "path": "/answerability-contract.php#evidence-contract-aec-ct-07" }, { "id": "machine-answerability-evidence-contract", "kind": "Machine Answerability Evidence Contract publication", "label": "Machine Answerability Evidence Contract and Review Ownership Lab", "path": "/answerability-contract.php" }, { "id": "AEC-CT-06", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-06", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "AEC-CT-07", "kind": "Machine Answerability Evidence-Gap Escalation contract", "label": "AAC-CL-07", "path": "/answerability-escalation.php#evidence-gap-workspace" }, { "id": "machine-answerability-evidence-gap-escalation", "kind": "Machine Answerability Evidence-Gap Escalation publication", "label": "Machine Answerability Evidence-Gap Remediation and Dispute Escalation Lab", "path": "/answerability-escalation.php" }, { "id": "MAPR-RESULT-B9AA7DDDFF63", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Correlated transport symptoms with common cause unproven", "path": "/answerability-patterns.php?preset=MAPR-PRESET-CORRELATED-TRANSPORT-COMMON-CAUSE-UNPROVEN" }, { "id": "MAPR-RESULT-F503CEC14915", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "No observed recurrence in a sparse selected sample", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SPARSE-NO-OBSERVED-RECURRENCE" }, { "id": "MAPR-RESULT-9DD2829BDCC2", "kind": "Machine Answerability Exception Recurrence Pattern Review branch", "label": "Repeated same-stage, same-fixture recurrence", "path": "/answerability-patterns.php?preset=MAPR-PRESET-SAME-STAGE-SAME-FIXTURE-RECURRENCE" }, { "id": "machine-answerability-exception-recurrence-pattern-review", "kind": "Machine Answerability Exception Recurrence Pattern Review publication", "label": "Machine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review", "path": "/answerability-patterns.php" }, { "id": "MAC-BR-002", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Bounded coverage verified and no regression alert recorded", "path": "/answerability-coverage.php?branch=MAC-BR-002" }, { "id": "MAC-BR-010", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Configuration changed outside the monitored component", "path": "/answerability-coverage.php?branch=MAC-BR-010" }, { "id": "MAC-BR-007", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Coverage remediated and alert path independently tested", "path": "/answerability-coverage.php?branch=MAC-BR-007" }, { "id": "MAC-BR-005", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Disabled monitor creates false silence", "path": "/answerability-coverage.php?branch=MAC-BR-005" }, { "id": "MAC-BR-003", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Drift alert delivered but not reviewed", "path": "/answerability-coverage.php?branch=MAC-BR-003" }, { "id": "MAC-BR-018", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Drift alert lost during deduplication", "path": "/answerability-coverage.php?branch=MAC-BR-018" }, { "id": "MAC-BR-004", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Drift alert reviewed and regression independently verified", "path": "/answerability-coverage.php?branch=MAC-BR-004" }, { "id": "MAC-BR-006", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Monitor restored against a stale baseline", "path": "/answerability-coverage.php?branch=MAC-BR-006" }, { "id": "MAC-BR-016", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Monitoring compares an unknown source state with a stale baseline", "path": "/answerability-coverage.php?branch=MAC-BR-016" }, { "id": "MAC-BR-013", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Producer-controlled verification leaves independence unresolved", "path": "/answerability-coverage.php?branch=MAC-BR-013" }, { "id": "MAC-BR-009", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Quiet monitoring cannot convert an ineffective action into an effective control", "path": "/answerability-coverage.php?branch=MAC-BR-009" }, { "id": "MAC-BR-001", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Scheduled monitoring has no performed coverage record", "path": "/answerability-coverage.php?branch=MAC-BR-001" }, { "id": "MAC-BR-017", "kind": "Machine Answerability Monitoring Coverage branch", "label": "Silent provenance monitor misses a shared source dependency", "path": "/answerability-coverage.php?branch=MAC-BR-017" }, { "id": "machine-answerability-monitoring-coverage", "kind": "Machine Answerability Monitoring Coverage publication", "label": "Machine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab", "path": "/answerability-coverage.php" }, { "id": "machine-answerability-remediation", "kind": "Machine Answerability Remediation publication", "label": "Machine Answerability Remediation and Prevention Lab", "path": "/answerability-remediation.php" }, { "id": "MAR-SG-16", "kind": "Machine Answerability Remediation safeguard", "label": "Continuous assurance invalidation", "path": "/answerability-remediation.php#safeguard-material-change-assurance-invalidation" }, { "id": "MAR-SG-15", "kind": "Machine Answerability Remediation safeguard", "label": "Exact software and configuration manifest", "path": "/answerability-remediation.php#safeguard-exact-artifact-manifest" }, { "id": "MAR-SG-14", "kind": "Machine Answerability Remediation safeguard", "label": "Material-change revalidation gate", "path": "/answerability-remediation.php#safeguard-material-change-revalidation" }, { "id": "MAR-SG-18", "kind": "Machine Answerability Remediation safeguard", "label": "Named correction, suspension, and retirement owner", "path": "/answerability-remediation.php#safeguard-independent-reconstruction-correction-owner" }, { "id": "MAR-H-EV-CHANGE_IMPACT", "kind": "Machine Answerability Replay handoff", "label": "Evulgare Change Impact", "path": "/answerability-replay.php#production-answerability-handoff" }, { "id": "machine-answerability-replay", "kind": "Machine Answerability Replay publication", "label": "Machine Answerability Replay and Causal Contribution Lab", "path": "/answerability-replay.php" }, { "id": "MAER-RESULT-3AC98EAF1C6B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Ownerless exception escalation", "path": "/answerability-retest.php?preset=MAER-PRESET-OWNERLESS-ESCALATION" }, { "id": "MAER-RESULT-9748DE4E576B", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Recurring transport and deduplication failure", "path": "/answerability-retest.php?preset=MAER-PRESET-RECURRING-TRANSPORT-DEDUP" }, { "id": "MAER-RESULT-034FF9A56113", "kind": "Machine Answerability Validation Exception and Retest branch", "label": "Successful independent same-fixture retest", "path": "/answerability-retest.php?preset=MAER-PRESET-SUCCESSFUL-SAME-FIXTURE" }, { "id": "machine-answerability-validation-exception-retest", "kind": "Machine Answerability Validation Exception and Retest publication", "label": "Machine Answerability Validation Exception, Retest, and Escalation Ledger", "path": "/answerability-retest.php" } ] } ] }