A design test for AI governance, written for the committees that will hold the oversight pen
· Samuel R. Lammie, with Claude (Anthropic) and ChatGPT (OpenAI)
Disclosure: the co-authors of this piece are large language models built by companies that profit from AI adoption and whose systems would fall under the oversight it describes. Weigh its contributions accordingly.
The 120th Congress convenes in January with new committee chairs and new oversight priorities. Whoever holds those gavels will hear a great deal about artificial intelligence: frameworks, pilots, task forces, guardrails. This piece offers them one test to apply to all of it. For any AI provision, ask where it binds. A governor slows the machine itself. A stamp is a named person's approval before the irreversible step. An after-action review learns from what already happened. Most of what is sold as AI oversight is an after-action review dressed as a stamp. The difference decides whether anyone can actually stop a system once it is running.
I write as a retired federal land manager, not as a partisan. My federal career ran from Bureau of Indian Affairs forestry on Apache reservations in Arizona, through the National Park Service, to more than two decades in the Forest Service, ending as the Northern Region's geospatial program manager. In 2025 I completed Carnegie Mellon's certificate in Managing Artificial Intelligence Systems, so I come to this from both sides: as someone who ran the systems agencies depend on, and as someone trained in how AI systems should be governed. The test below is the one I would want any committee to apply, whichever party chairs it.
Where things stand
Federal AI policy now runs on three instruments, and none of them is a statute.
The first governs how agencies use AI. OMB Memorandum M-25-21, issued April 3, 2025, requires each agency to name a Chief AI Officer and identify "high-impact" AI, meaning systems whose output is a principal basis for decisions that significantly affect rights or safety. For those systems it sets minimum risk practices, including "human oversight, intervention, and accountability" and a "timely human review and a chance to appeal." It also contains the strongest sentence in current federal AI policy: if a high-impact use case does not comply, "the agency must safely discontinue use of the AI functionality."
The second governs who may regulate AI at all. Executive Order 14365, signed December 11, 2025, created a Justice Department AI Litigation Task Force to challenge state AI laws. It directed Commerce to list "onerous" state laws within 90 days, tied some federal funding to state alignment, and asked for a legislative proposal to preempt conflicting state rules. It carves out child safety, data center infrastructure and state procurement. An executive order cannot preempt state law on its own; that takes Congress.
The third is still a draft. In June 2026, Representatives Lori Trahan (D) and Jay Obernolte (R) released a discussion draft of the Great American AI Act that would preempt state laws on AI model development for three years while leaving states free to regulate deployment and use. It drew fire from both directions: from Democrats, civil rights and labor groups for preempting too much, and from many Republicans for preempting too little. In July the two sponsors introduced one piece of it as a stand-alone bill requiring independent audits of large frontier developers.
That is the ground the new chairs inherit: a use-side memo with a real brake in its text, a preemption push with no statute behind it, and a bipartisan draft that splits development from use. All three can be read with the same test.
The test: governor, stamp, or after-action review
A governor on an old steam engine did not report that the engine had run too fast. It closed the throttle before the engine could. That is the first stage: friction built into the system itself, through permissions, rate limits, spending caps and required confirmations. A governor slows the machine. It does not decide.
The second stage is the stamp: a named, accountable person's final approval before the irreversible step. Engineers stamp drawings; surveyors stamp plats. A stamp says a qualified person looked, judged, and will answer for it. It is the only stage where refusal lives.
The third stage is the after-action review, the wildland fire community's term for learning from what happened: an audit, a report, an inspector general finding, a hearing. By then the agent is already out the door. In earlier pieces I called this a gate. After-action review is the more honest term, because a gate implies it stops something.
All three have their place. Governors buy time, and after-action reviews are how institutions learn. But only the stamp puts a person between the system and the harm, and AI systems increasingly act faster than any review can follow.
Applied to the current instruments, the test sorts quickly. M-25-21's discontinue clause is a governor at the program level: noncompliant systems must stop. Its compliance reporting is an after-action review. Its human-oversight requirement is a stamp only if the human approves before an AI-driven decision takes effect; afterward, it is a review. Executive Order 14365 is neither, because it governs who may regulate rather than how systems behave. The Trahan–Obernolte draft would remove state-level governors on model development for three years. The federal instrument offered so far is an independent audit, which is an after-action review. Audits are worth having. They are not a stamp.
The question for a committee is never "does this provision mention oversight?" It is "does this provision bind in the machine, at the stamp, or only in the review afterward, and on whom?"
The rate problem
Stability is a rate, not a state. Living systems run at nested speeds: a leaf turns over in a season, a hardwood stand in a century, a soil in millennia. Systems fail when one part runs at a speed the parts that govern it cannot match. A forest plan revised every fifteen years cannot govern a beetle outbreak that moves in two seasons.
AI oversight has the same flaw. An agent acts at machine rate, in seconds. The instruments that oversee it run at document rate: annual inventories, compliance reports, hearings scheduled months out. A human "in the loop" who reviews a weekly digest of decisions already executed is not in the loop. That human is conducting an after-action review, inspecting what has already happened.
The design response is not to make hearings faster. It is to put the governor where the rate is: in the system's permissions, its spending limits, its required confirmations before irreversible actions. Those are engineering choices, and they can be written into procurement contracts and agency policy. Committees can ask for them by name. And for every irreversible action, they can ask who holds the stamp.
Voluntary in name
The NIST AI Risk Management Framework is voluntary. So are most industry safety commitments. But "voluntary" describes the text, not the effect. When a framework is written into procurement requirements, cited by courts as the standard of care, or demanded by insurers, it becomes mandatory in effect. When a mandatory requirement carries no audit, no consequence and no published compliance record, it becomes voluntary in effect.
The test is the same in both directions: follow the instrument to the point where someone bears a cost for ignoring it. If no one does, it is guidance, whatever the cover page says.
This matters for M-25-21 directly. Its discontinue clause is mandatory in text. Whether it holds in practice depends on whether anyone outside the agency can see which high-impact systems were found noncompliant, and whether any were actually switched off. A committee can ask that question with a single letter.
The Petrov clause
In September 1983, Stanislav Petrov, a Soviet duty officer, watched an early-warning system report incoming American missiles. He judged it a false alarm and did not pass it up the chain as an attack. He was right. The system had a human in the loop, and at the moment of action the human held.
Petrov's case is usually told as a story about courage. For a committee, it is better read as a design specification. Three things had to be true for his refusal to count. He had to be positioned before the irreversible step, not after it. He had to have enough time and information to judge. And he had to be able to refuse without the refusal being overridden by procedure.
Every human-oversight provision in AI policy can be held to those three conditions. Is the reviewer placed before the action or after it? Is the reviewer staffed, trained and given the time to actually review, or is one person approving hundreds of outputs a day? Is a refusal protected, so that a federal employee who halts a system is backed rather than disciplined? A requirement that fails any of the three is not a stamp, however it is worded. It is an after-action review.
The second condition is already failing. In remote sensing, a classifier that maps forest cover from satellite imagery is only as good as its ground truth: field plots where a person walked in, measured the stand and recorded what was actually there. Without those plots the map still looks finished. It is simply unverified. Every Petrov clause assumes a reviewer with that kind of field knowledge and the time to use it.
In October 2026, USDA's IT program manager told a Washington panel, of keeping people overseeing AI work: "I think that's untenable in our industry or in government — we just don't have the resources anymore." That is the second condition conceded in public, before anyone has tested the first or the third.
I managed geospatial work for the Forest Service's Northern Region, 25 million acres across Montana, Idaho and the Dakotas. An oversight framework that requires human review without staffing the reviewers has a stamp on paper and no one to hold it. Committees overseeing AI deployment should also oversee the workforce that has to check it.
The question is not whether a document names someone who may refuse. It is whether that refusal holds load at the moment the system acts.
The first 90 days
None of this requires new legislation to begin. A committee with oversight jurisdiction can start with four requests.
Ask for the discontinue ledger. Request from each major agency its inventory of high-impact AI under M-25-21, which systems were found noncompliant, and which were actually discontinued. The memo's compliance deadlines have passed, so the answers should already exist. A clause that has never been exercised has not yet been shown to hold load.
Ask where the human sits. For each high-impact system, ask whether human review happens before the AI-driven decision takes effect or after. Ask how many decisions each reviewer handles per day. The answers sort stamps from after-action reviews faster than any policy document.
Ask what protects a refusal. Ask whether any agency has written guidance protecting an employee who halts an AI system in good faith. If none exists, that is the cheapest way to make a stamp real: one paragraph of policy.
Put the verification workforce in the same frame. When an agency reports AI adoption, ask in the same hearing what has happened to the field and technical staff who would catch its errors. Adoption and verification capacity should be reported together, because one is meaningless without the other.
Any preemption bill can then be read through the same test. If it removes state governors, what replaces them: a federal governor, a stamp, or only an after-action review?
The throttle
The ridges above Leading Creek are bare this week, and with the leaves down you can see how the hillside is actually built. Oversight is the same. Strip away the vocabulary of frameworks and principles, and the structure underneath is simple: at some point between a request and a result in the world, either someone can stop the machine or no one can. The new committees will decide where that point sits. They should decide it on purpose.
Sources
- OMB M-25-21, Accelerating Federal Use of AI through Innovation, Governance, and Public Trust (govinfo)
- Akin Gump summary of M-25-21
- White & Case on Executive Order 14365
- Global Policy Watch on the Great American AI Act draft
- Washington Examiner on the stand-alone audit bill
- Tech Times on USDA and human oversight of AI
- Forkast on the M-25-21 deadline

