Browse Cases

Why It Matters: The complaint is worth watching because it advances a theory — that a state disparate-outcome liability regime is constitutionally equivalent to commanded racial classification — that, if accepted, would create significant friction with decades of federal disparate-impact jurisprudence under Title VII, ECOA, and the Fair Housing Act, frameworks the federal government itself administers. Count Two presents the stronger and more doctrinally grounded question: whether an explicit statutory authorization for race- or sex-conscious AI adjustments can survive strict or intermediate scrutiny absent the specific evidentiary findings *Croson* and its progeny demand, and that question is likely to survive early motion practice. The case is also a leading indicator of how the federal government intends to use constitutional litigation — rather than preemption doctrine — as a tool to contest state AI regulation, a strategic choice with broad implications for the emerging field of algorithmic governance. How the district court treats the *SFFA* "zero-sum" importation in a non-admissions context may become the most consequential doctrinal development to emerge from this litigation.

Why It Matters: Doe v. Perplexity AI is significant because Perplexity's business model — generating direct, synthesized answer-engine responses rather than hosting third-party content — places it at the frontier of the unresolved question of whether Section 230 immunizes AI-generated output or whether the AI developer is itself the "information content provider" stripped of immunity; it also implicates the Garcia v. Character Technologies question of whether AI-generated outputs constitute protected speech at the pleading stage, and may help define the duty-of-care standard for AI answer engines that represent their outputs as factually accurate.

Why It Matters: This motion signals the emergence of parallel, coordinated class action litigation against a generative AI developer premised on product liability and tort theories for AI-generated nonconsensual intimate imagery, with the consolidation effort potentially positioning a single court to develop unified precedent on whether strict liability design-defect and negligence frameworks apply to generative AI outputs.

Why It Matters: This brief pushes the D.C. Circuit toward a significant and unresolved doctrinal question: whether the First Amendment protects not just a developer's written governance documents — which fit comfortably within existing editorial-judgment precedent — but also the design choices embedded in an AI system itself. The retaliation theory, grounded in publicly documented government hostility toward Anthropic's expressed values, is the brief's most legally orthodox argument and tracks the *Vullo* playbook closely enough to warrant serious merits attention. If the D.C. Circuit reaches the AI-expression question, whatever it says will carry substantial weight in future disputes over government leverage over AI developers' product decisions — a dynamic that extends well beyond the procurement context.

Why It Matters: This case tests whether courts will apply standard APA arbitrary-and-capricious review — including its requirement that agencies follow their own statutory sequence and engage with contrary factual evidence — to national-security procurement decisions that agencies have historically shielded from meaningful judicial scrutiny. The procedural-inversion argument, if accepted, would establish that even the § 4713 emergency carve-out has real limits when the record reflects self-induced urgency, a holding with broad implications for how agencies invoke national-security exigencies to bypass procedural requirements. The First Amendment retaliation theory is the brief's most novel and contested contribution: if the D.C. Circuit reaches it, the case could clarify whether *Vullo*'s government-coercion framework extends to procurement exclusions where agency officials have publicly disparaged a contractor's expressive advocacy, a question with significant consequences for AI companies whose public policy positions increasingly put them in tension with government clients.

Why It Matters: This brief is worth watching primarily because of its unconstitutional conditions framing: by grounding the First Amendment claim in the government-wide scope of the ban rather than the original contract dispute, TPAF gives the D.C. Circuit a doctrinal hook — rooted in *Alliance for Open Society* rather than the more government-favorable *Rust v. Sullivan* — that does not require the court to resolve whether an AI company's values statements and its product functionality are legally separable. That question is genuinely open: no court has squarely addressed whether a national-security procurement statute can support a cross-agency blacklist when the designated "risk" is a contractor's public advocacy about permissible uses of its own technology. The statutory misapplication argument, while creative, turns on whether courts will read § 4713's supply-chain-risk authority as limited to intentional adversarial actors — a reading the government can contest — making the First Amendment theory the stronger vehicle for Petitioner's relief.