Inference Investigation

Claim investigated: The presence of SEC filings but absence of USASpending contract records suggests Project Maven contracts may be classified, handled through non-traditional procurement channels, or the contracting entities are not the same as those making SEC disclosures Entity: Project Maven Original confidence: inferential Result: STRENGTHENED → SECONDARY

Assessment

The inference has strong logical foundation given the established facts showing SEC filings but absent USASpending records. However, it requires verification of the specific companies making SEC disclosures and examination of classified contract databases. The timing of late 2019 SEC filings aligns with post-Google transition period when new contractors would be establishing positions.

Reasoning: The absence of USASpending records despite SEC disclosures creates a verifiable gap that supports the inference about non-traditional procurement or classification. The 2019 timing coincides with known contractor transitions, providing contextual support. However, without examining the actual SEC filing contents, the inference cannot reach primary confidence.

Underreported Angles

• The 15-month gap between Google's June 2018 withdrawal and the September 2019 SEC filings suggests an unreported transition period with potential interim contractors or procurement restructuring
• SEC filings appearing in Q3/Q4 2019 coincide with broader Pentagon AI strategy formalization under the JAIC (Joint Artificial Intelligence Center), suggesting Project Maven may have been absorbed into larger classified programs
• The specific absence of Project Maven in USASpending despite documented Pentagon AI spending suggests systematic use of Other Transaction Authorities (OTAs) or Special Access Program procurement channels
• Corporate disclosure patterns in defense AI suggest companies may be disclosing Project Maven exposure in risk factors rather than revenue recognition, indicating contingent or prospective rather than active contracts

Public Records to Check

• SEC EDGAR: Project Maven AND filing_date:[2019-09-27 TO 2019-12-20] AND form_type:(10-K OR 10-Q OR 8-K) Would identify the specific companies making disclosures and context (risk factors, revenue, contracts) to determine if disclosing entities differ from actual contractors

• USASpending: Maven OR "Algorithmic Warfare Cross-Functional Team" AND award_date:[2017 TO 2020] AND funding_agency:"Department of Defense" Would reveal if contracts exist under alternative names or organizational structures, confirming or refuting the absence claim

• SEC EDGAR: Palantir Technologies AND Project Maven AND filing_date:[2019 TO 2020] Would determine if known successor contractor Palantir made SEC disclosures, establishing connection between disclosing entities and actual contractors

• court records: "Other Transaction Authority" AND "Project Maven" AND "Department of Defense" Would reveal if non-traditional procurement channels (OTAs) were legally challenged or disclosed in litigation

• LDA: "Algorithmic Warfare" OR "Project Maven" AND client_type:"Department of Defense" AND year:[2018 TO 2020] Would identify lobbying on Maven-related issues under alternative program names during the transition period

Significance

SIGNIFICANT — This pattern reveals potential systematic use of non-transparent procurement channels for critical AI weapons programs, which has implications for congressional oversight, public accountability, and understanding of defense AI commercialization. The gap between SEC disclosure requirements and contract transparency creates a blind spot in tracking corporate-military AI relationships.