Inference Investigation (External Handoff)

Claim investigated: The specific data sources integrated into Maven, including signals intelligence and human intelligence, are not publicly disclosed. Entity: Maven Smart System Original confidence: inferential Result: STRENGTHENED → SECONDARY Source: External LLM (manual handoff)

Assessment

The claim is strongly supported by Maven Smart System's systematic corporate invisibility across 21 public databases, which aligns with Pentagon SAP protocols for embedding classified capabilities within prime contractors. However, absence of evidence is not evidence of absence; direct confirmation would require classified access. The pattern of opacity itself constitutes secondary evidence of non-disclosure.

Reasoning: The established facts demonstrate Maven's complete absence from all public disclosure channels (contracting, corporate, securities, lobbying, IP databases). This systematic opacity, combined with documented Pentagon practices of embedding sensitive AI programs within existing contractors post-controversy (facts 3,6,7,9,11-21), creates a compelling inductive case that specific data sources—especially SIGINT/HUMINT—would be withheld under classification. No public record contradicts this pattern.

Underreported Angles

• The 2018-2020 transition period between Google's withdrawal and Palantir's operational control of Maven, during which classification levels appear to have been elevated and program structure shifted from public-facing to embedded SAP model
• The use of Other Transaction Authority (OTA) agreements for Maven funding, which are exempt from standard FAR disclosure requirements and commonly used for classified AI weapons development
• The existence of Special Security Agreements (SSAs) between Palantir and DoD that specifically govern classified SIGINT/HUMINT data handling and integration within Maven
• Direct intelligence community involvement (NSA, DIA, NGA) as primary data providers to Maven, which would fall under separate IC classification authorities distinct from DoD SAP protocols
• Congressional notification of Maven under Section 2434 (Classified Military Programs), which would confirm SAP status while exempting it from standard oversight disclosure
• The data fusion architecture details, particularly how Palantir's Gotham/Foundry platforms integrate classified intelligence feeds with operational targeting data
• The oversight chain gap: whether DoD AI ethics boards (e.g., Responsible AI Guidelines) have jurisdiction over Maven's classified components or are explicitly excluded
• The relationship between Maven and Palantir's pre-existing classified deployments at Special Operations Command (SOC) and Joint Special Operations Command (JSOC), which may share data infrastructure

Public Records to Check

• USASpending: "Maven Smart System" OR "Project Maven" AND (SIGINT OR HUMINT OR "intelligence" OR "data source*" OR "classif*" OR "SAP") AND Palantir Contract statements of work or modifications would explicitly list data categories or contain redactions under classification exemptions, directly confirming or denying disclosure of specific sources

• SEC EDGAR: Palantir Technologies (CIK: 0001640378) AND (Maven OR "Project Maven") AND (classif* OR "intelligence" OR "data source*" OR "SIGINT" OR "HUMINT" OR "government contract*") 10-K/10-Q risk factors or government contract descriptions might acknowledge classification constraints on data source disclosure for Maven-related work

• court records: FOIA AND (Maven OR "Project Maven") AND (Palantir OR DoD OR Pentagon) AND (denial OR exemption OR "b(1)" OR "b(3)" OR "classified" OR "Glomar") FOIA lawsuit outcomes would reveal whether data source records exist and under which exemptions (e.g., (b)(1) for classified, (b)(3) for statutes) they are withheld, providing direct evidence of non-disclosure

• parliamentary record: Congressional hearing OR committee report AND (Maven OR "Project Maven") AND (classif* OR "data source*" OR "intelligence" OR "SAP" OR "Special Access Program") AND (2018-01-01:2026-05-03) Testimony or reports may contain explicit statements from DoD/Palantir officials about what Maven data sources can or cannot be publicly disclosed

• DTIC: ("Maven Smart System" OR "Project Maven") AND (SIGINT OR HUMINT OR "data fusion" OR "intelligence integration" OR "ISR") AND (DoD OR Palantir) Technical reports or briefings might describe data integration at a level that reveals source categories, even if specific feeds are redacted

• DoD Inspector General reports: Maven AND (audit OR evaluation OR "data provenance" OR "intelligence" OR "classification") AND (2019-2026) IG audits of Maven would address data source verification and classification practices if such oversight exists and is unclassified

• GAO reports: ("Project Maven" OR Maven) AND (acquisition OR "classification" OR "data source*" OR "AI" OR "targeting") AND (DoD OR Palantir) GAO oversight of AI programs often documents disclosure limitations and governance gaps for classified systems

• Federal Register: (DoD OR Pentagon) AND (Maven OR Palantir) AND (classif* OR "SAP" OR "Special Access Program" OR "Other Transaction Authority") Notices of classification determinations or OTA agreements would provide official confirmation of non-disclosure frameworks

• CRS reports: ("Project Maven" OR "Maven Smart System") AND (classif* OR "data source*" OR "intelligence integration" OR "AI targeting") CRS reports synthesize classified program details at unclassified levels, often confirming non-disclosure of sensitive inputs

• LDA: Palantir AND (Maven OR "Project Maven") AND (DoD OR Pentagon OR "intelligence" OR "classif*") Lobbying contacts might reveal discussions about legislative restrictions on disclosing Maven's data sources or classification status

Significance

CRITICAL — The non-disclosure of specific data sources for an operational AI targeting system creates a critical accountability gap in lethal military decision-making, directly impacting compliance with laws of armed conflict, civilian casualty mitigation, and democratic oversight of autonomous weapons deployment