WHYAMERICASUCKS.COM
PUBLIC SITE MAPLatest Stories
menuMenu
Abstract network diagram representing links between government, technology, and media systems
Fact Check

Palantir's 22-Point Manifesto And What The Record Actually Shows

Palantir's new 22-point brief is real, its defense and government footprint is documented, and several viral claims still need stricter proof than social media clips provide.

Published
April 21, 2026

Records Research Desk

Updated
April 21, 2026

Standards Review

Investigation
Corruption Watch

Primary-source fact check

Byline

Records Research Desk

Reviewed By

Standards Review

PalantirAlex KarpAI WeaponsSurveillanceFact Check
CorruptionRecords Research DeskStandards Review8 min read

The post and defense footprint are documented

Palantir did publish the 22-point brief linked to Alex Karp's book, including statements about hard power, software-led deterrence, and national service. That is not rumor; it is public company messaging.

Palantir's own annual report and SEC filings also show a company with deep government exposure. In 2025, government revenue was a major part of total revenue, and in 2024 the company disclosed a strategic partnership with Israel's Defense Ministry.

The manifesto argues for a political role for engineers

The brief goes beyond defending contracts Palantir already has. It argues that Silicon Valley has a civic obligation to participate in national defense, which recasts military software work as a duty rather than a business line.

That is the ideological move at the center of the post.

Genocide liability is still legally unresolved

Claims that Palantir is legally complicit in genocide are serious and require legal findings, not just rhetoric. The International Court of Justice's January 26, 2024 order in South Africa v. Israel imposed provisional measures, but did not issue a final merits ruling that genocide was proven.

That distinction matters for credibility: provisional measures and plausible-rights language are not the same as a final judgment.

The Israel partnership is the hard record

The documented center of the Israel claim is Palantir's own annual-report disclosure. The company said it agreed to a strategic partnership with Israel's Defense Ministry in 2024 to supply technology during the ongoing war.

The disclosure leaves legal questions about how the technology was used, while placing the company inside the war infrastructure by its own filing language. The next reporting burden is contract scope, deployment lane, and operational use.

Two viral claims still lack primary-record proof

Available public documents do not establish that Palantir built a specific 'blackmail file' on Americans. The surveillance-risk concerns are real policy questions, but they are different from proving a blackmail architecture.

Likewise, the exact quote that Palantir was 'created to kill leftists' was not located in a high-confidence primary source during this review. Related founder rhetoric exists, but precision and sourcing standards still apply.

Surveillance fears are larger than one viral phrase

Palantir's public controversy does not depend on proving one perfect quote or one secret file. The deeper issue is the company's business model: integrating data for governments, law enforcement, militaries, and intelligence-linked customers.

When a company builds tools that make fragmented records searchable and operational, the public question becomes who controls the system, what rules bind it, and whether ordinary people can ever see or challenge how they are classified.

The verified record is already serious enough

The verified record already shows a company openly arguing for AI-enabled hard-power doctrine while expanding ties to defense and security institutions.

The durable public-interest question is how much democratic control can exist over private software systems that are built for war, policing, border control, and intelligence work.

More Stories

Keep Reading

These related pieces come from the same public-records layer, but follow different investigations and reporting paths.