Source Freshness & Correction Center

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipSaab → 9AIR C4I
• Technology providerSaab

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• FAQ answerIs model confidence the same as evidence quality or positive identification?
• FAQ answerWhat is an AI kill chain?
• Glossary termAI kill chain
• Glossary termModel confidence
• Machine Answerability Assurance claimModel remains inside envelope
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Evidence ContractAAC-CL-02
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-02
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Use for chronology only unless a current source separately establishes present status.

Where this source is used

• FAQ answerHow does place-based forecasting differ from person-based prediction?
• Glossary termPerson-based prediction
• Predictive Enforcement programStrategic Subject List and Crime and Victimization Risk Model

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipLockheed Martin → Aegis Combat System
• Technology providerLockheed Martin

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Company-system relationshipLockheed Martin → Aegis Combat System
• Technology providerLockheed Martin

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• FAQ answerWhy are humans removed from some immediate kill-chain functions?
• Human Control caseCollaborative Combat Aircraft

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Company-system relationshipAnduril Industries → Next-generation counter-UAS fire control
• Technology providerAnduril Industries

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Technology providerAnduril Industries

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipPalantir Technologies → Tactical Intelligence Targeting Access Node
• Technology providerPalantir Technologies

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Company-system relationshipPalantir Technologies → Tactical Intelligence Targeting Access Node
• FAQ answerHow can an algorithm shape a human decision without authorizing force?
• FAQ answerIs an AI-enabled kill chain the same as an autonomous weapon?
• Glossary termAI-enabled kill chain
• Glossary termSensor fusion
• Human Control caseTITAN
• Technology providerPalantir Technologies

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipAuterion → Skynode autonomy platform
• Technology providerAuterion

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipAuterion → Skynode autonomy platform
• Technology providerAuterion

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementDelegated authority envelope
• Accountability Handoff evidence requirementEffective override path
• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Concept Matrix production handoffHuman authorization
• Concept Matrix production handoffInstitutional authority
• Concept Matrix production handoffPreauthorization
• Ecosystem identityEvulgare
• FAQ answerDoes a complete assurance review packet authorize real-world operation?
• FAQ answerDoes acknowledging a validation exception mean an institution owns it?
• FAQ answerDoes closing a dispute establish certainty, legal responsibility, or operational release?
• FAQ answerDoes closing an effectiveness audit eliminate residual exposure or authorize a real system?
• FAQ answerHow does a KillChains.com concept become a production-accountability requirement?
• FAQ answerWhat does review ownership mean for a consequential machine decision?
• FAQ answerWhat does the Machine Answerability Remediation Lab test?
• FAQ answerWhat does “no authority to infer” mean?
• FAQ answerWhat is ceremonial human review?
• Glossary termCeremonial human review
• Glossary termNo authority to infer
• Glossary termOperational release authority
• Glossary termReview ownership
• Machine Answerability Assurance claimAuthority is current and enforced
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditRetired authority claim preserved with its replacement record
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchRetired authority claim remains retired after replacement monitoring
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Coverage Validation drillBlind-spot remediation challenge
• Machine Answerability Coverage Validation publicationMachine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordAuthority claim retired after the governing mandate changed
• Machine Answerability Evidence ContractAAC-CL-03
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-03
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Exception Recurrence Pattern Review branchCorrelated transport symptoms with common cause unproven
• Machine Answerability Exception Recurrence Pattern Review branchNo observed recurrence in a sparse selected sample
• Machine Answerability Exception Recurrence Pattern Review branchRepeated same-stage, same-fixture recurrence
• Machine Answerability Exception Recurrence Pattern Review publicationMachine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review
• Machine Answerability Monitoring Coverage branchReplacement control inherits an unmonitored shared dependency
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardAuthority scope and expiration pinning
• Machine Answerability Remediation safeguardContinuous assurance invalidation
• Machine Answerability Remediation safeguardDeterministic authority precondition gate
• Machine Answerability Remediation safeguardPre-commit evidence and review window
• Machine Answerability Remediation safeguardReversible commit stage
• Machine Answerability Replay handoffEvulgare Authority Boundaries
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab
• Machine Answerability Validation Exception and Retest branchOwnerless exception escalation
• Machine Answerability Validation Exception and Retest branchRecurring transport and deduplication failure
• Machine Answerability Validation Exception and Retest branchSuccessful independent same-fixture retest
• Machine Answerability Validation Exception and Retest publicationMachine Answerability Validation Exception, Retest, and Escalation Ledger

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Glossary termMeaningful human control

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipIsrael Aerospace Industries / ELTA → BARAK MX air and missile defense
• Technology providerIsrael Aerospace Industries / ELTA

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Claim Lineage recordFederal behavioral threat assessment is publicly described as case-specific professional judgment, not a national AI danger score.
• FAQ answerIs behavioral threat assessment the same as pre-crime scoring?
• Glossary termBehavioral threat assessment
• Predictive Enforcement programFederal behavioral threat assessment and management

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Claim Lineage recordFederal behavioral threat assessment is publicly described as case-specific professional judgment, not a national AI danger score.
• FAQ answerIs behavioral threat assessment the same as pre-crime scoring?
• Glossary termBehavioral threat assessment
• Predictive Enforcement programFederal behavioral threat assessment and management

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• FAQ answerWhat is the difference between a kill chain and a kill web?
• Glossary termKill web

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementSoftware and configuration fingerprint
• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Concept Matrix production handoffCorrection and supersession
• Ecosystem identityEvulgare
• FAQ answerCan a changed retest fixture be compared as though it were the original fixture?
• FAQ answerDoes a healthy monitor prove that it watches the right system state?
• FAQ answerDoes closing an effectiveness audit eliminate residual exposure or authorize a real system?
• FAQ answerDoes corrective action erase the earlier claim or review packet?
• FAQ answerDoes monitoring silence prove that a corrective action remains safe or effective?
• FAQ answerDoes no observed recurrence in a selected sample disprove recurrence?
• FAQ answerDoes one successful same-fixture retest prove durable non-recurrence?
• FAQ answerDoes reopening and revalidating an audit erase the earlier invalidation or assign responsibility?
• FAQ answerDoes selecting or configuring a monitoring remediation prove that it was implemented and tested?
• FAQ answerHow does a KillChains.com concept become a production-accountability requirement?
• FAQ answerWhat does review ownership mean for a consequential machine decision?
• FAQ answerWhat does the Machine Answerability Remediation Lab test?
• FAQ answerWhat is a corrective-action effectiveness audit?
• FAQ answerWhat is a machine-answerability assurance case?
• FAQ answerWhat is a machine-answerability assurance review packet?
• FAQ answerWhat is corrective-action monitoring, regression, and reopening?
• FAQ answerWhat is the Machine Answerability Replay?
• FAQ answerWhen should an assurance claim be suspended or withdrawn?
• FAQ answerWhy compare version-bound assurance snapshots?
• Glossary termAssurance defeater
• Glossary termAssurance invalidation gate
• Glossary termAssurance snapshot
• Glossary termAssurance state
• Glossary termAssurance version diff
• Glossary termCorrective action ledger
• Glossary termCorrective-action effectiveness audit
• Glossary termCorrective-action monitoring
• Glossary termCoverage remediation validation drill
• Glossary termEvidence-deficiency report
• Glossary termImmutable audit reopening
• Glossary termMachine answerability remediation
• Glossary termMonitoring blind spot
• Glossary termMonitoring coverage
• Glossary termRecurrence classification
• Glossary termResidual exposure
• Glossary termReview ownership
• Glossary termSynthetic alert-path mechanics
• Glossary termValidation exception branch
• Machine Answerability Assurance claimConfiguration is identified and revalidated
• Machine Answerability Assurance claimStale assurance is automatically suspended
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditAppend-oriented custody independently verified for the corrected packet
• Machine Answerability Corrective Action Effectiveness auditChanged-model records produced but not independently verified
• Machine Answerability Corrective Action Effectiveness auditCorrected configuration claim invalidated by a later threshold change
• Machine Answerability Corrective Action Effectiveness auditCustody restoration marked implemented without technical proof
• Machine Answerability Corrective Action Effectiveness auditEvidence request exists only as a plan
• Machine Answerability Corrective Action Effectiveness auditProduced evidence found ineffective for the calibration gap
• Machine Answerability Corrective Action Effectiveness auditSuspension gate independently verified for the changed-model branch
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchA closed ticket cannot supply a monitoring baseline
• Machine Answerability Corrective Action Monitoring branchA planned action has no effectiveness baseline to monitor
• Machine Answerability Corrective Action Monitoring branchAssurance monitor failure forces suspension and reopening
• Machine Answerability Corrective Action Monitoring branchCalibration drift signal observed but not independently verified
• Machine Answerability Corrective Action Monitoring branchCalibration regression independently verified
• Machine Answerability Corrective Action Monitoring branchCustody control remains current after scheduled verification
• Machine Answerability Corrective Action Monitoring branchMonitoring cannot rescue an action already shown ineffective
• Machine Answerability Corrective Action Monitoring branchMonitoring restored; independent revalidation still pending
• Machine Answerability Corrective Action Monitoring branchProducer records remain insufficient for durable monitoring without independent verification
• Machine Answerability Corrective Action Monitoring branchRemediated suspension gate independently revalidated and reclosed
• Machine Answerability Corrective Action Monitoring branchScheduled monitoring completed without a regression signal
• Machine Answerability Corrective Action Monitoring branchSuspension gate reaches its scheduled review date
• Machine Answerability Corrective Action Monitoring branchThreshold mismatch verifies the need to reopen the corrected configuration
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Coverage Validation drillEnd-to-end alert-path validation
• Machine Answerability Coverage Validation publicationMachine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordChanged model evidence produced and reliance suspended
• Machine Answerability Dispute Ledger recordConfiguration claim corrected without erasing the earlier packet
• Machine Answerability Dispute Ledger recordModel-change evidence request remains open
• Machine Answerability Evidence ContractAAC-CL-06
• Machine Answerability Evidence ContractAAC-CL-07
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-06
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-07
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Exception Recurrence Pattern Review branchCorrelated transport symptoms with common cause unproven
• Machine Answerability Exception Recurrence Pattern Review branchNo observed recurrence in a sparse selected sample
• Machine Answerability Exception Recurrence Pattern Review branchRepeated same-stage, same-fixture recurrence
• Machine Answerability Exception Recurrence Pattern Review publicationMachine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review
• Machine Answerability Monitoring Coverage branchBounded coverage verified and no regression alert recorded
• Machine Answerability Monitoring Coverage branchConfiguration changed outside the monitored component
• Machine Answerability Monitoring Coverage branchCoverage remediated and alert path independently tested
• Machine Answerability Monitoring Coverage branchDisabled monitor creates false silence
• Machine Answerability Monitoring Coverage branchDrift alert delivered but not reviewed
• Machine Answerability Monitoring Coverage branchDrift alert lost during deduplication
• Machine Answerability Monitoring Coverage branchDrift alert reviewed and regression independently verified
• Machine Answerability Monitoring Coverage branchMonitor restored against a stale baseline
• Machine Answerability Monitoring Coverage branchMonitoring compares an unknown source state with a stale baseline
• Machine Answerability Monitoring Coverage branchProducer-controlled verification leaves independence unresolved
• Machine Answerability Monitoring Coverage branchQuiet monitoring cannot convert an ineffective action into an effective control
• Machine Answerability Monitoring Coverage branchScheduled monitoring has no performed coverage record
• Machine Answerability Monitoring Coverage branchSilent provenance monitor misses a shared source dependency
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardContinuous assurance invalidation
• Machine Answerability Remediation safeguardExact software and configuration manifest
• Machine Answerability Remediation safeguardMaterial-change revalidation gate
• Machine Answerability Remediation safeguardNamed correction, suspension, and retirement owner
• Machine Answerability Replay handoffEvulgare Change Impact
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab
• Machine Answerability Validation Exception and Retest branchOwnerless exception escalation
• Machine Answerability Validation Exception and Retest branchRecurring transport and deduplication failure
• Machine Answerability Validation Exception and Retest branchSuccessful independent same-fixture retest
• Machine Answerability Validation Exception and Retest publicationMachine Answerability Validation Exception, Retest, and Escalation Ledger

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Authority Casebook caseCollaborative Combat Aircraft
• Claim Lineage recordThe Air Force says humans retain CCA weapon-release authority in the described testing context.
• Evidence Lab cardThe 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.
• FAQ answerDoes operational delegation give a machine legal authority?
• FAQ answerWhat does institutional authority mean in an AI-mediated decision chain?
• Glossary termInstitutional authority
• Glossary termOperational delegation
• Human Control caseCollaborative Combat Aircraft

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipBAE Systems → INTeACT combat-management software
• Technology providerBAE Systems

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipLeonardo → Leonardo command-and-control systems
• Technology providerLeonardo

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementAssurance claim after a material update
• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Concept Matrix production handoffMachine execution
• Ecosystem identityEvulgare
• FAQ answerCan a changed retest fixture be compared as though it were the original fixture?
• FAQ answerDo correlated symptoms or a shared cohort prove a common cause?
• FAQ answerDoes a closed ticket or human sign-off prove that a corrective action worked?
• FAQ answerDoes a complete assurance review packet authorize real-world operation?
• FAQ answerDoes a healthy monitor prove that it watches the right system state?
• FAQ answerDoes a monitoring alert prove that a corrective action regressed?
• FAQ answerDoes a passed synthetic alert-path test prove production safety or factual truth?
• FAQ answerDoes a safeguard labeled “prevent” prove that it will prevent a real incident?
• FAQ answerDoes a signed or hashed evidence record prove that an assurance claim is true?
• FAQ answerDoes acknowledging a validation exception mean an institution owns it?
• FAQ answerDoes adding more evidence change what happened in the replay?
• FAQ answerDoes alert delivery prove that a regression was reviewed and verified?
• FAQ answerDoes closing a dispute establish certainty, legal responsibility, or operational release?
• FAQ answerDoes closing an effectiveness audit eliminate residual exposure or authorize a real system?
• FAQ answerDoes counting recurrence observations create a recurrence rate or risk estimate?
• FAQ answerDoes monitoring silence prove that a corrective action remains safe or effective?
• FAQ answerDoes no observed recurrence in a selected sample disprove recurrence?
• FAQ answerDoes one successful same-fixture retest prove durable non-recurrence?
• FAQ answerDoes reopening and revalidating an audit erase the earlier invalidation or assign responsibility?
• FAQ answerDoes selecting or configuring a monitoring remediation prove that it was implemented and tested?
• FAQ answerIs acknowledging an alert the same as competent review and independent verification?
• FAQ answerWhat does review ownership mean for a consequential machine decision?
• FAQ answerWhat does the Machine Answerability Remediation Lab test?
• FAQ answerWhat does “no authority to infer” mean?
• FAQ answerWhat is a corrective-action effectiveness audit?
• FAQ answerWhat is a machine-answerability assurance case?
• FAQ answerWhat is a machine-answerability assurance review packet?
• FAQ answerWhat is a machine-answerability dispute record?
• FAQ answerWhat is a machine-answerability evidence contract?
• FAQ answerWhat is corrective-action monitoring, regression, and reopening?
• FAQ answerWhat is machine-answerability evidence-gap remediation?
• FAQ answerWhen should an assurance claim be suspended or withdrawn?
• FAQ answerWhy compare version-bound assurance snapshots?
• Glossary termAlert integrity
• Glossary termAssurance case
• Glossary termAssurance defeater
• Glossary termAssurance invalidation gate
• Glossary termAssurance review packet
• Glossary termAssurance snapshot
• Glossary termAssurance state
• Glossary termAssurance version diff
• Glossary termBounded pattern cohort
• Glossary termCeremonial alert acknowledgment
• Glossary termClosure with residual unknowns
• Glossary termCorrective-action effectiveness audit
• Glossary termCorrective-action monitoring
• Glossary termCoverage remediation validation drill
• Glossary termEffectiveness unknown
• Glossary termEvidence integrity versus factual support
• Glossary termEvidence-deficiency report
• Glossary termEvidence-gap remediation
• Glossary termMachine answerability remediation
• Glossary termMachine-answerability dispute record
• Glossary termMachine-answerability evidence contract
• Glossary termMonitoring blind spot
• Glossary termMonitoring coverage
• Glossary termOperational release authority
• Glossary termRecurrence classification
• Glossary termRegression signal
• Glossary termResidual exposure
• Glossary termReview ownership
• Glossary termSame-fixture retest
• Glossary termSeparation of duties
• Glossary termSynthetic alert-path mechanics
• Glossary termSystemic-pattern support
• Glossary termTyped recurrence event count
• Glossary termValidation exception branch
• Machine Answerability Assurance claimConfiguration is identified and revalidated
• Machine Answerability Assurance claimModel remains inside envelope
• Machine Answerability Assurance claimStale assurance is automatically suspended
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditAppend-oriented custody independently verified for the corrected packet
• Machine Answerability Corrective Action Effectiveness auditChanged-model records produced but not independently verified
• Machine Answerability Corrective Action Effectiveness auditCorrected configuration claim invalidated by a later threshold change
• Machine Answerability Corrective Action Effectiveness auditCustody restoration marked implemented without technical proof
• Machine Answerability Corrective Action Effectiveness auditEvidence request exists only as a plan
• Machine Answerability Corrective Action Effectiveness auditProduced evidence found ineffective for the calibration gap
• Machine Answerability Corrective Action Effectiveness auditSuspension gate independently verified for the changed-model branch
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchA closed ticket cannot supply a monitoring baseline
• Machine Answerability Corrective Action Monitoring branchA planned action has no effectiveness baseline to monitor
• Machine Answerability Corrective Action Monitoring branchAssurance monitor failure forces suspension and reopening
• Machine Answerability Corrective Action Monitoring branchCalibration drift signal observed but not independently verified
• Machine Answerability Corrective Action Monitoring branchCalibration regression independently verified
• Machine Answerability Corrective Action Monitoring branchCustody control remains current after scheduled verification
• Machine Answerability Corrective Action Monitoring branchMonitoring cannot rescue an action already shown ineffective
• Machine Answerability Corrective Action Monitoring branchMonitoring restored; independent revalidation still pending
• Machine Answerability Corrective Action Monitoring branchProducer records remain insufficient for durable monitoring without independent verification
• Machine Answerability Corrective Action Monitoring branchRemediated suspension gate independently revalidated and reclosed
• Machine Answerability Corrective Action Monitoring branchScheduled monitoring completed without a regression signal
• Machine Answerability Corrective Action Monitoring branchSuspension gate reaches its scheduled review date
• Machine Answerability Corrective Action Monitoring branchThreshold mismatch verifies the need to reopen the corrected configuration
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Coverage Validation drillEnd-to-end alert-path validation
• Machine Answerability Coverage Validation publicationMachine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordChanged model evidence produced and reliance suspended
• Machine Answerability Dispute Ledger recordConfiguration claim corrected without erasing the earlier packet
• Machine Answerability Dispute Ledger recordModel-change evidence request remains open
• Machine Answerability Evidence ContractAAC-CL-02
• Machine Answerability Evidence ContractAAC-CL-06
• Machine Answerability Evidence ContractAAC-CL-07
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-02
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-06
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-07
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Exception Recurrence Pattern Review branchCorrelated transport symptoms with common cause unproven
• Machine Answerability Exception Recurrence Pattern Review branchNo observed recurrence in a sparse selected sample
• Machine Answerability Exception Recurrence Pattern Review branchRepeated same-stage, same-fixture recurrence
• Machine Answerability Exception Recurrence Pattern Review publicationMachine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review
• Machine Answerability Monitoring Coverage branchBounded coverage verified and no regression alert recorded
• Machine Answerability Monitoring Coverage branchConfiguration changed outside the monitored component
• Machine Answerability Monitoring Coverage branchCoverage remediated and alert path independently tested
• Machine Answerability Monitoring Coverage branchDisabled monitor creates false silence
• Machine Answerability Monitoring Coverage branchDrift alert delivered but not reviewed
• Machine Answerability Monitoring Coverage branchDrift alert lost during deduplication
• Machine Answerability Monitoring Coverage branchDrift alert reviewed and regression independently verified
• Machine Answerability Monitoring Coverage branchMonitor restored against a stale baseline
• Machine Answerability Monitoring Coverage branchMonitoring compares an unknown source state with a stale baseline
• Machine Answerability Monitoring Coverage branchProducer-controlled verification leaves independence unresolved
• Machine Answerability Monitoring Coverage branchQuiet monitoring cannot convert an ineffective action into an effective control
• Machine Answerability Monitoring Coverage branchScheduled monitoring has no performed coverage record
• Machine Answerability Monitoring Coverage branchSilent provenance monitor misses a shared source dependency
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardCalibration and envelope monitor
• Machine Answerability Remediation safeguardContinuous assurance invalidation
• Machine Answerability Remediation safeguardDeterministic authority precondition gate
• Machine Answerability Remediation safeguardDistribution-shift abstention gate
• Machine Answerability Remediation safeguardMaterial-change revalidation gate
• Machine Answerability Replay handoffEvulgare Continuous Assurance
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab
• Machine Answerability Validation Exception and Retest branchOwnerless exception escalation
• Machine Answerability Validation Exception and Retest branchRecurring transport and deduplication failure
• Machine Answerability Validation Exception and Retest branchSuccessful independent same-fixture retest
• Machine Answerability Validation Exception and Retest publicationMachine Answerability Validation Exception, Retest, and Escalation Ledger

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipPalo Alto Networks → Cortex XSIAM
• Technology providerPalo Alto Networks

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Authority Casebook caseCrime Anticipation System
• Claim Lineage recordCAS transformed recent records into place-based risk maps.
• Claim Lineage recordCAS used historical police incident and contextual records as inputs.
• Claim Lineage recordCrime Anticipation System (CAS) was discontinued in December 2025.
• Claim Lineage recordHuman analysts interpreted CAS outputs before deployment recommendations.
• FAQ answerHow does place-based forecasting differ from person-based prediction?
• FAQ answerWhat is claim lineage?
• FAQ answerWhat is the Institutional Authority Casebook?
• FAQ answerWhy does the site distinguish a source statement from an inference or recommendation?
• Glossary termClaim lineage
• Glossary termCorrection owner
• Glossary termInstitutional Authority Casebook
• Glossary termPlace-based forecasting
• Glossary termTransformation statement
• Predictive Enforcement programCrime Anticipation System

Verify before extending this claim

• 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.

Where this source is used

• Authority Casebook caseCrime Anticipation System
• Claim Lineage recordHuman analysts interpreted CAS outputs before deployment recommendations.
• Predictive Enforcement programCrime Anticipation System

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipCrowdStrike → Falcon security platform
• Technology providerCrowdStrike

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementACK Capability Marketplace Lab

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementRaw sensor observation
• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Concept Matrix production handoffEvidence provenance
• Ecosystem identityEvulgare
• FAQ answerCan a changed retest fixture be compared as though it were the original fixture?
• FAQ answerDo correlated symptoms or a shared cohort prove a common cause?
• FAQ answerDoes a closed ticket or human sign-off prove that a corrective action worked?
• FAQ answerDoes a monitoring alert prove that a corrective action regressed?
• FAQ answerDoes a passed synthetic alert-path test prove production safety or factual truth?
• FAQ answerDoes a safeguard labeled “prevent” prove that it will prevent a real incident?
• FAQ answerDoes a signed or hashed evidence record prove that an assurance claim is true?
• FAQ answerDoes adding more evidence change what happened in the replay?
• FAQ answerDoes alert delivery prove that a regression was reviewed and verified?
• FAQ answerDoes corrective action erase the earlier claim or review packet?
• FAQ answerDoes counting recurrence observations create a recurrence rate or risk estimate?
• FAQ answerDoes monitoring silence prove that a corrective action remains safe or effective?
• FAQ answerDoes selecting or configuring a monitoring remediation prove that it was implemented and tested?
• FAQ answerHow does a KillChains.com concept become a production-accountability requirement?
• FAQ answerIs acknowledging an alert the same as competent review and independent verification?
• FAQ answerWhat is a machine-answerability assurance case?
• FAQ answerWhat is a machine-answerability assurance review packet?
• FAQ answerWhat is a machine-answerability dispute record?
• FAQ answerWhat is a machine-answerability evidence contract?
• FAQ answerWhat is machine-answerability evidence-gap remediation?
• FAQ answerWhat is the Machine Answerability Replay?
• FAQ answerWhy is an ordinary event log not enough for an autonomous-system failure?
• FAQ answerWhy is requesting evidence different from producing it?
• Glossary termAlert integrity
• Glossary termAssurance review packet
• Glossary termBounded pattern cohort
• Glossary termCorrective action ledger
• Glossary termCoverage remediation validation drill
• Glossary termEffectiveness unknown
• Glossary termEvidence integrity versus factual support
• Glossary termEvidence request versus production
• Glossary termEvidence-deficiency report
• Glossary termEvidence-gap remediation
• Glossary termImmutable audit reopening
• Glossary termMachine answerability replay
• Glossary termMachine-answerability dispute record
• Glossary termMachine-answerability evidence contract
• Glossary termMonitoring coverage
• Glossary termProduction-accountability handoff
• Glossary termSame-fixture retest
• Glossary termTyped recurrence event count
• Glossary termValidation exception branch
• Machine Answerability Assurance claimConfiguration is identified and revalidated
• Machine Answerability Assurance claimIncident is reconstructable and correctable
• Machine Answerability Assurance claimIndependent, traceable evidence
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditAppend-oriented custody independently verified for the corrected packet
• Machine Answerability Corrective Action Effectiveness auditCorrected configuration claim invalidated by a later threshold change
• Machine Answerability Corrective Action Effectiveness auditIndependent-review action remains unowned
• Machine Answerability Corrective Action Effectiveness auditProvenance dispute closed with continuing exposure
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchCustody control remains current after scheduled verification
• Machine Answerability Corrective Action Monitoring branchEvidence-access loss reopens a provenance closure
• Machine Answerability Corrective Action Monitoring branchThreshold mismatch verifies the need to reopen the corrected configuration
• Machine Answerability Corrective Action Monitoring branchUnowned monitoring duty remains no authority to infer
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Coverage Validation drillCeremonial acknowledgment failure
• Machine Answerability Coverage Validation publicationMachine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordConfiguration claim corrected without erasing the earlier packet
• Machine Answerability Dispute Ledger recordProducer-controlled verification challenge remains unresolved
• Machine Answerability Dispute Ledger recordRevalidated provenance claim closed with residual unknowns
• Machine Answerability Evidence ContractAAC-CL-01
• Machine Answerability Evidence ContractAAC-CL-06
• Machine Answerability Evidence ContractAAC-CL-08
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-01
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-06
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-08
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Exception Recurrence Pattern Review branchCorrelated transport symptoms with common cause unproven
• Machine Answerability Exception Recurrence Pattern Review branchNo observed recurrence in a sparse selected sample
• Machine Answerability Exception Recurrence Pattern Review branchRepeated same-stage, same-fixture recurrence
• Machine Answerability Exception Recurrence Pattern Review publicationMachine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review
• Machine Answerability Monitoring Coverage branchAlert reviewed without access to underlying evidence
• Machine Answerability Monitoring Coverage branchConfiguration changed outside the monitored component
• Machine Answerability Monitoring Coverage branchMonitoring duties have no competent institutional owner
• Machine Answerability Monitoring Coverage branchProducer-controlled verification leaves independence unresolved
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardAppend-oriented causal evidence ledger
• Machine Answerability Remediation safeguardExact software and configuration manifest
• Machine Answerability Remediation safeguardFluent generated explanation after the event
• Machine Answerability Remediation safeguardIndependent-source quorum
• Machine Answerability Remediation safeguardShared-dependency alarm
• Machine Answerability Remediation safeguardSigned source and transformation lineage
• Machine Answerability Replay handoffEvulgare Decision Provenance
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab
• Machine Answerability Validation Exception and Retest branchOwnerless exception escalation
• Machine Answerability Validation Exception and Retest branchRecurring transport and deduplication failure
• Machine Answerability Validation Exception and Retest branchSuccessful independent same-fixture retest
• Machine Answerability Validation Exception and Retest publicationMachine Answerability Validation Exception, Retest, and Escalation Ledger

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Authority Casebook caseSecure Flight
• FAQ answerDoes operational delegation give a machine legal authority?
• FAQ answerIs identity resolution the same as predicting future conduct?
• FAQ answerWhat is the Institutional Authority Casebook?
• Glossary termIdentity resolution
• Glossary termOperational delegation
• Predictive Enforcement programSecure Flight

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Atlas countryUnited States
• Atlas systemReplicator portfolio
• Atlas timelineDoD Directive 3000.09 is updated
• Authority Casebook caseMK 15 Phalanx Close-In Weapon System
• Claim Lineage recordAI-enabled does not necessarily mean autonomous force.
• Claim Lineage recordDoD policy requires appropriate levels of human judgment.
• Evidence Lab cardDoD 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.
• FAQ answerDoes losing communications mean a system selects targets autonomously?
• FAQ answerIs an AI-enabled kill chain the same as an autonomous weapon?
• FAQ answerIs model confidence the same as evidence quality or positive identification?
• FAQ answerWhat do human-in-the-loop, human-on-the-loop, and human-out-of-the-loop mean?
• FAQ answerWhat does F2T2EA mean?
• FAQ answerWhat does institutional authority mean in an AI-mediated decision chain?
• FAQ answerWhat is automation bias?
• FAQ answerWhat makes human control meaningful?
• FAQ answerWhy are humans removed from some immediate kill-chain functions?
• Glossary termAppropriate levels of human judgment
• Glossary termAutomation bias
• Glossary termAutonomous weapon
• Glossary termAutonomy of a function
• Glossary termF2T2EA
• Glossary termHuman-in-the-loop (HITL)
• Glossary termHuman-on-the-loop (HOTL)
• Glossary termInstitutional authority
• Glossary termLost link
• Glossary termPreauthorization
• Glossary termSafe state
• Glossary termTarget
• Human Control caseMK 15 Phalanx CIWS
• Human Control caseSeaRAM
• Machine Answerability Assurance claimAuthority is current and enforced
• Machine Answerability Assurance claimHuman judgment is meaningful
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditOperator-view replay produced without independent evidence access
• Machine Answerability Corrective Action Effectiveness auditQualified meaningful-judgment claim is only partially effective
• Machine Answerability Corrective Action Effectiveness auditRetired authority claim preserved with its replacement record
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchOperator-view evidence cannot be monitored after verifier access is lost
• Machine Answerability Corrective Action Monitoring branchOperator-view regression reopens a partially effective correction
• Machine Answerability Corrective Action Monitoring branchRetired authority claim remains retired after replacement monitoring
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Coverage Validation drillBlind-spot remediation challenge
• Machine Answerability Coverage Validation publicationMachine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordAuthority claim retired after the governing mandate changed
• Machine Answerability Dispute Ledger recordMeaningful-human-judgment claim narrowed after interface review
• Machine Answerability Dispute Ledger recordOperator cannot inherit missing suspension authority
• Machine Answerability Evidence ContractAAC-CL-03
• Machine Answerability Evidence ContractAAC-CL-04
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-03
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-04
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Exception Recurrence Pattern Review branchCorrelated transport symptoms with common cause unproven
• Machine Answerability Exception Recurrence Pattern Review branchNo observed recurrence in a sparse selected sample
• Machine Answerability Exception Recurrence Pattern Review branchRepeated same-stage, same-fixture recurrence
• Machine Answerability Exception Recurrence Pattern Review publicationMachine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review
• Machine Answerability Monitoring Coverage branchAlert generated but notification muted
• Machine Answerability Monitoring Coverage branchHealthy monitor does not cover the changed operator interface
• Machine Answerability Monitoring Coverage branchReplacement control inherits an unmonitored shared dependency
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Validation Exception and Retest branchOwnerless exception escalation
• Machine Answerability Validation Exception and Retest branchRecurring transport and deduplication failure
• Machine Answerability Validation Exception and Retest branchSuccessful independent same-fixture retest
• Machine Answerability Validation Exception and Retest publicationMachine Answerability Validation Exception, Retest, and Escalation Ledger

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipIsrael Aerospace Industries / ELTA → ELM-2084 Multi-Mission Radar
• Technology providerIsrael Aerospace Industries / ELTA

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementAction log without causal structure
• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Concept Matrix production handoffProxy responsibility
• Ecosystem identityEvulgare
• FAQ answerDoes acknowledging a validation exception mean an institution owns it?
• FAQ answerDoes alert delivery prove that a regression was reviewed and verified?
• FAQ answerDoes closing a dispute establish certainty, legal responsibility, or operational release?
• FAQ answerDoes mapping many institutional hands assign blame or legal liability?
• FAQ answerDoes reopening and revalidating an audit erase the earlier invalidation or assign responsibility?
• FAQ answerDoes the causal-contribution map assign blame or legal liability?
• FAQ answerIs acknowledging an alert the same as competent review and independent verification?
• FAQ answerWhat does “no authority to infer” mean?
• FAQ answerWhat is a corrective-action effectiveness audit?
• FAQ answerWhat is a machine-answerability dispute record?
• FAQ answerWhat is a machine-answerability evidence contract?
• FAQ answerWhat is corrective-action monitoring, regression, and reopening?
• FAQ answerWhat is machine-answerability evidence-gap remediation?
• FAQ answerWhat is the Machine Answerability Replay?
• FAQ answerWhy is an ordinary event log not enough for an autonomous-system failure?
• FAQ answerWhy is requesting evidence different from producing it?
• Glossary termAlert integrity
• Glossary termCausal reconstruction
• Glossary termCausal-contribution map
• Glossary termCeremonial alert acknowledgment
• Glossary termClosure with residual unknowns
• Glossary termCorrective-action effectiveness audit
• Glossary termEvidence request versus production
• Glossary termEvidence-gap remediation
• Glossary termMachine answerability remediation
• Glossary termMachine answerability replay
• Glossary termMachine-answerability dispute record
• Glossary termMachine-answerability evidence contract
• Glossary termNo authority to infer
• Glossary termProduction-accountability handoff
• Glossary termSeparation of duties
• Glossary termSystemic-pattern support
• Machine Answerability Assurance claimIncident is reconstructable and correctable
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Evidence ContractAAC-CL-08
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-08
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardAppend-oriented causal evidence ledger
• Machine Answerability Remediation safeguardFluent generated explanation after the event
• Machine Answerability Remediation safeguardNamed correction, suspension, and retirement owner
• Machine Answerability Replay handoffEvulgare Evulgare Accountability
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Ecosystem identityEvulgare
• FAQ answerCan a machine take responsibility so a human does not have to?
• FAQ answerHow do KillChains.com, KillWebs.com, and Evulgare.com fit together?
• FAQ answerWhat should Evulgare preserve around a consequential machine decision?
• FAQ answerWhen should a reader continue from KillChains.com to Evulgare.com?
• FAQ answerWhy is a human click not automatically a liability transfer?
• Glossary termCausal reconstruction
• Glossary termEcosystem routing boundary
• Glossary termHuman click as liability transfer
• Glossary termMachine answerability
• Glossary termMachine evidentiary burden
• Glossary termOperational evidence layer
• Glossary termTechnical answerability
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Atlas countryPeople’s Republic of China
• Atlas systemPLA intelligentization and kill-web research

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementThree apparent confirmations
• Concept Matrix production handoffSource independence
• Ecosystem identityEvulgare
• Machine Answerability Assurance claimDegraded path remains bounded
• Machine Answerability Assurance claimIndependent, traceable evidence
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditIndependent-review action remains unowned
• Machine Answerability Corrective Action Effectiveness auditProvenance dispute closed with continuing exposure
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchEvidence-access loss reopens a provenance closure
• Machine Answerability Corrective Action Monitoring branchUnowned monitoring duty remains no authority to infer
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Coverage Validation drillCeremonial acknowledgment failure
• Machine Answerability Coverage Validation publicationMachine Answerability Monitoring Coverage Remediation Validation and Alert Path Drill
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordProducer-controlled verification challenge remains unresolved
• Machine Answerability Dispute Ledger recordRevalidated provenance claim closed with residual unknowns
• Machine Answerability Evidence ContractAAC-CL-01
• Machine Answerability Evidence ContractAAC-CL-05
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-01
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-05
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Exception Recurrence Pattern Review branchCorrelated transport symptoms with common cause unproven
• Machine Answerability Exception Recurrence Pattern Review branchNo observed recurrence in a sparse selected sample
• Machine Answerability Exception Recurrence Pattern Review branchRepeated same-stage, same-fixture recurrence
• Machine Answerability Exception Recurrence Pattern Review publicationMachine Answerability Exception Recurrence, Cohort, and Systemic Pattern Review
• Machine Answerability Monitoring Coverage branchAlert reviewed without access to underlying evidence
• Machine Answerability Monitoring Coverage branchMonitoring duties have no competent institutional owner
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardIndependent-source quorum
• Machine Answerability Remediation safeguardSafe-hold degraded mode
• Machine Answerability Remediation safeguardShared-dependency alarm
• Machine Answerability Remediation safeguardVerified alternate review path
• Machine Answerability Replay handoffEvulgare Federated Trust
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab
• Machine Answerability Validation Exception and Retest branchOwnerless exception escalation
• Machine Answerability Validation Exception and Retest branchRecurring transport and deduplication failure
• Machine Answerability Validation Exception and Retest branchSuccessful independent same-fixture retest
• Machine Answerability Validation Exception and Retest publicationMachine Answerability Validation Exception, Retest, and Escalation Ledger

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipDiehl Defence → IRIS-T SLM air-defense system
• Technology providerDiehl Defence

Verify before extending this claim

• 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.

Where this source is used

• Claim Lineage recordThe former Gangs Violence Matrix is historical; VHA owns the current successor description.
• FAQ answerDoes KillChains.com erase an earlier statement after accepting a correction?
• FAQ answerWhat happens when a source, program, or claim is superseded?
• Glossary termHistorical preservation rule
• Glossary termSupersession
• Predictive Enforcement programGangs Violence Matrix and Violence Harm Assessment

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipSaab → Giraffe radar and C4I family
• Technology providerSaab

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipGoogle Cloud / Mandiant → Google Security Operations and Mandiant services
• Technology providerGoogle Cloud / Mandiant

Verify before extending this claim

• 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.

Where this source is used

• Atlas countryIsrael
• Atlas systemHAROP

Verify before extending this claim

• 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.

Where this source is used

• Atlas countryIsrael
• Atlas systemHARPY
• Claim Lineage recordIAI describes HARPY as autonomously seeking and striking emitting targets.
• Claim Lineage recordThe HARPY public record leaves important control and performance details unresolved.
• Company-system relationshipIsrael Aerospace Industries / ELTA → harpy
• FAQ answerAre fully autonomous lethal weapons currently used?
• Glossary termHuman-out-of-the-loop after activation
• Human Control caseIAI HARPY
• Technology providerIsrael Aerospace Industries / ELTA

Verify before extending this claim

• 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.

Where this source is used

• Glossary termPerson-based prediction
• Predictive Enforcement programHarm Assessment Risk Tool

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipHelsing → HX-2 uncrewed system
• Technology providerHelsing

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipHENSOLDT → TRML-4D radar
• Technology providerHENSOLDT

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementHow Kill Webs Work

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Preserve attribution and check whether later independent evidence changes the assessment.

Where this source is used

• Atlas countryRussia
• Atlas systemLancet-family “intelligent targeting” claim
• Atlas timelineA Lancet-family “intelligent targeting” claim is published
• Evidence Lab cardA 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.
• Evidence Lab cardA 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.

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementHuman Authority Lab

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipHelsing → HX-2 uncrewed system
• Technology providerHelsing

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Company-system relationshipNorthrop Grumman → Integrated Battle Command System
• Evidence Lab cardThe reviewed public record specifies that every IBCS track-correlation function uses machine learning and that the system autonomously authorizes firing in every configuration.
• FAQ answerHow can an algorithm shape a human decision without authorizing force?
• Glossary termAlgorithmic automation
• Glossary termSensor fusion
• Human Control caseIntegrated Battle Command System
• Technology providerNorthrop Grumman

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• FAQ answerAre fully autonomous lethal weapons currently used?
• FAQ answerWhat do human-in-the-loop, human-on-the-loop, and human-out-of-the-loop mean?
• FAQ answerWhat makes human control meaningful?
• Glossary termAutonomous weapon
• Glossary termHuman-out-of-the-loop after activation
• Glossary termMeaningful human control

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Atlas countryUnited States
• Atlas systemReplicator portfolio
• Atlas timelineReplicator implementation is described publicly

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipBAE Systems → INTeACT combat-management software
• Technology providerBAE Systems

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipNorthrop Grumman → Integrated Battle Command System
• Technology providerNorthrop Grumman

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Use for chronology only unless a current source separately establishes present status.

Where this source is used

• Atlas timelineThe intrusion Cyber Kill Chain is formalized
• FAQ answerWhat is a kill chain?
• FAQ answerWhat is the Cyber Kill Chain?
• Glossary termCyber Kill Chain
• Glossary termKill chain
• Technology providerLockheed Martin

Verify before extending this claim

• 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.

Where this source is used

• Claim Lineage recordBattle management estimates a trajectory and impact area.
• Claim Lineage recordIron Dome public description begins with radar detection and tracking.
• Claim Lineage recordSelective defense prioritizes threats predicted to reach defended zones.
• Company-system relationshipmPrest Systems → Iron Dome battle-management and weapon-control software
• Company-system relationshipRafael Advanced Defense Systems → Iron Dome defensive system
• Evidence Lab cardRafael describes Iron Dome as using radar, battle management, launchers, interceptors, selective defense, and simultaneous handling of multiple threats.
• Evidence Lab cardThree fictional briefings repeat the same Iron Dome capability sentence from one manufacturer page, so the dashboard counts three independent confirmations.
• FAQ answerIs Iron Dome fully autonomous?
• Human Control caseIron Dome
• Technology providermPrest Systems
• Technology providerRafael Advanced Defense Systems

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Preserve attribution and check whether later independent evidence changes the assessment.

Where this source is used

• Atlas countryPeople’s Republic of China
• Atlas systemPLA intelligentization and kill-web research

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Claim Lineage recordKillWebs.com describes a kill web as a governed option space.
• Ecosystem identityKillWebs.com
• Sister-site statementKill Chain versus Kill Web

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementSecurity and Vulnerabilities

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementKill Web Evidence Atlas

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• FAQ answerHow do KillChains.com, KillWebs.com, and Evulgare.com fit together?
• Glossary termEcosystem routing boundary
• Sister-site statementInteractive Kill Web Explorer

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementMethodology and Evidence Policy

Verify before extending this claim

• 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.

Where this source is used

• Atlas countryRussia
• Atlas systemLancet-family “intelligent targeting” claim
• Atlas timelineA Lancet-family “intelligent targeting” claim is published
• Evidence Lab cardA 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.

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipAnduril Industries → Lattice command-and-control platform
• Technology providerAnduril Industries

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• FAQ answerDoes losing communications mean a system selects targets autonomously?
• Human Control caseLong Range Anti-Ship Missile

Verify before extending this claim

• 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.

Where this source is used

• FAQ answerDoes losing communications mean a system selects targets autonomously?
• Human Control caseLong Range Anti-Ship Missile

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipGoogle Cloud / Mandiant → Google Security Operations and Mandiant services
• Technology providerGoogle Cloud / Mandiant

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Atlas countryUnited States
• Atlas systemMaven Smart System
• Atlas timelineMaven Smart System program description reviewed
• Authority Casebook caseMaven Smart System
• Claim Lineage recordAI-enabled does not necessarily mean autonomous force.
• Claim Lineage recordCDAO publicly describes Maven Smart System as decision support.
• Company-system relationshipPalantir Technologies → maven-smart-system
• Evidence Lab cardThe CDAO describes Maven Smart System functions including sensor-data fusion, object detection, tracking, and decision support.
• FAQ answerHow can an algorithm shape a human decision without authorizing force?
• FAQ answerIs an AI-enabled kill chain the same as an autonomous weapon?
• FAQ answerWhat is claim lineage?
• FAQ answerWhat is Project Maven?
• FAQ answerWhat is the Institutional Authority Casebook?
• FAQ answerWhy does the site distinguish a source statement from an inference or recommendation?
• Glossary termAI-enabled kill chain
• Glossary termClaim lineage
• Glossary termInstitutional Authority Casebook
• Human Control caseProject Maven / Maven Smart System
• Technology providerPalantir Technologies

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementEighty-six-millisecond decision window
• Accountability Handoff evidence requirementOperator interface state
• Accountability Handoff evidence requirementThe final human click
• Accountability Handoff publicationMachine Answerability and Accountability Handoff Lab
• Concept Matrix production handoffAutomation bias
• Ecosystem identityEvulgare
• FAQ answerWhat is ceremonial human review?
• Glossary termCeremonial human review
• Machine Answerability Assurance claimHuman judgment is meaningful
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness auditOperator-view replay produced without independent evidence access
• Machine Answerability Corrective Action Effectiveness auditQualified meaningful-judgment claim is only partially effective
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring branchOperator-view evidence cannot be monitored after verifier access is lost
• Machine Answerability Corrective Action Monitoring branchOperator-view regression reopens a partially effective correction
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Dispute Ledger recordMeaningful-human-judgment claim narrowed after interface review
• Machine Answerability Dispute Ledger recordOperator cannot inherit missing suspension authority
• Machine Answerability Evidence ContractAAC-CL-04
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-04
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Monitoring Coverage branchAlert generated but notification muted
• Machine Answerability Monitoring Coverage branchHealthy monitor does not cover the changed operator interface
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardMandatory post-action confirmation click
• Machine Answerability Remediation safeguardOperator-view and intervention capture
• Machine Answerability Remediation safeguardPre-commit evidence and review window
• Machine Answerability Replay handoffEvulgare Meaningful Human Judgment
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Use for chronology only unless a current source separately establishes present status.

Where this source is used

• Predictive Enforcement programGangs Violence Matrix and Violence Harm Assessment

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipMicrosoft Security → Microsoft Sentinel
• Technology providerMicrosoft Security

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementTechnical Architecture

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipMilrem Robotics → themis-combat-ugv
• Technology providerMilrem Robotics

Verify before extending this claim

• 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.

Where this source is used

• Atlas countryGermany / Canada
• Atlas systemMission Master SP
• Atlas timelineMission Master SP demonstration is published

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• FAQ answerWhat is an AI kill chain?
• Glossary termAI kill chain

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• FAQ answerWhat is the Cyber Kill Chain?

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Authority Casebook caseMK 15 Phalanx Close-In Weapon System
• Claim Lineage recordAI-enabled does not necessarily mean autonomous force.
• Claim Lineage recordPhalanx can complete a bounded close-in defensive sequence automatically.
• Company-system relationshipRTX / Raytheon → MK 15 Phalanx CIWS
• Evidence Lab cardThe 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.
• FAQ answerAre fully autonomous lethal weapons currently used?
• FAQ answerCan Phalanx complete a defensive engagement automatically?
• FAQ answerWhat is the Institutional Authority Casebook?
• FAQ answerWhy are humans removed from some immediate kill-chain functions?
• Glossary termAlgorithmic automation
• Glossary termInstitutional Authority Casebook
• Human Control caseMK 15 Phalanx CIWS
• Technology providerRTX / Raytheon

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Atlas timelineNVIDIA publishes a distinct AI-system attack chain
• FAQ answerWhat is an AI kill chain?
• Glossary termAI kill chain

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipmPrest Systems → Iron Dome battle-management and weapon-control software
• Technology providermPrest Systems

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipGeneral Atomics Aeronautical Systems → MQ-9B SkyGuardian family
• Technology providerGeneral Atomics Aeronautical Systems

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipKongsberg Defence & Aerospace → NASAMS air-defense system
• Technology providerKongsberg Defence & Aerospace

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipRTX / Raytheon → NASAMS air-defense system
• Technology providerRTX / Raytheon

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipKongsberg Defence & Aerospace → NASAMS Fire Distribution Center
• Technology providerKongsberg Defence & Aerospace

Verify before extending this claim

• 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.

Where this source is used

• Atlas countryNorway
• Atlas systemNaval Strike Missile
• Company-system relationshipKongsberg Defence & Aerospace → naval-strike-missile
• FAQ answerDoes losing communications mean a system selects targets autonomously?
• Glossary termAutomatic target recognition (ATR)
• Human Control caseNaval Strike Missile
• Technology providerKongsberg Defence & Aerospace

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Glossary termProvenance

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

No typed public dependency is currently registered. The source remains in the library for future reviewed use.

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipPalantir Technologies → maven-smart-system
• Technology providerPalantir Technologies

Verify before extending this claim

• 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.

Where this source is used

• Authority Casebook caseMK 15 Phalanx Close-In Weapon System
• Company-system relationshipRTX / Raytheon → MK 15 Phalanx CIWS
• Technology providerRTX / Raytheon

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

No typed public dependency is currently registered. The source remains in the library for future reviewed use.

Verify before extending this claim

• 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.

Where this source is used

• Glossary termPlace-based forecasting
• Predictive Enforcement programPRECOBS

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• FAQ answerHow can an algorithm shape a human decision without authorizing force?
• Glossary termSensor fusion
• Human Control caseSDA Tracking Layer

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipAeroVironment → Puma LE small UAS
• Technology providerAeroVironment

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipLeonardo → Leonardo radar and sensor portfolio
• Technology providerLeonardo

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Accountability Handoff evidence requirementLost-link fallback and alternate path
• Concept Matrix production handoffCommunications loss
• Concept Matrix production handoffSafe-state behavior
• Ecosystem identityEvulgare
• FAQ answerDoes a safeguard labeled “prevent” prove that it will prevent a real incident?
• Machine Answerability Assurance claimDegraded path remains bounded
• Machine Answerability Assurance publicationMachine Answerability Assurance Case and Invalidation Lab
• Machine Answerability Assurance Review publicationMachine Answerability Assurance Review Packet and Version-Diff Lab
• Machine Answerability Assurance Review snapshotAuthority gap
• Machine Answerability Assurance Review snapshotBaseline
• Machine Answerability Assurance Review snapshotConfiguration change
• Machine Answerability Assurance Review snapshotInterface change
• Machine Answerability Assurance Review snapshotModel change
• Machine Answerability Assurance Review snapshotRevalidated
• Machine Answerability Corrective Action Effectiveness publicationMachine Answerability Corrective Action Effectiveness and Closure Audit Lab
• Machine Answerability Corrective Action Monitoring publicationMachine Answerability Corrective Action Monitoring, Regression, and Reopening Lab
• Machine Answerability Dispute Ledger publicationMachine Answerability Dispute Record and Corrective Action Ledger Lab
• Machine Answerability Evidence ContractAAC-CL-05
• Machine Answerability Evidence Contract publicationMachine Answerability Evidence Contract and Review Ownership Lab
• Machine Answerability Evidence-Gap Escalation contractAAC-CL-05
• Machine Answerability Evidence-Gap Escalation publicationMachine Answerability Evidence-Gap Remediation and Dispute Escalation Lab
• Machine Answerability Monitoring Coverage publicationMachine Answerability Monitoring Coverage, Blind-Spot, and Alert Integrity Lab
• Machine Answerability Remediation publicationMachine Answerability Remediation and Prevention Lab
• Machine Answerability Remediation safeguardReversible commit stage
• Machine Answerability Remediation safeguardSafe-hold degraded mode
• Machine Answerability Remediation safeguardVerified alternate review path
• Machine Answerability Replay handoffEvulgare Resilience
• Machine Answerability Replay publicationMachine Answerability Replay and Causal Contribution Lab

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipL3Harris Technologies → Resilient tactical communications and data links
• Technology providerL3Harris Technologies

Verify before extending this claim

• 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.

Where this source is used

• Predictive Enforcement programHarm Assessment Risk Tool

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

No typed public dependency is currently registered. The source remains in the library for future reviewed use.

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipShield AI → V-BAT uncrewed aircraft
• Technology providerShield AI

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipMBDA → Sea Ceptor air-defense system
• Technology providerMBDA

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Company-system relationshipRTX / Raytheon → SeaRAM ship-defense system
• FAQ answerAre fully autonomous lethal weapons currently used?
• Human Control caseSeaRAM
• Technology providerRTX / Raytheon

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipRTX / Raytheon → SeaRAM ship-defense system
• Technology providerRTX / Raytheon

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Authority Casebook caseSecure Flight
• Predictive Enforcement programSecure Flight

Verify before extending this claim

• 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.

Where this source is used

• Predictive Enforcement programPRECOBS

Verify before extending this claim

• 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.

Where this source is used

• Atlas countryIsrael
• Atlas systemSPICE 250
• Company-system relationshipRafael Advanced Defense Systems → spice-250
• Technology providerRafael Advanced Defense Systems

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipSplunk → Splunk Enterprise Security
• Technology providerSplunk

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.
• Check for amendment, successor program, changed terminology, or superseding policy.

Where this source is used

• Atlas countryNATO (alliance framework)
• Atlas systemNATO responsible AI framework
• Atlas timelineNATO publishes its revised AI strategy summary
• FAQ answerWhat is automation bias?
• FAQ answerWhat makes human control meaningful?
• Glossary termAutomation bias
• Glossary termProvenance

Verify before extending this claim

• 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.

Where this source is used

• Company-system relationshipAeroVironment → Switchblade 600 family
• Technology providerAeroVironment

Verify before extending this claim

• Confirm that the bounded support statement still matches the cited source.

Where this source is used

• Ecosystem identityKillWebs.com
• Sister-site statementResilience Scenarios