In every crisis, half the room runs in circles while the other half picks up a clipboard and starts taking stock. The Anthropic-Pentagon dispute is that crisis, and defense contractors are deciding which half they want to be in.

The short version: The government designated a FedRAMP-authorized, facility-cleared American AI company a national security supply chain threat, via social media, after the company refused to remove safety restrictions on autonomous weapons and mass surveillance. Anthropic sued days later, with the Pentagon’s own officials on the record stating the designation was “ideologically driven” with “no evidence of supply chain risk.”

If you are a federal contractor, your phone has already rung. But before you do anything, understand this: The noise level of this situation is not proportional to the regulatory clarity it has produced. There is no FAR clause. No compliance deadline. No SAM.gov representation requirement. What exists—as of this writing—is a contested social media post, a two-page letter, and a lawsuit that could produce a preliminary injunction within days.

That does not mean you should do nothing. It means you should do the right things, in the right order, and document every step.

Why This Is Not Section 889—and Why That Distinction Is Critical

Section 889 banned Huawei, ZTE, and others with clear statutory text, implementing FAR clauses, defined timelines, and mandatory SAM.gov representations. Contractors knew what was prohibited, when compliance was due, and what a violation looked like.

The Anthropic designation arrived via social media. The formal letter followed a week later and contains two paragraphs of boilerplate with no substantive analysis of how a FedRAMP-authorized, facility-cleared American company constitutes a foreign adversary sabotage risk. There is no FAR clause. No compliance deadline. No representation requirement. Anthropic is not Huawei, and this process is not Section 889.

That distinction matters enormously. Overreacting to a designation that gets vacated the following month costs just as much as underreacting to one that survives. Structured analysis is the whole game.

Who Actually Gets Hurt

Anthropic has excellent lawyers and a compelling lawsuit. The less visible casualties are the thousands of small and midsize defense subcontractors that adopted Claude because the government told them commercial AI adoption was a priority and that now face unplanned transition costs with no rule book, no timeline, and no budget line to cover those costs.

For many of these organizations, AI tools were not a convenience. They were what made CMMC compliance financially possible. The documentation burden for Level 2 certification is substantial, and AI tools cut the cost of meeting it. Losing those tools does not just disrupt workflows. For smaller contractors, it can make certification economically unviable.

The Equitable Adjustment Question

Here is what most small contractors do not know: They may be entitled to get reimbursed for the costs of dealing with this. When the government forces a change in how to perform a contract, even without formal paperwork, you have the right to seek additional compensation as a constructive change.

The equitable case here is particularly strong because the government actively created this dependency. GSA put Claude on its approved vendor list. The Pentagon entered major AI agreements as part of its own stated push to accelerate commercial AI adoption across the defense enterprise. Contractors that built Claude into their workflows were following the government’s lead. The government does not get to encourage a technology on Monday and declare it a national security threat on Friday without some accountability for the bill it just handed you.

Of course, request for equitable adjustment (REA) recovery is not automatic. You need to tie costs to a specific contract, not general disruption. You need written direction from your contracting officer (CO). And you need to document costs right now, as they happen, not six months later. Additionally, if the court vacates the designation as unlawful, the theory shifts from constructive change to something stronger. The government had no legal basis to impose these costs on you at all.

The Section 889 experience showed exactly how this plays out. Contractors that got paid kept meticulous contemporaneous records and tied costs to specific contract impacts. Those that waited and tried to reconstruct their costs largely came up empty.

Ten Actions Federal Contractors Should Take Now

The following recommended actions are organized to serve a dual purpose: positioning contractors to demonstrate good-faith compliance if the designation survives a legal challenge and building the record that supports cost recovery if it does not. In a situation of genuine legal uncertainty, both objectives must be pursued simultaneously from day one.

1. Open a formal response file today. Every decision gets documented, dated, and approved in writing. This file is your compliance defense and your REA foundation simultaneously. It costs the same to build one that serves both purposes.
2. Map every Anthropic dependency before you touch anything. Survey dev environments, security platforms, compliance tools, and custom applications. Assume the exposure runs deeper than you think—because it almost always does.
3. Contact your Managed Service Provider and Managed Security Service Provider today—in writing. Many contractors access Claude through service providers that embedded it in shared platforms. You need written confirmation of their dependencies. Their transition costs flowing to you are potentially compensable.
4. Get your CO to put the direction in writing. A social media post is not a contract modification. Verbal CO guidance is not enough. A written CO direction transforms a general policy announcement into a contract-specific change—and that is the difference between a strong REA and a weak one.
5. Pull every active contract and look for existing disclosure obligations. You need to know your representation and supply chain clause exposure before a CO asks—not after. Get contracts counsel involved now.
6. Document every cost in real time—without exception. Log every hour, every tool evaluation, every MSP invoice change as it happens. Contemporaneous records win REA claims. Reconstructed spreadsheets do not.
7. Do not touch Controlled Unclassified Information (CUI) or classified systems without a formal change management review. A hasty removal from a CUI/CMMC-scoped environment can degrade your security posture faster than it resolves your compliance risk. Slow down here even if you are moving fast everywhere else.
8. Build your decision framework before the court acts. A preliminary injunction could issue within weeks. Know in advance what an injunction, a denial, and a partial stay each mean for your response posture. Do not restart your analysis every time the docket moves.
9. Brief your board and executive leadership—with counsel in the room. This is not a decision the CIO or CISO owns alone. It requires executive sign-off, documented board awareness, and qualified government contracts counsel. Decisions made below that level create personal exposure if things go wrong.
10. Permanently incorporate AI platforms into your supply chain risk management (SCRM) program. The lesson here is not about Anthropic. It is that AI platforms are supply chain dependencies that can disappear overnight for reasons that have nothing to do with their technical performance. If your SCRM program does not account for that yet, fix it now.

The Unifying Principle

Every one of the 10 actions above serves the same dual purpose: demonstrating good-faith compliance if the designation survives and building the cost recovery record if it does not. In a situation this uncertain, those two objectives are not in tension. They are the same objective, achieved through the same work.

The contractors that navigate this best will be the ones that started their dependency mapping before the legal dust settled, documented costs before the transition was complete, and never mistook a contested social media post for a FAR clause. Because it is not one. At least not yet, and possibly not ever.

Federal contractors did not create this situation. They are entitled to navigate it carefully, deliberately, and with full awareness of the legal and contractual rights available to them.

The clipboard is the most useful tool available right now. Pick it up.