The site has two artifacts. One is the state bills, each read as what it changes from the laws before it; the other is the composite: for each obligation that state frontier AI law imposes (publish a frontier AI framework, report critical safety incidents, protect whistleblowers, and so on), it reproduces the strictest enacted version of that obligation, verbatim, in the words of the state that enacted it. Sections are ordered as a bill is ordered, each section carries the chip of the state whose words those are, and each carries its own effective date, because the strictest version of one duty may not be in force on the same day as the strictest version of the next.
The composite has two views: the enacted view (every obligation, whatever its effective date) and the in force today view (only what already binds).
Defined terms are glossed in brackets in our own typeface: [like this]. The bracketed text is ours; everything outside the brackets is the statute’s.
Every provision starts as a span copied out of an archived official text, together with the file it came from, its section cite, its effective date, and the URL of the official page. It is tagged against one baseline (California SB 53) as matching California, tightening California on a parameter California also regulates, or having no California analogue at all. A provision tagged as having no California analogue must still carry the nearest California text, so that the claim can be checked rather than taken on trust.
Category names are not ours to invent. The obligation categories that structure the composite follow the vocabulary the field already uses, and where a reading of a statute comes from someone else’s work, that work is cited on the row.
Two things on this site are ours rather than the statutes’: the map’s legend buckets and the “also on the books” scope labels are editorial groupings written here to make the picture skimmable, not categories any legislature enacted or any tracker publishes.
The site does not grade states against each other.
Annotations are drafted with AI assistance. The verifier checks quotations, not annotations: the quoted text is the record, annotations are a reading aid, and a misleading annotation is a bug; report it.
Each archived file carries the source URL and the UTC retrieval time in its header. Quotations are matched against these files, not against the live web, so a page that changes upstream cannot silently change what this site says it says. Statuses on the Massachusetts page follow the bill history published on malegislature.gov: the House non-concurred in the Senate amendment on 30 July 2026 and committees of conference were appointed in both branches.
The obligation categories adapt pillar language from the SB 53 coalition letter to Gov. Newsom (Encode AI and 22 other signatory organizations, 24 September 2025), and the framing of what these laws still leave uncovered follows the Secure AI Project’s statement of policy priorities. Neither organization is responsible for how the vocabulary is used here.
The annotated-statute format owes a debt to sb53.info, Miles Kodama’s annotated SB 53 (written while at GovAI). All quotations on this site are drawn directly from official statute texts. The state outlines are from simplemaps.com, free for commercial use.
Corrections are welcome. If a quotation does not match the enacted text, if a section is attributed to the wrong state, or if a law has moved since 1 August 2026, that is a defect and it will be fixed. Maintainer: Jay Kim, in a personal capacity. File corrections as GitHub issues or by email to jay.ifp.automation@gmail.com.
Corrections that changed a page, and every republication of the site, are listed on the changelog.