Friday’s 2–1 ruling from the U.S. Court of Appeals for the D.C. Circuit handed the Pentagon what it wanted: Anthropic stays a supply chain risk, and Claude stays out of Defense Department systems. Two judges for the government, one against, with the underlying merits still somewhere down the road.

Everyone is treating this as round three of a retaliation case — and it is one. In February the government began pressuring Anthropic over the company’s refusal to let Claude power domestic mass surveillance or autonomous weapons. In late August a district judge found the blacklisting unlawful. By early September, a Pentagon official was confirming on the record that the label stood anyway. Friday’s panel made that position tenable again.

But the litigation framing is a trap, and both sides have walked into it.

The Label Requires No Findings. That’s the Whole Point.

A suspension or debarment — the normal way the federal government cuts off a vendor — comes with a stated cause, a paper trail, and a process you can contest before you’re shut out of the market. “Supply chain risk” arrives as a conclusion with no findings attached. Nobody has to prove that Claude leaks data, that the company’s cap table is compromised, or that any specific system has been penetrated. The department asserts unacceptable risk, and the vendor’s remedy is to sue — which takes years, and which, as of Friday, can be lost 2–1 on the way to a merits ruling that may never matter.

Note what happened in the gap. A district judge said the government acted unlawfully, and the product stayed banned. Winning the retaliation case did not put Claude back on a single defense network. That is what it means to litigate against a designation rather than against a finding. You can win the argument and still lose the access.

The Clause That Actually Ends the Business

Designations don’t need to be enforced to work. They propagate.

Prime contractors treat a federal risk label as a stop-work; nobody at a major integrator wants to be the person who explains to a contracting officer why a flagged vendor appears in a bid. Insurance carriers reprice around it. State procurement shops copy federal lists by reference. The Pentagon contract is the visible loss; the invisible one is every subcontract in Huntsville, Alabama and suburban Virginia where Anthropic’s name would have appeared and now quietly doesn’t.

“We don’t litigate designations,” said the contracts compliance lead at a mid-size defense supplier outside Huntsville, on a call from the parking lot outside her own bid-review meeting. “We just stop listing the vendor. It’s cheaper than explaining it to a contracting officer.”

That is the mechanism. No hearing, no finding, no vote — just a few thousand purchasing decisions made by people who are paid to avoid risk, not to adjudicate it.

The Right Spent a Decade Complaining About Exactly This

Here’s the part my side of the aisle should sit with. The designation category wasn’t invented last spring. It grew out of the telecom-security fights of the last decade — rules written to keep Huawei and Kaspersky out of federal networks. Those were good decisions on the merits. But the instrument itself has no nationality and no ideology. It flags a vendor, and the flag does the work.

The same right that spent years furious about debanking, about ESG scores quietly closing off capital, about agencies punishing disfavored firms through paperwork rather than statute, should notice the shape of this. A national security label applied without articulated findings, upheld 2–1 while the merits pend, is the administrative state’s cleanest weapon — cleaner than any regulation, because it never has to survive notice-and-comment.

The civil libertarians have their own version of this problem. They will get a beautiful district court opinion and no remedy, because the doctrine is a consolation prize. The Electronic Frontier Foundation is right that unsupported national security claims shouldn’t be a pretext for retaliation. Being right is not the same as being able to buy Claude back onto the network.

Make the Department Say What the Risk Is

The answer isn’t stripping the Pentagon of designation authority. If a vendor genuinely creates a supply chain risk, the department should be able to act fast. The reform is narrower and boring: require a written factual basis — which system, which mechanism, which mitigation the vendor refused — with a 90-day appeal and an automatic sunset if no findings are produced.

If the risk is real, the department can say so in a paragraph. If it can’t, the label was never about the risk. Right now, two pages of memo and a 2–1 panel are enough to end a company’s public-sector business, and the government doesn’t even have to win the case. It only had to file the label.

Sources