USMCA's Source Code Rule Can Reach an AI Auditor Who Copies Nothing · Traverse Analysis
USMCA's Source Code Rule Can Reach an AI Auditor Who Copies Nothing
USMCA Article 19.16 bars compulsory access to Canadian- or Mexican-owned source code, so an on-site AI audit can raise a treaty issue even if nothing is copied. A January 12 comment can ask the parties to define when an assessor may open the file.
A Canadian developer that lets an auditor read its source code on a locked terminal has still granted access. bars a party from requiring "the transfer of, or access to" source code owned by a person of another party as a condition for the import, distribution, sale or use of the software. A U.S. audit mandate tied to sale or use that keeps every copy inside the developer's building can therefore raise the treaty question as squarely as one that ships the code to Washington.
That reading now has a live federal test. On November 19, Rep. Lori Trahan released an updated FRONTIER Act section-by-section that would guarantee embedded access for independent verification organizations at the largest frontier developers. Full bill text will follow in the coming weeks, according to the release. The next day, Rethink Trade, a program of the American Economic Liberties Project, called the USMCA review an opportunity to strip Article 19.16 out of the agreement.
For a developer drafting comments in the 2027 USMCA review, the useful request is narrower than deletion. Article 19.16 already accommodates a regulator examining code in a specific inquiry. It is silent on an outside assessor with a standing access plan, and that gap is the one a comment can define.
What the November outline would open to assessors
Under the FRONTIER Act 2.0 summary, large frontier developers, those with at least $1 billion in AI-related development spending over 36 months, would commission an annual independent audit of compliance with their published frontier AI framework. The redacted audit report would be published and sent to the Secretary of Commerce. Section 10 adds that any redaction comes with a justification and an unredacted copy to the Secretary.
Very large developers, at $5 billion or more, would also retain a licensed independent verification organization for each category of catastrophic risk, with a resident team on site. The developer would first choose its own assessor. Once licensed organizations have capacity for a category, the Secretary would assign one, and later the outline combines assignment with developer choice. A single access plan, proposed by the lead verifier and approved by the Secretary, would cover unredacted materials, model weights, internal-use models and personnel. Source code is not on that list.
Section 6 would require large developers to register with the Secretary as a condition of developing, deploying or operating any foundation model. The outline does not say whether refusing a verifier a particular source file would put that registration at risk. That link is what turns an access request into a condition of sale or use under Article 19.16.
Why viewing without copying is still access
The July bill, H.R. 9925, introduced by Rep. Jay Obernolte with Trahan and four other cosponsors, already shows the mechanics. Section 4(c)(1) would give the developer's auditor timely access to "materials, records, personnel, systems" and other information reasonably necessary for the audit. To protect trade secrets and other listed interests, the developer could restrict note-taking, copying, retaining or removing materials and could require on-premises review. Rethink Trade argues that "systems" could reach source code. The bill's preemption clause in section 9 names source code expressly among the third-party access requirements that states could no longer newly impose, subject to listed exceptions. The November outline replaces that approach with a federal floor that preserves state laws at least as protective.
Illinois has already enacted the same security model. Beginning on the later of January 1, 2028 or 90 days after a developer first qualifies as large, Public Act 104-0538 requires an annual third-party audit with access to all materials reasonably necessary. It lets the developer require on-premises review and limit copying. Those protocols limit what an auditor takes away, but Article 19.16 turns on what the auditor must be shown.
Ownership sets the outer edge. A U.S. measure applied to a U.S.-owned model does not engage the article, even if that model is sold in Canada.
Request concerning Canadian-owned software sold in the United States
What Article 19.16 turns on
Send Commerce an audit finding that a safety test failed
The finding can be reported without code or an algorithm expressed in it. An appendix reproducing the code changes what Commerce receives.
Give the verifier model weights
H.R. 9925 section 2(17) defines a weight as a numerical parameter adjusted through training. A request for weights alone does not establish access to source code.
Let an assessor read a source file under a standing access plan
On-site viewing is access. The question is whether the developer may refuse without losing the right to deploy or sell.
Preserve a file for a regulator examining a specific incident
Paragraph 2 allows a regulatory body to require preservation and availability for a specific investigation, subject to safeguards against unauthorized disclosure.
Where the specific-inquiry exception stops
Article 19.16.2 lets a regulatory body or judicial authority require code to be preserved and made available to the regulatory body for "a specific investigation, inspection, examination, enforcement action, or judicial proceeding." Footnote 6 adds that such disclosure shall not be construed to negatively affect the code's trade-secret status. A pre-market inspection ordered by a regulator can fit that text. A resident verifier that sets the scope and frequency of its own assessments, and reports at least every six months, is harder to describe as the regulatory body conducting a specific examination. The Rethink Trade paper reads the exception as tied to an event already underway, a stakeholder position rather than a ruling.
Chapter scope adds a second variable. Under Article 19.2.3(b), the whole digital trade chapter, except Article 19.18 on open government data, does not apply to information held or processed by or on behalf of a party, or to measures related to that information, including measures related to its collection. A verifier assigned by the Secretary and paid from a fee-funded pool may be read as collecting information on behalf of the United States. A developer-selected auditor checking a self-written framework is a weaker candidate. Neither reading has been tested.
What the UK-Singapore text adds
The Business Software Alliance urged USTR to keep the bar on forced transfer or disclosure of source code and algorithms as a condition for market access. Keeping the rule and defining the assessor are compatible. The United Kingdom and Singapore did both in their Digital Economy Agreement. Article 8.61-K(1) mirrors the USMCA prohibition. Paragraph 3 then extends the carve-out to a designated conformity assessment body, drops the word specific and adds the monitoring of compliance with codes of conduct and other standards, still subject to safeguards against unauthorized disclosure.
Treaty text is a separate lever from enforcement. Proposals to take Chapter 19 out of dispute settlement would change who can bring a claim. Rewriting Article 19.16.2 would change what a regulator may require in the first place.
What to put in the January filing
The USTR notice sets a January 12, 2027 deadline, one minute before midnight EST. Written comments go to docket USTR-2026-0595, and requests to appear with a summary of testimony go to USTR-2026-0596. A developer can ask the three governments to state when a regulator may designate an independent assessor to inspect code, for what defined purpose, what the assessor may retain and who answers for an unauthorized disclosure. Any text change would still pass through each country's amendment approval and implementation steps.
The comment need not include code. It can name the owner, the decision that depended on opening a file and what test results alone could not show. When Trahan's full text appears, the provision to read first is the consequence of refusing a verifier access to a source file. If refusal can block registration or deployment, Article 19.16.1 is engaged for Canadian- and Mexican-owned software. If the plan keeps code out of scope, the treaty question shrinks to weights and documents.
Daily Trade Brief
Get the next one in your inbox.
New U.S. trade actions and the analysis that changes an import, customs, or counsel file, on weekday mornings after you confirm your address.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.