Inference Investigation (External Handoff)

Claim investigated: The full operational capabilities and deployment locations of Maven Smart System are classified. Entity: Maven Smart System Original confidence: inferential Result: STRENGTHENED → SECONDARY Source: External LLM (manual handoff)

Assessment

The claim is highly plausible given Maven's SAP-consistent corporate invisibility across 25+ public databases, its use of OTA procurement vehicles that limit disclosure, and the lethal nature of AI targeting systems. However, it remains inferential because no single public record explicitly confirms classification of capabilities and deployment locations—the pattern of opacity itself is the strongest evidence.

Reasoning: The established facts demonstrate Maven's complete absence from all public disclosure channels (25 separate confirmations), operation under OTA agreements designed to reduce transparency, and adherence to SAP protocols that embed classified AI capabilities within prime contractors. The already-elevated non-disclosure of data sources (SIGINT/HUMINT) and the program's transition from public Project Maven to invisible Maven Smart System post-2018 create a compelling inductive case that operational capabilities and deployment locations are similarly classified. No public record contradicts this pattern.

Underreported Angles

• The specific combatant commands (CENTCOM, INDOPACOM, AFRICOM, SOCOM) where Maven Smart System is operationally deployed, which would reveal the geographic scope of lethal AI targeting
• Integration with specific ISR platforms (MQ-9 Reaper, RQ-4 Global Hawk, P-8 Poseidon, Sentinel satellites) that feed full-motion video and sensor data into Maven's targeting algorithms
• The operational tempo and frequency of Maven's use in kinetic strikes, which would indicate scale, maturity, and real-world impact of the AI system
• Classification level hierarchy (SAP, SCI, NOFORN, ORCON, etc.) that specifically governs Maven's operational capability and deployment location disclosures under DoD 5205.07-M
• Foreign deployment of Maven on allied bases (e.g., Incirlik AB, RAF Akrotiri, Al Udeid) or in partner nations, creating diplomatic and Status of Forces Agreement implications
• Integration with allied intelligence systems (Five Eyes, NATO) that may share SIGINT/HUMINT feeds with Maven, revealing cross-domain data dependencies
• Testing and evaluation locations (Nellis AFB, Yuma Proving Ground, White Sands) where Maven was validated before operational fielding, indicating development timeline
• The chain of command and authorization thresholds for Maven's targeting recommendations, including which echelons (battalion, brigade, Joint Task Force) can approve lethal action based on its outputs
• Maven's precise position in the kill chain (find, fix, track, target, engage, assess) and whether it operates at tactical, operational, or strategic levels of warfare
• Any unclassified oversight mechanisms (DoD Responsible AI Guidelines working groups, JAG legal reviews, or combatant command ISR synchronization cells) with access to Maven's full capabilities and deployment information

Public Records to Check

• USASpending: "Maven Smart System" OR "Project Maven" AND (deployment OR location OR theater OR AOR OR "area of responsibility" OR "combatant command" OR capability OR "operational use" OR "fielded" OR platform OR sensor) AND Palantir Contract statements of work, delivery locations, or performance locations might explicitly mention deployment regions or operational capabilities, or contain redactions under classification exemptions directly confirming non-disclosure

• SEC EDGAR: Palantir Technologies (CIK: 0001640378) AND (Maven OR "Project Maven" OR "AI targeting" OR "military AI") AND (deployment OR location OR "geographic" OR theater OR AOR OR "operational" OR capability OR platform) 10-K/10-Q risk factors, MD&A, or government contract descriptions might reference deployment regions, operational capabilities, or platform integrations at an unclassified level

• parliamentary record: (House Armed Services OR Senate Armed Services OR Intelligence Committee) AND (Maven OR "Project Maven") AND (deployment OR location OR "where deployed" OR capability OR "operational" OR theater OR AOR OR "combatant command") AND (2018-01-01:2026-05-03) Congressional testimony from DoD (e.g., USD(I), USD(A&S), service chiefs) or Palantir executives might explicitly state whether Maven's capabilities and deployment locations are classified, or reference classification guidance

• DTIC: ("Maven Smart System" OR "Project Maven") AND (deployment OR location OR theater OR "operational use" OR "fielded" OR capability OR platform OR "ISR" OR "sensor fusion" OR "targeting") AND (DoD OR Palantir OR "AI") Technical reports, briefings, or test documentation might describe operational deployment, platform integrations, or capability details, even if specific locations or full specs are redacted

• DoD budget justifications: Maven OR "Project Maven" AND (PE 0603780D8Z OR "Program Element" OR "AI" OR "targeting" OR "machine learning" OR "autonomous") AND (deployment OR location OR capability OR "operational") Program Element (PE) narratives in RDT&E or O&M budget volumes sometimes include unclassified deployment or capability summaries for major AI programs

• court records: FOIA AND (Maven OR "Project Maven") AND (Palantir OR DoD OR Pentagon OR Defense) AND (deployment OR location OR capability OR "operational" OR "fielded") AND (denial OR exemption OR "b(1)" OR "b(3)" OR classified) FOIA lawsuit outcomes and denial letters would reveal whether deployment/location/capability records exist and under which exemptions (e.g., (b)(1) for national security, (b)(3) for statutes) they are withheld, providing direct confirmation of classification

• Federal Register: (Department of Defense OR Pentagon) AND (Maven OR Palantir OR "Project Maven") AND (classif* OR "SAP" OR "Special Access Program" OR "deployment" OR "operational capability" OR "Other Transaction Authority") Notices of classification determinations, SAP establishment, or OTA agreements would provide official confirmation that Maven's operational details are classified

• GAO reports: ("Project Maven" OR Maven OR "AI targeting" OR "military AI") AND (deployment OR location OR "where used" OR capability OR "operational assessment" OR "fielding" OR "combat use") AND (DoD OR Palantir) GAO audits of AI acquisition programs often document deployment locations and operational capabilities at unclassified levels, or explicitly note classification as a limitation

• CRS reports: ("Project Maven" OR "Maven Smart System" OR "DoD AI targeting") AND (deployment OR location OR theater OR "combatant command" OR capability OR "operational use" OR "classif*") CRS reports for Congress synthesize information on sensitive programs and often confirm classification of operational details while providing unclassified context

• DoD Inspector General reports: Maven OR "Project Maven" AND (deployment OR location OR "field site" OR "operational site" OR capability OR "operational" OR audit OR evaluation) AND (2019-01-01:2026-05-03) IG audits of Maven would need to verify deployment locations and operational capabilities to assess program effectiveness, and their redaction patterns would confirm classification

Significance

CRITICAL — The classification of operational capabilities and deployment locations for a lethal AI targeting system creates a critical accountability void, removing essential information about where and how autonomous targeting decisions are made from public oversight, directly impacting compliance with international humanitarian law, civilian casualty mitigation, and democratic control over military AI deployment