A defense law already forces Chinese AI models off DoD contracts. Fifty tech companies just asked Washington not to go further.
Section 1532 of the FY2026 NDAA already bars DoD contractors and subcontractors from using AI built by Chinese-controlled companies. Nvidia, Microsoft, Meta, and 47 other companies just published a letter asking Washington not to extend that logic into a blanket ban on open-weight AI generally — the same category of model cost-conscious GCs have been using to build their own tools.
A provision buried in this year's defense policy bill already bars Chinese-developed AI from Department of Defense contract work — and it reaches subcontractors, not just primes. Now Nvidia, Microsoft, Meta, and 47 other companies are publicly asking Washington not to widen that rule into a ban on open-weight AI generally, the same category of model this newsletter flagged two weeks ago as a cheap way for GCs to build their own RFI and estimating tools.
What did the defense bill actually ban?
Section 1532 of the FY2026 National Defense Authorization Act prohibits DoD contractors and subcontractors from using "covered artificial intelligence" while performing on a DoD contract. Covered AI means anything built by DeepSeek or its parent, High-Flyer, or by any company domiciled in, or under the ownership, control, or influence of, a "covered nation" — currently China, Russia, North Korea, and Iran — or listed on the Commerce Department's Consolidated Screening List. Contractors had 30 days from enactment to pull any covered AI tool out of DoD systems and contract performance. Waivers exist, but only case by case, signed off by the Secretary of Defense.
That reaches further than most compliance teams have registered. It's not limited to obvious national-security software — it's any AI tool, including one your firm built in-house or bought from a small vendor, if the underlying model traces back to a covered-nation company.
Does this touch a mechanical, electrical, or GC subcontractor?
Yes, if the contract is DoD-funded. Barracks, motor pools, base housing, hangars, and Army Corps of Engineers work all flow through prime and subcontract chains where Section 1532's prohibition follows the contract, not the company. A trade sub performing on a DoD job doesn't get a pass because the AI tool is theirs rather than the prime's.
Two weeks ago, we wrote up Kimi K3 — a Chinese lab's open-weight coding model — as cheap enough that a GC could build a custom RFI tracker instead of renting one. That calculation still holds for commercial work. It doesn't hold on a DoD contract: Kimi K3's developer, Moonshot AI, is a Chinese company, which puts any tool built on it inside Section 1532's prohibition for that job.
Why did Nvidia just publish a letter about this?
On July 24, Nvidia CEO Jensen Huang used his first-ever post on X to publish "Open Weights and American AI Leadership," a letter arguing against what it calls "premature restrictions" on open-weight AI models. It launched with 25 signers — Nvidia, Microsoft, Meta, Palantir, IBM, Dell, Mistral, Hugging Face, and others — and doubled to 50 within a day, adding OpenAI, Google, AMD, Cisco, Cloudflare, and GitHub. Anthropic and Amazon are notably absent from both versions.
The letter isn't a response to Section 1532 specifically. It's aimed at a broader push, reported by Axios on July 20, that the administration is reviving after Kimi K3's launch: options under review include Entity List designations for Chinese AI labs, wider federal procurement restrictions, and liability rules for any company using a Chinese model — not just DoD contractors. An executive order formalizing some of this could land by the end of 2026, with fuller agency rollout in 2027.
What this changes for a GC's vendor list
| Question | Why it matters now |
|---|---|
| Which model powers this AI feature? | Determines whether the tool is exposed to Section 1532 or a future broader rule |
| Where is that model's developer domiciled? | "Covered nation" status attaches to the company, not the model's price or benchmark score |
| Is this tool used on any DoD-funded contract? | Section 1532 only reaches DoD contract performance today — not commercial work, not yet |
| Who owns the removal obligation? | The contractor and subcontractor, on a 30-day clock — not the government, and not the vendor |
None of this reaches most commercial GC and trade-sub work today. Western open-weight models — Meta's Llama, Mistral, Google's Gemma — aren't covered nation AI and aren't touched by Section 1532. The immediate action item is narrower: if your firm bids DoD work, or your subs do, find out what model actually runs behind every "smart" feature in the stack before the next award, not after.
If your firm bids any DoD-funded work, forward this to whoever signs your compliance certifications — the Kimi K3 cost case we made two weeks ago doesn't apply on those contracts.
- Does federal law already ban Chinese AI models on construction contracts?
- Only on Department of Defense contracts, and only a specific category. Section 1532 of the FY2026 NDAA prohibits DoD contractors and subcontractors from using 'covered artificial intelligence' — AI built by DeepSeek, its owner High-Flyer, or any company domiciled in or controlled by China, Russia, North Korea, or Iran — while performing DoD contract work. It required existing tools to be removed within 30 days of enactment, and applies to subcontractors, not just primes.
- Is Kimi K3 covered under Section 1532?
- Kimi K3 isn't named in the statute, but its developer, Moonshot AI, is a Chinese company, which puts it inside the law's broad 'covered nation' definition. There's no published exemption list, so any DoD contractor or subcontractor using it, or a tool built on it, should treat it as prohibited for that contract's performance.
- What is the Nvidia 'Open Weights' letter and does it undo the NDAA ban?
- It's an advocacy letter, not legislation. Nvidia CEO Jensen Huang published it on July 24, 2026 as his first post on X, and it grew from 25 signers to 50 within a day, including Microsoft, Meta, OpenAI, and Google. It argues against extending Chinese-model restrictions into a broader ban on open-weight AI in general. It has no legal effect on Section 1532, which is already enacted law.
- Does this affect construction work that isn't federal?
- Not directly today. Section 1532 only reaches DoD contract performance. But the Trump administration is reportedly weighing broader tools — Entity List designations, wider federal procurement restrictions, and liability rules — that could extend past DoD contracts, with an executive order possibly landing by the end of 2026 and fuller agency rollout in 2027.
- What should a GC or sub do about this now?
- Ask every AI-enabled tool vendor which model powers the feature and where that model's developer is domiciled, before using it on any DoD-funded job. If your firm built its own tool on an open-weight model to save cost, confirm the developer's country of ownership. Document the check — the removal obligation under Section 1532 falls on the contractor and subcontractor, not the government.