Updated 2026-09-09
from the news desk
Why did judge block Anthropic blacklist? The 8 April order says no stay, with key issues still open
The court document available here is the D.C. Circuit’s 8 April 2026 order, which denied Anthropic’s request for a stay pending review. Its attached statement said the case still raises novel questions about what counts as supply-chain…
The court document here does not show a judge blocking the Anthropic blacklist. The D.C. Circuit’s 8 April 2026 order denied Anthropic’s request for a stay and left the designation in place, while signaling that Anthropic’s merits argument is that 41 U.S.C. § 4713 targets genuine supply-chain risks, not punishment for refusing requested military uses. The court said the legality and reviewability questions remained open.
What the 8 April order actually did
The D.C. Circuit order filed on 8 April 2026 denied Anthropic’s emergency motion for a stay pending review. The same order granted expedition, set briefing through 13 May 2026, and calendared oral argument for 19 May 2026.
The attached per curiam statement said the panel was not deciding the merits at that stage. Instead, the judges weighed harm and public interest. The statement said: “On one side is a relatively contained risk of financial harm to a single private company.” It then contrasted that with the government’s side: “On the other side is judicial management of how, and through whom, the Department of War secures vital AI technology during an active military conflict.”
So, for readers asking why did judge block Anthropic blacklist, the document in hand points the other way. The D.C. Circuit did not block the designation on 8 April. It let the designation stand while speeding up review.
Why Anthropic says the designation was unlawful
The per curiam statement described the challenged move as a determination under 41 U.S.C. § 4713. It said Anthropic PBC, which develops Claude, a family of advanced large language models, was designated by Secretary Pete Hegseth on 3 March 2026. The same statement added: “The impetus for the determination was Anthropic’s refusal to contractually authorize the Department to use Claude for mass domestic surveillance or lethal autonomous warfare.” It also said: “As a result, the Department has canceled its contracts with Anthropic, begun to remove Claude from its systems, and prohibited its other contractors from using Anthropic as a subcontractor on work performed for the Department.”
One reading of Anthropic’s legal challenge starts with the statute’s text. Section 4713 defines supply-chain risk as “the risk that any person may sabotage, maliciously introduce un - wanted function, extract data, or otherwise manipulate the design, integrity, manufac - turing, production, distribution, installation, operation, maintenance, disposition, or retire - ment of covered articles so as to surveil, deny, disrupt, or otherwise manipulate the function, use, or operation of the covered articles or in - formation stored or transmitted on the cov - ered articles.” The same section requires a written determination that “use of the authority in subsection (a)(1) is necessary to protect national security by reducing supply chain risk;” and that “less intrusive measures are not reason - ably available to reduce such supply chain risk;”
On that reading, a designation driven by a dispute over permitted end uses is hard to square with a statute focused on sabotage, unwanted functions, data extraction, or manipulation of covered articles. The case against the designation rests on that mismatch. If the real trigger was refusal to permit certain military uses, one argument is that the Department used a supply-chain tool for a different purpose.
Why the government still had a serious answer
The per curiam statement also laid out why the government still had traction at the stay stage. The statement said the Department was operating during an active military conflict. It also cited a 9 January 2026 Hegseth memo stating: “[t]he Department must also utilize models free from usage policy constraints that may limit lawful military applications”
The same statement noted that the Department relied on Anthropic for regular updates to Claude and that Claude contained built-in safeguards designed to prevent uses Anthropic considered harmful. The statement further said Anthropic and the Department had recently disagreed about whether existing usage policies allowed some military operations.
One government reading is that a supplier’s continuing control over updates and safeguards can affect the operation of AI services the Department buys. If that reading holds, the Department can argue the dispute was not only about speech or politics. It can argue that dependence on a vendor whose policy constraints may shape how a service functions is itself a procurement and national-security risk.
That does not resolve whether the statute ultimately fits. But it helps explain why the D.C. Circuit refused immediate relief even while acknowledging that Anthropic had raised substantial challenges and would likely suffer some irreparable harm.
What parts of the blacklist fight remain alive
The D.C. Circuit stressed that the merits questions were still open. Its statement said: “Anthropic’s petition raises novel and difficult questions, including what counts as a supply-chain risk under section 4713 and what qualifies as an urgent national-security interest justifying the use of truncated statutory procedures.”
The order then directed the parties to brief three concrete issues. First, it asked whether the court had jurisdiction under 41 U.S.C. § 1327 to review covered procurement actions taken under 41 U.S.C. § 4713. Second, it asked whether the government had, through the determination or notice or otherwise, directed or taken specific covered procurement actions against Anthropic. Third, it asked whether, and if so how, Anthropic could affect the functioning of its models before or after delivery to the Department.
Section 4713 helps explain why those issues matter. The statute authorizes only defined covered procurement actions, including excluding a source, finding a source non-responsible on supply-chain grounds, or directing a contractor to exclude a source from a subcontract. The same statute also sets default notice-and-response procedures, while subsection (c) lets an agency temporarily delay some of them if it determines that an urgent national security interest requires immediate action.
That leaves the central fight unresolved in the record here. Anthropic’s strongest merits point, on one reading, is that Congress wrote § 4713 for technical or operational supply-chain threats of the kind the statute itself lists. The Department’s strongest answer, on another reading, is that control over updates, safeguards, and permitted uses can itself create an operational risk in a covered procurement. The 8 April order did not choose between those readings.
Frequently asked questions
Did the 8 April 2026 court order block the Anthropic blacklist?
No. The D.C. Circuit’s 8 April 2026 order denied Anthropic’s motion for a stay pending review and expedited the case instead.
What is supply-chain risk under 41 U.S.C. § 4713?
41 U.S.C. § 4713 defines supply-chain risk as the risk that a person may sabotage, add unwanted function, extract data, or otherwise manipulate covered articles so they can surveil, deny, disrupt, or otherwise manipulate their operation or stored or transmitted information.
Why did Anthropic say the designation was unlawful?
The D.C. Circuit’s per curiam statement said the impetus for the determination was Anthropic’s refusal to authorize use of Claude for mass domestic surveillance or lethal autonomous warfare. One legal argument, reading § 4713’s text, is that this does not match the statute’s definition of supply-chain risk.
What issues did the D.C. Circuit leave open?
The 8 April 2026 order told the parties to brief jurisdiction under 41 U.S.C. § 1327, whether the government had actually taken reviewable covered procurement actions against Anthropic, and whether Anthropic could affect how its models function before or after delivery to the Department.
Caveats: The descriptions of the Department’s motive, the contract cancellations, the scope of the designation, and the update-and-safeguards dispute are drawn from the D.C. Circuit’s 8 April 2026 per curiam statement. The record here does not include the underlying determination itself or a later merits ruling.