CounterpediaKnowledge you can trace back to the source.

Federal Preemption of State AI Laws: 181 Bills and No Record Governance Among Them

Republished editorial · Edition 1 · Updated 2026-02-19 · Ask about this record (Deterministic Ask v0.1) →

profileCounterpose Publicationcounterpose_publicationsource kindcaptured_counterpose_signal

Editorial republication

This page republishes captured Counterpose editorial from the Counterpedia admitted pool. It is not a governed Counterpedia record. This surface does not establish capture, source verification, or claim truth. The disclosures below are render-time only and assert no substrate verification, admission, or enforcement.

Verification posture (derived from this record)

  • This page is not source-verified by Counterpedia.
  • No SRS publication-ingest receipt is established for this editorial republication on this render surface; it is not receipt-verified or cryptographically validated.
  • Claims here are republished editorial, not admitted as verified fact by Counterpedia.
  • No registered source captures are anchored to this record.
  • No citation spans are present in this record.
  • No Counterpedia lineage / audit events are recorded for this record.

At a glance

Editorial thesis
Editorial thesis not declared
Publication
Counterpose CP-5 · captured editorial
Edition
CP-SIG-5-ED-1
Sources
Evidence not yet indexed
Verification
Not source-verified by Counterpedia

Signal body

# Federal Preemption of State AI Laws: 181 Bills and No Record Governance Among Them

Counterpose | CP-5 | February 19, 2026

A publication of Vega Commons Project, Inc.

---

A December 2025 executive order established a DOJ AI Litigation Task Force to challenge state AI laws and directed Commerce to identify state regulations requiring challenge within 90 days. The White House conditioned broadband funding on states not enacting conflicting AI laws and sent memos opposing specific state bills, including a Utah bill requiring frontier AI developers to publish safety plans. As of February 19, 2026, the 90-day identification deadline was approaching.

A custody surface is the set of records an AI system generates during operation that can be discovered, subpoenaed, or compelled through legal process. An interaction record is the log of what a user asked, what the system responded, and any reasoning the system performed.

At the same time, 181 AI and privacy bills were tracked across state legislatures. Chatbot bills advanced in Virginia, Washington, Utah, Arizona, and Hawaii. Tennessee passed a health AI bill. None of these bills addresses the lifecycle of AI interaction records. They regulate transparency (tell users it is AI), safety (detect self-harm), or discrimination (prevent bias). The record governance layer sits beneath all of these concerns and is addressed by neither the state bills the federal government seeks to preempt nor the federal framework it proposes as a replacement.

Both sides of the preemption fight absorb political energy without either addressing the custody question. State bills regulate platform conduct toward users. Federal preemption removes those regulations. Neither layer governs what happens to the records generated during every AI interaction: who retains them, for how long, under what lifecycle controls, and what happens when they are demanded in legal proceedings.

A governance standard that addresses platform behavior at the record layer operates regardless of which regulatory level prevails, because it addresses infrastructure architecture rather than governmental authority. The preemption debate determines which government can regulate AI. It does not determine whether the records AI generates are governed.

---

## Sources

| Source | Date | Description | URL | |--------|------|-------------|-----| | White House, Executive Order on AI preemption | December 11, 2025 | DOJ task force, Commerce identification mandate | | | Roll Call | February 19, 2026 | 181 state AI bills tracked, preemption memo details | |

---

## Amendment Log

*No amendments to date.*

---

The observations presented reflect analytical assessment of publicly available information and do not constitute legal, insurance, or investment advice. Counterpose maintains no formal relationship with any vendor, regulator, or standards body referenced in this publication.

Technical details
record id
CP-SIG-5
current edition
CP-SIG-5-ED-1

    This record declined to admit the candidate. A refusal is not a finding that the opposite claim is true, and does not establish that this claim is false.

    Every candidate this record evaluated was admitted.

    This record carries no governed lifecycle history to display.

    For agents and developers

    Public projection

    Machine-readable projections of this same governed record. A bundle appears here only when the public SDK supports it; committed demonstration fixtures are listed separately below and are not supported artifacts.

    Page model
    JSON

    This record has no supported portable export bundle. The public Counterpedia SDK supports one bundle format, and only records carrying a claim lifecycle with a separately owned verification report produce it.

    Demonstration and historical artifacts

    Not supported machine artifacts. The file below is a committed demonstration fixture, kept reachable for inspection and reproducibility. It declares the fixture bundle format, which the public client and the MCP adapter both refuse with a typed unsupported-format result. Reachability is not support.

    Demo / historical fixture bundle (unsupported)
    Unsupported demonstration fixture JSON

    Verification artifacts

    No committed verification report is attached to this record.

    Human-readable receipt →

    Verification workbench →

    For developers →