This Week in Permitting Tech June 16, 2026: When the Government Can Pull Your AI Model
Three days after launch, the US government ordered Anthropic to pull its two most powerful models, raising a procurement risk the permitting tech industry hasn't had to reckon with before. Also this week: the Permitting Council put $14 million behind three federal agency AI projects, Florida's data center permitting law takes effect July 1, and the Senate is still the wall permitting reform legislation cannot get over.
NOTE: I delayed sending a day to see if any permitting stories spun out of Anthropic's pullback of Fable and Mythos, but no one bit. I think there are a few stories percolating under the surface, but they'll take time.
A government AI pullback sets a precedent nobody was ready for
Every permitting technology pitch deck in the last two years has AI at the center. AI-assisted plan review. AI-drafted Environmental Assessments. AI agents that route applications, flag errors, and surface precedents. The unspoken assumption behind all of it: once you deploy a model, it stays deployed. This week that assumption got stress-tested.
On June 12, the US government issued an export control directive requiring Anthropic to suspend access to Fable 5 and Mythos 5 for any foreign national, whether inside or outside the United States. Because Anthropic cannot distinguish foreign nationals from domestic users in real time, it pulled both models for everyone — three days after they launched. The stated basis was a reported jailbreak technique: asking the model to read a codebase and identify software vulnerabilities. Anthropic publicly disputed the severity, noting that the capability is routine among security professionals and available in other deployed models, including GPT-5.5. The company said it had found no universal jailbreak and argued that the government's standard, applied consistently, would halt all new deployments of the Frontier model across the industry. It is complying while disagreeing.
Social media did what social media does: complaints about lost workflows, arguments about what Fable could and couldn't do, speculation about the jailbreak. That is not the conversation that matters here. What matters is in Washington: the US government can now revoke a commercial AI model, at speed, with a same-day directive, and without a transparent technical process. That is a different risk from a model being deprecated or a vendor shutting down. Those happen on timelines you can see coming. An export control directive arrived at 5:21 PM on a Thursday and took effect immediately.
If you are building permitting workflows on frontier AI, or procuring systems that do, this is a risk category that didn't exist two years ago. Which models are at exposure? What happens to an AI-assisted EA workflow when the underlying model disappears overnight? Who owns the fallback plan, and who owns the liability when there isn't one? Nobody has clean answers yet. But these questions belong in the RFP.
Anthropic statement · Bloomberg · The New Stack
Permitting Council awards $14 million to USACE, NTIA, and the Coast Guard
On June 12, the Federal Permitting Improvement Steering Council announced grants totaling just over $14 million from its Environmental Review Improvement Fund. Three agencies get the money: the Army Corps of Engineers ($7.1 million for a unified AI-augmented regulatory workflow system), NTIA ($2.8 million for an AI agent that drafts Environmental Assessments for broadband projects), and the Coast Guard ($4.8 million for an online bridge permit application system to replace a largely manual process).
The USACE award is the one to read carefully, and the press release buries the most telling detail: the Corps currently runs its regulatory program across five separate legacy systems. Five systems, one agency, one regulatory program. When the announcement talks about reducing "staff-time spent on routine data management" and enabling AI adoption, it is actually describing the absence of the data foundation that a modern workflow requires. The $7.1 million is not a technology upgrade. It is the infrastructure that should have existed twenty years ago.
The NTIA EA Agent Tool is worth watching on its own. NTIA estimates the tool could cut Environmental Assessment timelines by 30 to 60 days and save $4.5 to $9 million on the BEAD broadband program alone. Those numbers depend on the tool working as described: an AI drafting EAs for projects that can't be categorically excluded, with subject matter expert review before anything goes out. Plausible for routine projects with decent applicant data. The failure mode is the same as any AI drafting tool: confident-sounding output built on incomplete input.
Permitting Council press release
USACE's five-system problem is everyone's coordination problem
The Corps' regulatory program issues permits under Section 404 of the Clean Water Act and Section 10 of the Rivers and Harbors Act, which means it touches nearly every major infrastructure project in the country. It also, per the Permitting Council announcement, runs its workflow across five legacy systems that don't communicate with each other.
That's not an obscure technical detail. It's why inter-agency coordination on Corps permits requires so much manual effort, why tracking a permit's status is harder than it should be, and why the Corps hasn't adopted AI tools that have been commercially available for years. You can't build an AI layer on top of five disconnected systems; the models have nothing coherent to work with and no workflow to plug into. (OK, technically you can, but it won't be good.) The $7.1 million funds the precondition, not the outcome.
The Corps has a history of ambitious modernization projects that expand in scope and slip in timeline. The Permitting Dashboard — meant to give the public real-time visibility into FAST-41 projects — has been a running explanation of why the data isn't quite ready. This initiative will likely take three to five years to yield measurable results. What the announcement does is name the problem and put a number on fixing it, which at least creates a basis for accountability.
Army Corps of Engineers Regulatory Program · Permitting Dashboard
Florida's data center law takes effect July 1, testing local permitting authority
Florida Governor Ron DeSantis signed SB 484 on May 7, and it takes effect July 1. The law covers several things at once: it bars utilities from passing data center electricity and infrastructure costs to residential and small-business ratepayers, requires large-scale data centers (50 megawatts or more) to pay the full cost of grid service, establishes a separate water consumptive use permit process for large data centers, and preserves local government authority to deny data center development.
The ratepayer protection piece is the politics. The permitting piece is what matters here. Florida is creating a distinct permitting track for data centers, with its own application requirements, its own threshold (50 MW), and a provision that treats any major modification as a new initial application rather than an amendment. That last part is the substantive design choice: data center operators who want to expand significantly can't use the softer path of amending an existing permit.
This is where state and federal intent diverge. EO 14318, the federal data center permitting executive order, also takes effect July 1, and it pushes toward faster federal review. Florida's law pushes toward more rigorous state and local review, with explicit protection of municipal denial authority. Projects large enough to need both federal FAST-41 treatment and Florida's new data center permit will navigate two tracks with different incentive structures and different definitions of "done." Nobody has written the coordination protocol for that yet.
Florida SB 484 · Data Center Dynamics · Governor's press release
The Senate remains the place where permitting reform goes to wait
The SPEED Act passed the House 221-196 last December. The ePermit Act has eight bipartisan Senate sponsors. The CERTAIN Act and McCormick's bill target specific choke points from different angles. None of them have moved in the Senate this month.
The core problem, covered in the June 8 issue, hasn't changed: Senate Democrats have made clear they won't support bipartisan permitting reform while the administration slow-walks renewable energy permits. That standoff doesn't have an obvious resolution. Both sides have leverage, and neither is exactly wrong. The administration wants reform that prioritizes fossil fuels and critical minerals; Democrats want a deal that includes renewables; and the constituency for sector-neutral permitting acceleration is smaller than the lobbying noise suggests.
Multiple bills address the same structural problem from different angles, each with a different coalition, none with enough votes to move. The Permitting Innovators Expo on July 31 will put technology solutions in front of agency leaders. Whether those solutions ever connect to the legal authority that would make them mandatory is the open question. The Expo won't answer it.
C2ES federal permitting reform tracker · Utility Dive · Bipartisan Policy Center on SPEED Act
State data center legislation is rewriting local permitting in real time
According to MultiState, more than 300 data center bills have been filed across 30-plus states in 2026. Most deal with energy costs and tax incentives. A smaller group addresses permitting authority directly, and they pull in opposite directions.
Some states have fast-tracked data center approval by pre-empting local zoning, treating data centers as infrastructure that doesn't require case-by-case municipal review. Others have reaffirmed or created municipal authority to reject, delay, or condition data center development, often in direct response to specific large projects that communities opposed.
Florida's SB 484 is in the second camp. So are the 11 states where moratorium bills have been introduced, though most haven't passed. The result is a patchwork: before committing to a site, a developer needs to map state pre-emption rules, local zoning authority, special permit requirements, and utility rate structures for that specific location. That's the same problem the permitting technology industry has been trying to solve in environmental review for years. The rules exist. Knowing which ones apply where requires more expertise than any single company or agency holds. If you're building siting tools for data centers, the opportunity is structurally identical. The governance is just newer.
MultiState data center tracker · ArentFox Schiff analysis · National Law Review
CEQ Permitting Innovators Expo set for July 31
The Permitting Innovators Expo is confirmed for July 31, 2026, in the Washington, DC area. Up to 50 solutions from the June 2 submission pool will be selected and invited to present to federal agency leaders. A Solutions Catalog will follow, distributed across the government.
What happens after the catalog is the real question. Federal agencies regularly receive technology assessments, innovation reports, and solution catalogs, and the conversion rate from catalog to contract is substantially lower than events would suggest. The Expo gets technologies in front of the right people. What turns that into a contract is usually a pre-existing relationship, a specific appropriation, or a mandate. Compare this week's Permitting Council grants ($14 million tied to specific agency problems with named project sponsors who have to deliver against them), and the difference between an event and an investment is pretty clear.
Permitting Innovators program · White House CEQ announcement
Permitting Tech is an independent news site covering investment, products, and policy in permitting technology. Written by Boon Sheridan.
