Guide · AI governance · about 8 minutes

AI governance cheatsheet: dates, frameworks, red flags

The AI governance track on one page: the dates that decide what applies when, what's still in motion, which framework asks what, how to tell which rules touch a system, the order of work for an engineer, and the phrases that should make you look closer. Each row links to the lesson that explains it. Checked November 7, 2026, and dated so you know how fresh it is.

Last checked November 2026

How to use this page

Checked: November 7, 2026. AI rules are moving faster than almost anything else on this site: dates in this page have changed during 2026, and some will change again. Treat every date as "as of" the line above, and check the source before you rely on it. Every row links to the lesson that explains it, with its sources.

Not legal advice. This page helps you read the rules, take part in a review and ask better questions. Anyone with real obligations needs a lawyer who practises in them.

Three habits that make everything here easier:

  • Classify by use, not technology. The same model can be minimal risk in one product and high-risk in another. What the output is used for, and whether it decides about people, sets almost every obligation.
  • Ask for evidence, not answers. A vendor's "yes", a reviewer's approval and a passing test all need something behind them: a document, a planted error caught, a test that could have failed.
  • Date everything. A compliance note without a date is a guess. Write down when you checked, and what.

Key dates

What applies when, oldest first. Bold rows are still to come.

DateWhatWhereLesson
Jan 26, 2023NIST AI RMF 1.0 released (voluntary)US2
Jul 5, 2023NYC Local Law 144: yearly bias audits for automated hiring toolsNew York City5
Dec 2023ISO/IEC 42001 published: a certifiable AI management systemInternational3
Jul 26, 2024NIST AI 600-1, the Generative AI ProfileUS2
Aug 1, 2024EU AI Act in force (applies in stages)EU4
Jan 23, 2025EO 14179: revoked the 2023 AI orderUS federal5
Feb 2, 2025EU AI Act: prohibited practices (Article 5) and AI literacy (Article 4)EU4
Apr 3, 2025OMB M-25-21 (using AI) and M-25-22 (buying AI) replace the 2024 memosUS federal5
Jul 23, 2025America's AI Action Plan, with EOs 14318, 14319, 14320US federal5
Aug 2, 2025EU AI Act: general-purpose AI model rules; penaltiesEU4
Oct 1, 2025M-25-22 applies to new AI contractsUS federal5
Dec 11, 2025EO 14365 (challenging state AI laws) and OMB M-26-04 (buying language models)US federal5
Jan 1, 2026California SB 53, Texas TRAIGA, Illinois HB 3773 take effectStates5
Jul 27, 2026EU Digital Omnibus (Regulation (EU) 2026/1744) in force: dates below movedEU4
Aug 2, 2026EU AI Act Article 50 transparency, for new systemsEU4
Aug 2026OWASP Top 10 for LLM Applications, 2026 editionInternational7
Sep 29, 2026EO 14434: agencies say "super intelligence" for AI in their own documentsUS federal1
Dec 2, 2026EU: new bans (nudifiers, child sexual abuse material); content marking for systems already on the marketEU4
Jan 1, 2027Colorado SB 26-189, New York RAISE Act, California's automated decision-making rulesStates5, 7
Aug 2, 2027EU member states' AI regulatory sandboxesEU4
Dec 2, 2027EU high-risk duties for Annex III uses (hiring, credit, education, benefits...)EU4
Dec 11, 2027OMB M-26-04 expires, unless renewedUS federal5
Aug 2, 2028EU high-risk duties for AI in Annex I regulated productsEU4

Still in motion

What to check before relying on anything above:

WhatStatus as of Nov 7, 2026Lesson
NIST AI RMFBeing revised under the AI Action Plan; check which version you cite2
M-25-21's high-impact deadlineThe memo says 365 days (April 2026); some trackers say September 22, 2026. No official extension found5
Federal preemption of state AI lawsEO 14365 lawsuits and funding conditions under way; no court has struck down a state AI law on those grounds; no federal statute5
FTC policy statement on AI accuracyProposed in July 2026; not final5
EU harmonised standardsBeing written (CEN and CENELEC, JTC 21); once published, following them shows high-risk compliance4
Commission guidelinesStill arriving, on definitions, prohibited practices and high-risk classification4

Which framework asks what

FrameworkBinding?WhoWhat it asks forLesson
NIST AI RMF 1.0VoluntaryAnyoneGovern, Map, Measure, Manage: 19 categories, 72 subcategories2
ISO/IEC 42001Voluntary; certifiableOrganizationsAn AI management system: clauses 4 to 10, 38 Annex A controls, a Statement of Applicability3
EU AI ActLawProviders and deployers, wherever based, if the output is used in the EUDuties by risk tier: banned, high-risk, transparency, minimal; plus general-purpose model rules4
OMB M-25-21, M-25-22, M-26-04Binding on US agenciesAgencies, and their vendors through contractsInventories, AI officers, seven practices for high-impact AI, contract terms5
State AI lawsLawBy where you operateDecision laws (notice, explanation, review); frontier model laws (safety frameworks, incident reports)5
OWASP LLM Top 10 (2026)VoluntaryBuilders of LLM appsSecurity risks: prompt injection, sensitive information disclosure, excessive agency first7

Which rules touch my system?

Five questions, in order. Each "yes" adds to the list.

AskIf yesLesson
Does it decide, or help decide, about people (jobs, credit, housing, education, benefits)?EU high-risk (Annex III); Colorado, Illinois, NYC, California ADMT; civil rights and credit law4, 5
Is its output used in the EU?The EU AI Act can apply, wherever you're based4
Does it talk to people, or make content?EU Article 50: say it's AI, mark generated content4
Do you sell it to a US federal agency?M-25-22 contract terms; M-26-04 if it's a language model5
Did you build it on someone else's model?You're probably its provider, with the provider's duties10

All "no"? It's probably minimal risk: no new legal duties, but the FTC Act still covers what you claim about it, and an inventory entry still belongs to it.

The engineer's sequence

The order of work, and what you end up with at each step.

StepDoYou end up withLesson
1. InventoryScan code, check what's running, ask about bought and planned AIA list of systems with owners, uses, data and review dates6
2. ClassifyUse the five questions aboveA tier and a rules list per system4, 5
3. DataAllowlist fields, redact, fence user text, check outputsA prompt guard and a log of hashes and counts7
4. TestNoise floor, fairness pairs, red team with a canary, release gatesTests that can fail, in CI8
5. OversightDesign the review; plant known errors; watch time and volumeNumbers that show review is real9
6. VendorsMust-haves, evidence, the right questions for the kind of vendorA verdict and a list of contract clauses10
7. PolicyTools, data, banned and reviewed uses, a default; test it with requestsOne page people can follow11

Red flags

Phrases that sound like controls and often aren't.

When you hearAskLesson
"It's not high-risk: a human makes the final decision"Does it profile people? Then the exemption doesn't apply4
"The executive order cancels the state law"Has a court, Congress or the state changed it? An order alone can't5
"We inventoried the repos"And bought software, switched-on features, and plans?6
"The filter blocks injections"What's in the model's context? Anything there can come out7
"We tested it for bias"How many runs, against what noise? Could the test have failed?8
"The model refused"Is the secret in the refusal anyway?8
"Every decision is reviewed by a person"How many planted errors do reviewers catch, in how many seconds?9
"They're ISO 42001 certified, so we're covered"What does the certificate's scope cover? What are our own duties?10
"The vendor scored 100%"Does choosing them make us the provider?10
"We banned it"Where did the use go instead?11

Numbers worth knowing

NumberWhatLesson
4 and 72NIST AI RMF functions, and subcategories2
12Risks in NIST's Generative AI Profile2
38ISO/IEC 42001 Annex A controls3
8Annex III high-risk areas in the EU AI Act4
€35M or 7%Top EU AI Act fine, for prohibited practices (€15M or 3% for most other duties)4
6 monthsMinimum log retention for EU high-risk deployers4
7Minimum practices for high-impact AI in M-25-215
0.8The four-fifths rule: an impact ratio below it suggests adverse impact8
72 hoursA common incident-notification term in AI contracts10