Explainer

The 2026 Midterms and AI Oversight: What Changes Procedurally

The midterm elections changed which party controls both chambers — and with it, the agenda-setting machinery of Congress. This post describes what changes procedurally. It makes no predictions and takes no position; the tracker will simply log what happens.

What actually changes with new gavels

Three pieces of committee machinery move when control changes:

• Agenda control. Committee chairs choose which discussion drafts get hearings, which get markups, and which sit in a drawer. For two years, frontier-AI proposals largely lived in that drawer. Hearing schedules for the 120th Congress will show what has changed.
• The record. Oversight letters, witness testimony, and hearing transcripts create the factual record on which later rulemaking stands — whatever anyone’s preferred policy turns out to be.
• Veto points flip. Provisions a prior chair would never schedule can now move, which shifts the binding constraint from gatekeeping to drafting quality. That cuts in every direction: it allows more legislation, not necessarily more of any particular kind.

Three things the tracker will watch

None of these are predictions. They are the specific, observable events the log is designed to capture.

1. The first hearing’s witness list

Committee intent shows up in who is invited to testify. A hearing organized around safety cases and dangerous-capability evaluations documents one kind of record; one organized around datacenter permitting and competitiveness documents another. Both can occur in the same Congress. The hearing record — not the press release — is what later bills cite, so the log records witness lists, testimony titles, and outcome documents.

2. Preemption clauses

The most consequential provision in any AI bill is usually not its headline requirement but a paragraph titled something like “preservation of State authority” — or its opposite. Mechanically: a preemption clause makes the federal standard a ceiling rather than a floor, overriding stronger state laws. Whether that is good or bad policy is exactly the kind of judgment SafeASI doesn’t make; what the tracker does is record which clauses appear, in which bills, with what wording. (See the pending explainer: State AI Laws and the Federal Preemption Debate.)

3. Requirements paired with funding titles

Requirements without administrative infrastructure tend not to be enforced, whatever their merits. When a bill moves through committee, the funding title is where enforcement capacity is created or removed — so amendments that strip a funding section are logged alongside votes on the requirements themselves.

The calendar problem

A typical bill takes nine to fourteen months from introduction to signature, if it gets there. The 120th Congress organizes in January; the legislative year runs to the August recess, then dissolves into appropriations season. Meanwhile the lame-duck session of the 119th is still operating, and any AI bill moving in December will be logged with the same status fields as anything introduced next year.

What the tracker will record

Every bill that touches frontier-scale AI gets an entry: bill number, chamber, committee, topic category, procedural status, last action with a date, and a link to the bill text on Congress.gov. Every hearing gets a calendar entry and, after the fact, a record link. That’s the whole method — describe what happened, when, with a source. You bring the interpretation.