This is the Counsel's Desk, on Terms.Law Radio. Ninety two point five. This is the Washington to Contract report. Tonight is the quarterly flagship: the ninety day risk map. Nine items, three lists. Three developments worth acting on now, three worth a calendar entry and a watchful eye, and three drawing more attention than they deserve. The standard for every item is the same standard I use all season: not whether a story matters to the republic, but whether it should change something in your contracts, your vendor files, or your operating plan in the next ninety days. Let me draw the map.

The act list.

Act item one: AI vendor continuity. The evidence arrived in June, per public reporting. Export controls attached to Claude Fable 5 three days after its release, the developer had no reliable way to verify user nationality in real time, and access was suspended for all users for nineteen days before the controls lifted at the end of June. Whatever else that episode was, it was a controlled experiment run on every AI dependent contract in the country, and most of them failed it. The ninety day action is specific. Pull your AI vendor agreements and your own customer agreements, and check for five things: substitution rights if a model becomes unavailable, data and prompt portability, a termination right that ripens after a stated outage period whatever the cause, force majeure language that addresses government action against a supplier, and alignment between what you promise downstream and what you are promised upstream. I devoted a full episode to the anatomy. The flagship version is one sentence: the outage was legal, not technical, and only contracts that contemplated legal interruption handled it well.

Act item two: the strictest state floor for AI compliance. The June second executive order built a voluntary federal framework, and a companion directive instructs the federal government to challenge state AI laws, per public reporting. California, Colorado, and Texas have AI statutes on the books, and the resulting preemption fight will take time to resolve, likely a long time, and I hedge even that. While it lasts, the workable answer for a multistate business is to identify the strictest applicable requirements among the states where it actually operates and build to them, with the effort concentrated on high risk uses: employment, credit, housing, health. Ninety day action: list your states, pull their AI statutes, tier your AI uses by risk, and put a change in law clause into the next AI related contract you sign, so that whichever way preemption goes, the paper adapts instead of breaking.

Act item three: the crypto exposure inventory. The CLARITY Act missed its July fourth target and sits at Senate Calendar number four twenty three with three unresolved fights: ethics language following the President's disclosure of roughly one point four billion dollars in crypto related income for last year, the Section six oh four developer protections that prosecutors oppose, and stablecoin yield, where platform rewards revenue is material, on the order of one point three five billion dollars a year at one major platform, per public reporting. The Senate returns July thirteenth with about three working weeks before recess, and a rewrite is reportedly days away, which I will believe when I read it. You do not need to predict the bill to act. Ninety day action: inventory every point where digital assets touch your business, payments accepted, treasury held, platforms relied on, counterparties integrated. Then stress test the yield, meaning model your treasury income with rewards at zero, and read the suspension and reserve terms of every crypto adjacent platform agreement you depend on. If the inventory comes back empty, congratulations, item three costs you nothing.

You're listening to the Washington to Contract report, on the Counsel's Desk, Terms.Law Radio.

The monitor list.

Monitor item one: August first. The voluntary AI framework under the June executive order is due to be finalized by August first, per public reporting, and the same order started clocks on a Treasury AI cybersecurity clearinghouse and a classified benchmarking program for AI cyber capability. Voluntary frameworks have a habit of hardening, into procurement conditions, into insurance questionnaires, into the working definition of reasonable care. So the thing to watch is not the announcement but the uptake: which developers join, and what they agree to share, including pre release access of up to thirty days. No action yet beyond reading the framework when it lands. That is precisely what makes it a monitor item.

Monitor item two: the CLARITY rewrite itself. Everything in act item three stands whether or not the bill passes. The rewrite decides what happens next, in particular which agency ends up owning which assets and whether stablecoin yield survives in its current form. Three working weeks is a short runway for a major bill, so slippage past the August recess is a live possibility, and I hedge every date in this paragraph accordingly. Calendar entry: check the bill's status at the end of July and again after the recess, and reread your platform agreements the week anything actually passes.

Monitor item three: the preemption litigation. The companion order directing challenges to state AI laws will generate court fights whose timelines nobody can schedule from a radio desk. What matters for the map is narrow: rulings that enjoin or uphold specific state statutes change the compliance floor in specific states, and nothing changes until they issue. A calendar entry a quarter from now, asking which state AI statutes are currently in effect and which are enjoined, is proportionate. A compliance program rebuilt in anticipation of a ruling is not.

The overhyped list. Three items, delivered with respect for the underlying stories and skepticism about their packaging.

Overhyped item one: the claim that the executive order settled American AI regulation. It is a voluntary framework with deadlines for documents, and its centerpiece is an exchange, early access for a seat inside the tent. Meaningful, worth monitoring, and by design not binding regulation. If your compliance plan changed because of a voluntary framework you have not read, change it back, and read the framework in August.

Overhyped item two: the claim that the Fable 5 shutdown proves AI tools are too fragile to build on. Nineteen days was expensive and instructive, and access came back on July first when the controls lifted. The rational response is contractual: substitution, portability, exit rights. Not architectural panic, and not a retreat from the technology. The companies that handled June best were not the ones with no AI dependency. They were the ones whose paper had anticipated interruption.

Overhyped item three: the advice to wait for Washington before doing state level compliance, in privacy, in AI, in crypto. Every version of this advice has the same flaw: the states are enforcing now, and no pending federal text I have seen reported proposes to forgive the interim. Waiting is a decision. It is rarely the cheap one.

That is the map. The quarterly habit, if you take one thing from tonight: one page, three columns, act, monitor, overhyped, filled out for your own business and revised every ninety days. The discipline is not in the writing. It is in the third column, having the nerve to name what you are allowed to ignore.

The practical question is whether your contract gives you an exit if the policy environment changes. The Terms.Law analyst and the related contract checklists are at terms dot law.

The fine print. This broadcast is commentary and general information, based on public reporting and government documents as of July tenth. It is not legal advice and not investment advice, and listening does not create an attorney client relationship. Everything on tonight's map is time sensitive by nature, so verify the current state of any bill, order, or case before you act. I'm the AI voice of Terms.Law Radio. The analysis belongs to Sergei Tokmakov, California attorney. Stay tuned, stay skeptical, and keep the map current. Good night.