Curated public record
The library favors official policy, official program documentation, technical standards, primary framework publications, and organization-controlled product material. Manufacturer claims are labeled and not treated as independent performance verification.
Answer-first summary
The site prefers official law, policy, doctrine, standards, procurement and program records, then clearly attributed manufacturer material, independent research, and high-quality reporting.
Read the supporting sectionIt supports the bounded statement described in the source record—not every claim on the destination page or every configuration and later version of a system.
Read the supporting sectionThe Source Freshness and Correction Center shows the current editorial review state, scheduled review date, typed public dependencies, supersession, and correction pathway for every source ID.
Read the supporting sectionDoD autonomy policy, NATO responsible-use principles, ICRC positions, and the UN multilateral process.
Official program descriptions and manufacturer-controlled technical material for selected systems.
NVIDIA AI Kill Chain, MITRE ATLAS and ATT&CK, NIST AML and SSDF guidance, and OWASP.
W3C WebXR, the pinned Three.js release, and official PHP runtime lifecycle documentation.
Bounded support: Human judgment, testing, safety, cybersecurity, interfaces, legal compliance, and senior review.
Bounded support: Sensor-data fusion, object detection, tracking, and decision support.
Bounded support: Fielding attritable autonomous systems at scale; not a claim of unrestricted lethal autonomy.
Bounded support: Lawfulness, responsibility and accountability, explainability and traceability, reliability, governability, and bias mitigation.
Bounded support: Recon, Poison, Hijack, Persist, Impact, and the Iterate/Pivot branch.
Bounded support: AI-system adversary tactics, techniques, mitigations, and case studies.
Bounded support: Lifecycle, attacker knowledge, access, capability, objectives, and mitigation terminology.
Bounded support: AI-specific secure development, provenance, supply-chain, and lifecycle controls.
Bounded support: Prompt injection, excessive agency, data and embedding weaknesses, and related application risks.
Bounded support: Browser interfaces for virtual- and augmented-reality devices, poses, views, and input.
Bounded support: Pinned WebGL/WebXR rendering line used by the simulation.
Bounded support: Supported PHP branches and security maintenance status.
Bounded support: Manufacturer-described autonomous search and attack against emitting radar targets.
Bounded support: Detection, recognition, acquisition, and attack; separate IAI material describes man-in-the-loop employment.
Bounded support: Automatic target acquisition/recognition, autonomous functions, data-link updates, human-in-the-loop, and mission abort.
Bounded support: Imaging-infrared seeker and autonomous target recognition; public operator information.
Bounded support: Autonomous functions limited to mobility and weapon control retained by a human operator.
Bounded support: Autonomous navigation and cueing with a stated human-in-the-loop requirement for kinetic decisions.
Bounded support: Claimed intelligent targeting and recognition; not independent verification of control mode or performance.
Bounded support: Public evidence and uncertainty concerning Russian drone autonomy development.
Bounded support: Reported approval and use of AI-enabled detection on the Saker Scout system.
Bounded support: PLA writings and the emphasis on integration, intelligentization, and decision advantage.
Bounded support: Analysis of PLA intelligentization ambitions and uncertainty about maturity.
Bounded support: Public PRC research concepts; not direct confirmation of operational deployment.
Bounded support: Proposed prohibitions and restrictions, target type, predictability, time, area, scale, supervision, and deactivation.
Bounded support: CCW discussions and the unsettled international governance process.
Bounded support: Seven-stage Cyber Kill Chain and the premise of interrupting adversary progression.
Bounded support: Automated search, detection, evaluation, tracking, engagement, and kill assessment for bounded close-in defense.
Bounded support: Self-contained close-in defense combining autonomous search and track functions with a guided interceptor launcher.
Bounded support: Radar, battle management, launchers, interceptors, selective defense, and multi-target operation.
Bounded support: Developmental weapons integration and explicit human retention of weapons-release authority in the described testing context.
Bounded support: AI/ML-enabled processing of space, high-altitude, aerial, and terrestrial sensor data for operational decision support.
Bounded support: Sensing, algorithms, processing, data fusion, missile warning and tracking, and tactical data products.
Bounded support: Integrated sensors, command-and-control nodes, and effectors; not a universal claim of machine-learning use or autonomous firing.
Bounded support: The shift from single-platform operator toward mission commander of multiple autonomous aircraft.
Bounded support: Composing distributed sensors, command nodes, and effects into adaptable cross-domain networks.
Bounded support: Semi-autonomous operation and reduced reliance on external networks in contested environments.
Bounded support: Fielded long-range anti-ship capability with onboard sensing and terminal guidance; detailed authority boundaries remain nonpublic.
Bounded support: Behavior-level tactics and techniques that complement, rather than duplicate, a linear kill-chain narrative.
Bounded support: Company-described long-endurance small-uncrewed-aircraft sensing, communications relay, and operational use by government customers.
Bounded support: Company-described loitering-system sensing, mission control, tracking, and post-launch functions; not a universal statement of engagement authority.
Bounded support: Company-described sensor integration, track fusion, command and control, and human-machine teaming.
Bounded support: Government selection and prototyping for counter-UAS fire-control capability; not proof of every final operational configuration.
Bounded support: Government-described participation in a command-and-control prototype; developmental status must remain visible.
Bounded support: Company-described edge autonomy, mission software, uncrewed-system coordination, and terminal tracking functions.
Bounded support: Company-reported government-funded delivery commitment; not independent verification of mode-specific field behavior or results.
Bounded support: Company-described naval combat-management, sensor integration, situational awareness, and command support.
Bounded support: Company-described integration surface for combat-management applications and mission-system services.
Bounded support: Company-described endpoint, identity, cloud, threat-intelligence, investigation, and response capabilities used in security operations.
Bounded support: Company-reported delivery of an air-defense fire unit to a NATO customer; not independent performance validation.
Bounded support: Company-described remotely piloted aircraft, sensing, endurance, communications, and mission-system integration.
Bounded support: Company-described government procurement and industrial-team context for MQ-9B; not a statement of mission-specific employment.
Bounded support: Company-described SIEM, detection, investigation, threat intelligence, and response workflows for security operations.
Bounded support: Provider-described managed hunting, investigation, and incident-response support; not a universal measure of detection effectiveness.
Bounded support: Company-described software-defined uncrewed system, onboard autonomy, human-control framing, and mission functions.
Bounded support: Company-reported operational delivery or use; independent mode-specific verification remains necessary.
Bounded support: Company-described radar detection, tracking, target acquisition, and integration into air-defense networks.
Bounded support: Company-reported delivery of radar systems for operational air-defense use; not independent performance validation.
Bounded support: Company-described multi-mission radar for detection, tracking, target acquisition, and fire-control support.
Bounded support: Company-described networked air and missile defense, battle management, sensors, launchers, and interceptors.
Bounded support: Company-described distributed air-defense architecture connecting sensors, fire-distribution centers, launchers, and effectors.
Bounded support: Company-described command, control, communications, sensor fusion, threat evaluation, and weapon coordination.
Bounded support: Company-described tactical communications, resilient networking, data exchange, and command connectivity.
Bounded support: Company-described command-and-control, mission management, information fusion, and decision-support capabilities.
Bounded support: Company-described radar, electro-optical, and sensor technologies for surveillance, tracking, fire control, and situational awareness.
Bounded support: Company-described naval combat-system integration of sensors, command and decision, fire control, and effectors.
Bounded support: Operator-described Aegis radar, command-and-decision, fire-control, and weapon-system integration.
Bounded support: Company-described naval local-area air defense and integration with ship combat-management and sensor systems.
Bounded support: Company-described cloud-native SIEM, threat detection, investigation, automation, and response.
Bounded support: Company-described autonomous mobility, modular mission payloads, logistics, reconnaissance, and human-controlled weapon integration.
Bounded support: Company-reported delivery of uncrewed ground vehicles for operational support roles; not independent verification of every configuration.
Bounded support: Company-described command-and-control, sensor fusion, situational awareness, and battle-management software.
Bounded support: Company-described integration of sensors and effectors through a networked air-and-missile-defense battle-command system.
Bounded support: Government-described delivery and program status for IBCS; not a claim about every operational mode or software method.
Bounded support: Company-described data integration, operational workflows, decision support, and mission applications.
Bounded support: Company announcement of Army prototype selection for AI/ML-enabled deep sensing and decision support; developmental status remains material.
Bounded support: Company-described security operations, analytics, detection, investigation, automation, and response.
Bounded support: Company-described electric vertical-takeoff-and-landing reconnaissance platform, onboard processing, sensing, and mission support.
Bounded support: Company-reported government order and operational-support context; not independent validation of mission outcomes.
Bounded support: Company-described self-contained terminal defense, search, tracking, engagement, and assessment functions.
Bounded support: Company-described self-contained close-in defense combining Phalanx sensing with a guided interceptor launcher.
Bounded support: Company-described networked air-defense system integrating sensors, command and control, launchers, and effectors.
Bounded support: Company-described radar command-and-control integration, air picture, tracking, and weapon coordination.
Bounded support: Company-described ground-based air-defense command, control, coordination, and situational awareness.
Bounded support: Company-described vertical-takeoff uncrewed aircraft, expeditionary ISR, communications, and autonomy.
Bounded support: Company-reported naval operational use; mission-specific payloads, authority, and performance remain bounded by public evidence.
Bounded support: Company-described SIEM, risk-based detection, investigation, orchestration, and response for security operations.
Bounded support: Company-described naval combat-management, sensor integration, track management, command support, and weapon coordination.
Bounded support: Public description of the interactive kill-web explorer, observed release characteristics, direct answers, feature routes, synthetic boundary, and sister-site relationship.
Bounded support: KillWebs.com working definition of a governed option space, selective reachability, later binding, and the relation between a web and a selected mission chain.
Bounded support: Structural comparison of selected chains and wider kill-web option spaces, including topology, authority, data, testing, failure response, and the roles of both sister sites.
Bounded support: Public description of a synthetic, non-operational capability-marketplace exercise that separates technical feasibility, constraints, comparison, authority, and execution.
Bounded support: Public-safe organization of kill-web concepts, programs, architecture layers, governance questions, evidence roles, research IDs, and public unknowns without tactical locations.
Bounded support: Public description of a synthetic lab examining evidence, time, authority, intervention, communications, lifecycle decisions, and reconstructable accountability.
Bounded support: Public description of sensing, correlation, option composition, policy and trust checks, authorization, assessment, and controlled recomposition.
Bounded support: Seven deterministic public-safe scenarios covering relay loss, stale evidence, unavailable authority, timing integrity, common dependencies, and rejected provenance.
Bounded support: Public explanation of capability semantics, data fabrics, transport, cloud-edge placement, identity, trust, orchestration, interfaces, and graceful degradation.
Bounded support: Public treatment of integrity, timing, identity, data poisoning, supply-chain, electromagnetic, and common-mode risks without operational attack procedures.
Bounded support: Authority order, evidence hierarchy, report promotion, synthetic model, safety boundary, correction process, and explicit public unknowns.
Bounded support: Historical description of PRECOBS as a near-repeat, place-based burglary forecasting approach and its analyst-mediated operational workflow. It does not establish current deployment or independent crime-reduction effects.
Bounded support: Historical official evidence that PRECOBS remained in use in the Nuremberg policing area in 2019. It does not establish the 2026 deployment footprint.
Bounded support: CAS purpose, national grid-cell design, twelve-week data window, human use of outputs, operational dates, and out-of-use status from December 2025. It does not establish a causal crime-reduction effect.
Bounded support: Public-record handling and documented governance questions concerning CAS data, evaluation, procedures, retention, and impact assessments. It does not by itself prove which requested records existed or how every local team used CAS.
Bounded support: SSL/CVRM purpose, operational and governance weaknesses, evaluation limitations, and CPD decommissioning of the Party to Violence models on November 1, 2019.
Bounded support: Development of HART with Durham Constabulary, its training data, random-forest classification, risk categories, and advisory use in custody and Checkpoint eligibility. It does not establish current use in 2026.
Bounded support: Public-sector description of HART as a supervised machine-learning tool used by Durham Police and discussion of bias, governance, and human decision-making. It does not establish current status or complete subgroup performance.
Bounded support: Retrospective public account that HART was used from 2016 through 2021. It does not establish whether HART remained operational after that period.
Bounded support: Official Met account of the former Gangs Violence Matrix and its decommissioning. It does not independently validate the Matrix’s selection, effects, or fairness.
Bounded support: Regulatory findings concerning the former Matrix’s governance, accuracy, retention, differentiation, and information sharing. It does not characterize every individual entry or later VHA practice.
Bounded support: VHA purpose, inclusion and scoring approach, published DPIA/EIA/SOP, annual MOPAC review, access/removal information, and current operational status. It does not establish causal effectiveness.
Bounded support: Current VHA population and demographic figures as of July 3, 2026, including 1,632 people meeting criteria. It does not establish that inclusion is accurate or effective for every person.
Bounded support: Secure Flight’s identity data, prescreening workflow, system purpose, records, sharing, and privacy controls. It does not disclose all matching rules or aggregate error rates.
Bounded support: Current TSA passenger-screening process and public travel guidance. It does not independently validate Secure Flight matching accuracy or disclose controlled criteria.
Bounded support: Public watchlisting lifecycle, nomination and identity-resolution roles, screening uses, and the distinction between a watchlist record and an agency’s downstream legal action.
Bounded support: The March 2025 renaming of the Terrorist Screening Center to the Threat Screening Center and the publicly described expansion of its mission. It does not disclose all dataset criteria or operating rules.
Bounded support: Watchlist scale, review and redress processes, accuracy and re-review concerns, and recommendations. Aggregate counts do not constitute a false-positive rate.
Bounded support: Current FBI BTAC and TATM operational support, multidisciplinary staffing, training, research, and behavior-based threat-assessment role. It does not establish a national AI future-danger score.
Bounded support: Multidisciplinary unit design, case-specific behavioral threat assessment, management, and continuing prevention practice. It does not establish that one indicator or profile predicts attack.
Bounded support: Evulgare identity, live domain, accountability principles, evidence-layer framing, and its public description of the KillChains–KillWebs–Evulgare ecosystem. It does not independently verify a customer deployment, certification, legal conclusion, or operational performance.
Bounded support: Evulgare’s public platform model connecting evidence, observation, transformation, model, uncertainty, interpretation, policy, authority, interface, human judgment, decision, outcome, provenance, and assurance. It does not independently establish production integration or performance.
Bounded support: The public product-area boundary for technical and causal attribution across evidence, model, software, policy, authority, interface, human review, and organizational controls. It explicitly does not claim to decide legal liability.
Bounded support: The public provenance model for append-oriented histories connecting entities, activities, agents, transformations, versions, authority, interface state, and later invalidations. It does not independently establish a deployed integration.
Bounded support: The public assurance model connecting claims, evidence, assumptions, counterclaims, defeaters, reviewers, configurations, and invalidating changes. It does not certify any external system or claim.
Bounded support: The public distinction among technical capability, trusted data, delegated authority, permitted purpose, and contextual permission. It does not establish the actual authority state of a third-party system.
Bounded support: The public human-judgment model preserving raw evidence, contrary indicators, alternatives, review time, abstention, and independent hypothesis formation. It does not prove that any particular interface provides meaningful control.
Bounded support: The public uncertainty model separating aleatoric and epistemic uncertainty, distribution status, evidence completeness, source dependence, and model disagreement. It does not validate any external model’s uncertainty estimates.
Bounded support: The public trust model treating identity, data integrity, semantic compatibility, disclosure, permitted use, and authority as separate dimensions. It does not prove that a connected source is trustworthy or authorized.
Bounded support: The public resilience model for partitions, shared dependencies, stale evidence, integrity failures, safe holds, quarantine, and reconciliation. It does not establish the resilience of a deployed third-party system.
Bounded support: The public change-impact model for tracing which claims, evidence, assumptions, interfaces, and verification activities are affected by software, model, dataset, policy, compiler, or environment changes. It does not automatically invalidate or revalidate a real system.
Citation policy
A source link supports the bounded statement described in its “supports” field. It does not automatically support every claim on the destination page, every configuration of a product, or every later version of a program. Product and program pages can change after publication; dates and archived release artifacts matter.
The source library is a curated evidence set, not a claim that all relevant public material has been discovered. Classified records, proprietary implementation details, operator doctrine, test evidence, and incident data are frequently unavailable.
Read the full publication methodology · Inspect source freshness and dependencies · Use the citation guide.
The public source-index.json file mirrors this registry for discovery clients. It is derived metadata: this human-readable page and the linked original sources remain the evidence path.