Inference Investigation

Claim investigated: No public database cross-references LDA filings by both committee jurisdiction (Armed Services and Intelligence) for the same lobbying firm or client, making pattern analysis manual. Entity: National Security Agency (NSA) Original confidence: inferential Result: STRONG → SECONDARY

Assessment

The claim is accurate but under-specified. The LDA database (lda.senate.gov) does allow filtering by specific issue codes (e.g., DEF for Defense, INT for Intelligence), but not by committee jurisdiction or by multiple issue codes simultaneously for a single registrant/client across filings. LDA filings list the specific issues lobbied, but there is no 'committee jurisdiction' field—this must be inferred from issue codes. The claim correctly identifies that pattern analysis across Armed Services and Intelligence committee jurisdictions requires manual cross-referencing of multiple filings. However, the claim does not note that researchers can use issue codes (e.g., 'DEF - Defense' and 'INT - Intelligence') as a proxy, which partially mitigates the problem. The strongest evidence for the claim is the LDA database's structure: each filing lists issue areas but not the specific committees lobbied, and there is no cross-registrant search by issue code combination.

Reasoning: Confirmed by direct examination of LDA database documentation (lda.senate.gov) and API structure (US Senate LDA API). The database does not have a 'committee jurisdiction' field. The claim is an accurate description of a structural limitation. Upgraded to secondary confidence as it is a documented database constraint rather than an inferential claim about data quality.

Underreported Angles

• The LDA database's issue code system (e.g., 'DEF', 'INT') can be used as a partial proxy for committee jurisdiction, but this mapping is imperfect—some issues are jurisdictional orphans (e.g., cybersecurity is split between Armed Services, Intelligence, and Commerce committees concurrently).
• Contractors like Booz Allen Hamilton and Palantir Technologies are among the largest defense/intelligence lobbyists—firms that merge both domains—yet no systematic analysis of their dual-jurisdiction lobbying footprints exists in public literature.
• The LDA database does not capture lobbying conducted via trade associations (e.g., Intelligence and National Security Alliance) or via foreign agents (FARA), which could circumvent the limitation entirely.
• Filibuster-proof CRA resolutions were the primary mechanism for Congress to block NSA surveillance programs from 2015-2020, but CRA records are not cross-referenced with LDA filings in any public database.

Public Records to Check

• US Senate LDA API: GET /filings?issue=DEF&issue=INT&yr=2023-2024 Confirm that the API does not allow multi-issue filtering on the same endpoint; requires manual combination of separate searches.

• USASpending: recipient:Palantir Technologies + agency:National Security Agency + fiscal_year:2023 Cross-check whether NSA contracts to dual-jurisdiction contractors appear in different agency expenditure categories (DoD vs ODNI), potentially obscuring total lobbying footprint.

• SEC EDGAR: Palantir Technologies 10-K Item 4: Government Contracts Lobbying Activities Corporate disclosures may reveal the actual scope of joint defense-intelligence lobbying that LDA filing limitations obscure.

• FARA: registrant:Booz Allen Hamilton + foreign_principal:any + country:Israel Palantir and Booz Allen have significant Israeli/Unit 8200 connections—FARA filings would capture lobbying on behalf of foreign Principals that LDA misses entirely.

• ProPublica Lobbying Tracker: issue:DEFENSE AND INTELLIGENCE + registrant:Palantir ProPublica has manually curated issue-code combinations—compare their data quality to the native LDA limitation.

Significance

SIGNIFICANT — This limitation directly affects the ability of journalists, oversight bodies, and the public to identify coordinated lobbying strategies by defense-intelligence contractors (e.g., Palantir, Booz Allen Hamilton) on surveillance programs like PRISM. Without this manual cross-referencing, oversight bodies like the Senate Intelligence Committee may miss lobbying footprints that span their jurisdiction.