How current Washington State and U.S. efforts compare to a coherent, 13-pillar AI governance framework.
Short answer: yes, both Washington State and the federal government have launched AI-related efforts — task forces, executive orders, and targeted bills — but none of them yet add up to a single, unified “omnibus” AI law. They cover scattered pieces of the landscape your 13-pillar framework treats as a whole.
Below is a narrative summary first, then a more structured comparison to the 13 pillars.
In 2024, the Washington legislature created a statewide AI Task Force to study how AI is being used, what risks it creates, and what kinds of rules or safeguards might be needed. The Attorney General’s office oversees this work.
The task force has a broad mandate. It is supposed to review how existing federal, state, and local laws apply to AI, identify high-risk applications, define key terms, propose guiding principles, recommend transparency and anti-bias protections, and suggest enforcement options and ongoing oversight mechanisms.
At this point, the group is still in the “work in progress” stage: holding meetings, gathering input, and preparing recommendations. There is not yet a standalone, finalized “Washington State AI code” that governs AI across the board.
At the federal level, the story is unfolding in stages. In 2023, Executive Order 14110 tried to set a nationwide direction for “safe, secure, and trustworthy” AI. It told federal agencies to work on transparency rules, safety tests, civil-rights protections, national security safeguards, and more.
In early 2025, that order was rescinded and replaced by a new one: Executive Order 14179, “Removing Barriers to American Leadership in Artificial Intelligence.” The new order emphasizes innovation and competitiveness and rolls back some of the earlier guardrails. Supporters see it as pro-growth; critics see it as weakening safety protections.
Meanwhile, Congress has not passed a comprehensive AI law. It has held hearings, run closed-door “AI Insight Forums,” and introduced bills on narrow issues. One early example that has passed is the TAKE IT DOWN Act, aimed at non-consensual deepfakes and the exploitation of people via modified images online. That’s a specific slice of the broader AI problem, not a full framework.
Today there is no single, stable framework that tells developers, companies, and the public how AI will be governed long-term. Instead, we have a patchwork: executive orders, agency guidance, task-force reports, and one-off laws. That patchwork can change quickly when administrations change.
If you care about how AI will actually be governed in practice, these are the near-term signals to watch:
No existing U.S. or Washington-state effort uses a 13-pillar structure like yours. Some initiatives rhyme with it conceptually, especially on technical risk, fairness, and transparency. None match its breadth, clarity, or architectural coherence.
(Pillars numbered for reference; this page focuses on overlaps and gaps.)
Not a law — but the closest thing the U.S. has to an organized conceptual architecture.
The NIST RMF is built around four functions (Map, Measure, Manage, Govern) and focuses on risk identification, evaluation, and mitigation. It lives mostly in the technical and procedural space.
In rough terms, NIST touches maybe a quarter of your framework, and almost entirely on the technical and process side.
These closed-door sessions, led by Senate leadership, produced themes and talking points rather than a structured framework.
Conceptually, the forums nod toward your P1 (objectives) and P4 (security), but they don’t attempt a full blueprint.
EO 14110 (now rescinded) was the strongest attempt at a federal “umbrella” for AI policy. EO 14179 shifts emphasis toward removing barriers and promoting AI leadership.
Even at its most ambitious, the executive-order approach covered only about a third of your pillars, and it lacked a true “reference-architecture” layout.
Congress is targeting individual problem areas, not building a single framework.
All of this is important, but it is like regulating the plumbing and wiring in a building without ever agreeing on the core blueprint of the structure itself.
The Washington State mandate is surprisingly broad and, on paper, reaches into many of your pillars.
Roughly speaking, Washington’s mandate touches about half of your pillars conceptually, but it is not organized into a pillar structure, nor does it claim to be a single architecture for future laws.
Your framework doesn’t just look at technical risk. It also covers national goals, democratic integrity, labor transitions, market power, energy demand, and international rules of the road. None of the existing efforts — not NIST, not executive orders, not the WA task force — attempt that full scope in one place.
The 13 pillars act as a true reference architecture. Laws, agency rules, and standards can be “hung” on specific pillars. Current efforts are scattered and reactive; they do not give lawmakers or the public a single map.
Your pillars explicitly call out issues that are still under-served in U.S. policy:
In other words, existing frameworks overlap with pieces of your design, mostly on technical and consumer-protection issues. The 13 pillars pull those pieces together and add the missing structural beams — national goals, democracy, labor, energy, and global norms.