Skip to content
Hugin
A single empty chair at the end of a long polished hearing table, lit from above in a dark room.
Public recordOpen fileA583F601

Public record case file · Latest recorded event Oct 2, 2026

Federal AI Safety Governance

Accountability file

A public-record case file for U.S. federal AI-safety governance and oversight: executive orders on AI, the NIST AI Risk Management Framework, the standards body launched as the U.S. AI Safety Institute and reconstituted as the Center for AI Standards and Innovation, FTC enforcement on AI claims, GAO oversight of federal AI use, and congressional AI hearings and legislation. It keeps executive-order status, standards guidance, enforcement actions, oversight reports, and legislative records separate until a public record supports the exact claim, and it does not rate AI model quality, capability, or safety.

Original editorial artwork generated for Hugin.

Latest recorded event
Oct 2, 2026
Source Anchors
30 verified
Timeline
24 events
Roles
13 public-record
Fingerprint
A583 F601 EBF3
Saved reading0In this browser

Keep roles, events, and source records here to pick up later. Your list stays in this browser and can be lost if you clear site data. Copy your saved links to keep a backup in your notes.

Your reading list is empty. Use a save button on an event, source, or role dossier to add it here.

Start reading

24 events · 13 roles · 30 sources

Recent developments in the record

The latest dated events in this file. Open an event for its cited sources and evidence limits.

  1. On the day EO 14434 prints, GSA's America.gov already writes 'SI', including in its link text for four outside articles whose web addresses read 'ai' →records release review · 4 source records
    Read summary and limits

    Read October 2, the GSA-run America.gov uses EO 14434's new term on its own pages. Its terms of use, under a dateline three weeks before the order, carry a section headed 'Answers generated with SI'. Its About page lists four press articles under link text reading 'SI-powered', 'SI Tool', 'SI-powered hub' and 'SI Push', while the four links' own web addresses read 'ai-powered', 'ai-tool', 'ai-powered-hub' and 'ai-push'; this desk did not open the articles and does not establish what their headlines say. Executive Order 14432, the America.gov order dated the same day as EO 14434, uses the term once, as lower-case 'super intelligence', without defining it or citing EO 14434, whose own definition is stated to apply 'For purposes of this order'. These are readings of one agency site and one order: they show the term in use, not which of EO 14434's two readings — Section 1's 'will not acknowledge' policy or Section 2's substitution in non-statutory documents — agencies follow in general.

    Evidence limits. Readings of a live agency site and two printed orders. The terms page's dateline against its use of 'SI' is recorded as an open inconsistency, and nothing here shows that GSA altered anyone's headline — only what its page displays and where its links point.

  2. Executive Order 14434 prints in the Federal Register at 91 FR 63129, word for word as filed for public inspection →records release · 2 source records
    Read summary and limits

    The Federal Register published Executive Order 14434, 'Inaugurating the Era of Super Intelligence', on October 2 at 91 FR 63129-63130, the date its public-inspection copy had scheduled. Compared word by word with that copy, the printed text is the same 687 words in the same order, by this desk's count, which ignores line breaks, page furniture, hyphenation and quotation-mark style; the Federal Register's API record lists no corrections. The terminology directive, the definition by cross-reference to 15 U.S.C. 9401(3) and the 60-day deadline for proposed legislative language, which runs from the order's September 29 date and which this desk counts to November 28, stand as filed.

    Evidence limits. Publication of an order already on this file. The word comparison is this desk's, and printing changes nothing about what the order requires or establishes.

  3. Executive Order 14434 tells agencies to write 'Super Intelligence' instead of 'AI' and orders a 60-day proposal for a new federal definition →records release · 2 source records
    Read summary and limits

    Executive Order 14434, 'Inaugurating the Era of Super Intelligence', dated at the White House September 29, went on Federal Register public inspection and is scheduled to print the next day. Section 2 directs agencies, to the maximum extent permitted by law, to use 'Super Intelligence' and 'SI' in place of 'Artificial Intelligence' and 'AI' in official correspondence, public communications, websites, reports, policy documents and other non-statutory documents, and exempts previously issued regulations, Presidential actions, contracts, grants and historical documents; the broader policy in Section 1 says the executive branch will not acknowledge the old terms' usage in any applicable setting. Section 3 defines the new terms by cross-reference, as the technologies already defined as artificial intelligence at 15 U.S.C. 9401(3), until superseded by later Presidential action or an Act of Congress. Read against that statute, enacted as section 5002 of division E of Public Law 116-283, the definition is structural and carries no capability threshold: a machine-based system that, for a given set of human-defined objectives, makes predictions, recommendations or decisions influencing real or virtual environments. The order gives the Assistant to the President for Science and Technology 60 days to send the President proposed legislative language for a federal definition reflecting the capabilities its Section 1 describes, with an assessment of whether it should modify, expand upon or supersede the statutory one. It sets no safety, standards, evaluation or procurement requirement, says it is subject to the availability of appropriations, and creates no enforceable right.

    Evidence limits. A terminology directive and a request for draft legislation. It makes no finding about any AI system, company, agency or official, and an executive order cannot change the statutory definition it cites.

Read the full timeline →
Read the case scope: what is included and excluded

Included in this file

  • Executive-order and White House AI-governance records tracked by their current in-force or revoked status (EO 14110, EO 14148, EO 14179, America's AI Action Plan, and EO 14409).
  • NIST AI Risk Management Framework records and the Center for AI Standards and Innovation, formerly the U.S. AI Safety Institute, as federal AI standards and evaluation context.
  • Federal Trade Commission civil enforcement records involving alleged deceptive or unfair AI claims and their later dispositions.
  • Government Accountability Office oversight and audit reports on federal AI governance, implementation, and use.
  • Congressional AI oversight records: hearings and AI-governance legislation with sponsor, committee, and status detail.

Outside this file’s scope

  • Tracking AI model releases, vendor benchmark claims, or model capability announcements, and rating or ranking AI model quality, safety, or performance, which are covered by the AI release-receipts case.
  • Tracking federal AI procurement such as contract awards, OMB and FAR acquisition rules, USAspending, or SAM.gov records, which are covered by the federal AI procurement watch case.
  • Treating a policy, framework, hearing, or enforcement filing as proof that a specific AI system is safe, unsafe, compliant, or noncompliant.

What remains unresolved

These questions stay open in the case file.

  • Which specific EO 14110 provisions were rescinded versus continued by agency action after the EO 14179 review, and is there an agency-by-agency Federal Register trail?
  • CAISI's September 17, 2026 GLM-5.3 assessment documents the method behind its cyber benchmark comparisons (a ReAct agent harness, maximum reasoning settings, a one-parameter IRT capability index); what is its published methodology for other evaluation areas, and which developer agreements are active as of mid-2026?
Read all 12 open questions →
Connection map

How the public record connects

Graph JSON

This view starts with the roles that have the most source-record links in this file. Explore Role Web and Timeline for the full set. A line represents a shared source record; it does not establish conduct or a direct relationship.

Publishing limits

These are the standards every anchor on this file must clear.

Minimum source tier
  • official record
  • oversight report
  • audit report
  • legislative record
  • civil enforcement record
Living people
For named officials, witnesses, or companies, publish only source-backed public roles and exact record relationships; do not infer intent, influence, or blame.
Victim protection
Do not publish private, nonpublic, or personal data; enforcement targets are alleged unless a record shows an adjudicated outcome.
Social leads
Social posts and coverage can start a governance or enforcement lead, but published copy requires official executive, standards, oversight, legislative, court, or enforcement records.

No guilt by proximity

A model, vendor, agency, or official appearing in the same governance lane is context only and does not prove a violation, a safety outcome, or responsibility for a policy.

Filed
Hugin · public social evidence reports
License
Text and data are shared under the terms noted at hugin.studio/support · attribution appreciated.
Fingerprint
A583 F601 EBF3
For researchers & contributorsSource desk, research joins & machine-readable exportsEverything Hugin uses to grow and audit this file — connection detail, review posture, scout queue, and every export.
Connection map

How the public record is joined

Graph JSON
timeline backed24
source links32
role links31
open queues2
Source groups
17 sourcesofficial record17 linked recordsNIST AI Risk Management Framework (AI RMF 1.0) / NIST AI RMF Generative AI Profile (NIST AI 600-1) / Center for AI Standards and Innovation (CAISI)
4 sourcescivil enforcement record4 linked recordsFTC Operation AI Comply enforcement sweep / Rytr LLC; Analysis of Proposed Consent Order To Aid Public Comment (89 FR 80565) / FTC reopens and sets aside the Rytr final order
Timeline joins
Jan 1, 2021 / officialCongress enacts the federal definition of 'artificial intelligence' at 15 U.S.C. 9401(3), with no capability threshold in it1 linked recordA statutory definition read in the 2024 Code edition, which this page states is current through January 6, 2025; it is not a finding about any system and this desk confirmed no later amendment independently.
Jan 26, 2023 / officialNIST releases the AI Risk Management Framework1 linked recordA voluntary framework does not establish whether any agency or vendor met it.
Role joins
official record holderNational Institute of Standards and Technology4 linked recordsNIST guidance is voluntary and non-regulatory; publishing a framework is not the same as mandating or certifying compliance.
official record holderCenter for AI Standards and Innovation2 linked recordsReconstituted from the U.S. AI Safety Institute in June 2025 with a reframed mission; continuity of specific programs across the rename should be verified per program.

Connections are navigation aids. They show where a record, event, or role is sourced; they do not convert association, correspondence, testimony requests, or document appearance into misconduct findings.

verified anchors30
timeline events24
research queues7
No hand-tuned source desk on this case yet, so no lead or probe queue is counted for it.
scout targets16
first-pass scout14
credential queue2
connectors16
keyless APIs6
free-key targets2
public search8
official pages0
POST templates0
CourtListener Search API / keyless apiGDELT DOC API / keyless apiFederal Register API / keyless apiGovInfo public document search / public searchRegulations.gov public search / public searcheCFR public search / public searchDOJ News API / keyless apiFOIA.gov government website search / public searchFBI Vault search / public searchNational Archives Catalog API / free key requiredData.gov CKAN catalog API / free key requiredCongress.gov public search / public search

Default public-record source desk for cases without a hand-tuned scout profile.

Source lanespublic-record-discovery
Sharing stateautomatic sharing disabled
Next actionAdd source receipts to the review queue before promoting case claims or social copy.
keyless apiCourtListener Search APIpublic-record source deltasLegal search across opinions, dockets, RECAP data, judges, and arguments.
keyless apiGDELT DOC APIpublic-record source deltasCoverage-index discovery for fresh public reporting rows.
keyless apiFederal Register APIpublic-record source deltasOfficial rule, notice, and agency-document discovery.
public searchGovInfo public document searchpublic-record source deltasFree public search across official publications from all three branches of the U.S. federal government.
public-record source deltas

Source leads and automated probes are review inventory. They become verified anchors only after Hugin can attach the public record, legal posture, and no-allegation guardrails.

Join board

Public-record joins are wired into exports

These are not loose TODOs anymore. Each lane below is computed from the case file's source tiers, then joined to matching sources, timeline events, role nodes, and release-roadmap requests.

wired lanes5
review lanes2
source joins49
release joins0
Wired lanes5Computed from the source tiers and joined to live records, roles, and releases.
WiredExecutive-order and AI Action Plan status monitor
18 sources

Track new or amended AI executive orders and AI Action Plan implementation through GovInfo and White House records before saying federal AI policy changed.

timeline15
roles6
release asks0
Connected roles
National Institute of Standards and TechnologyCenter for AI Standards and InnovationThe White House and Executive Office of the President
Release requests
No release request is attached to this lane yet.
PublishesDated in-force or revoked status of each order with GovInfo or Federal Register citations.
BlockedPredicting future policy or characterizing an administration's intent.
WiredCAISI evaluation and agreement tracking
17 sources

Monitor NIST and CAISI records for evaluation reports, developer agreements, and standards initiatives.

timeline15
roles6
release asks0
Connected roles
National Institute of Standards and TechnologyCenter for AI Standards and InnovationThe White House and Executive Office of the President
Release requests
No release request is attached to this lane yet.
PublishesNamed, dated CAISI actions with NIST citations.
BlockedRating model quality or safety, or implying a pass or fail verdict from the existence of an evaluation.
WiredFTC AI enforcement lifecycle
5 sources

Track FTC AI matters end to end using Federal Register consent notices and regulations.gov dockets, recording both openings and later set-asides.

timeline3
roles3
release asks0
Connected roles
National Institute of Standards and TechnologyFederal Trade CommissionGovInfo (U.S. Government Publishing Office)
Release requests
No release request is attached to this lane yet.
PublishesDocket-numbered actions, parties, dates, and current status framed as allegations or orders.
BlockedStating a company is guilty, or omitting a later reversal such as the Rytr set-aside.
WiredGAO AI oversight and recommendation tracking
4 sources

Monitor GAO's AI topic for new reports and open or closed recommendation status.

timeline3
roles2
release asks0
Connected roles
Government Accountability OfficeTreasury Inspector General for Tax Administration
Release requests
No release request is attached to this lane yet.
PublishesReport-numbered findings and recommendation status with GAO citations.
BlockedTracking procurement spending or contract awards, which belong to the federal AI procurement case.
WiredFederal AI-governance legislation and hearings
3 sources

Monitor congress.gov and GovInfo for AI-governance bills and oversight hearings across the 118th and 119th Congresses.

timeline3
roles4
release asks0
Connected roles
Senate Judiciary Subcommittee on Privacy, Technology, and the LawSenate Judiciary Subcommittee on Crime and CounterterrorismSenate Committee on Commerce, Science, and Transportation
Release requests
No release request is attached to this lane yet.
PublishesBill numbers, sponsors, committee action, enacted status, and hearing records.
BlockedPredicting passage or inferring a lawmaker's motive.
Needs review2Sources have landed but the lane is not promoted to wired yet.
Needs reviewFederal Register and GovInfo AI-document index
1 source

Build a citation-anchored index of AI executive orders, agency notices, and requests for information through GovInfo, since federalregister.gov blocks automated fetch.

timeline0
roles2
release asks0
Connected roles
National Institute of Standards and TechnologyGovInfo (U.S. Government Publishing Office)
Release requests
No release request is attached to this lane yet.
PublishesA document list with Federal Register or GovInfo citations and dates.
BlockedSummaries not traceable to a fetched primary record.
Needs reviewInternational index cross-check (OECD.AI)
1 source

Reconcile OECD.AI United States entries against U.S. primary records, including the observed EO 14179 signing-date discrepancy.

timeline0
roles1
release asks0
Connected roles
OECD.AI Policy Observatory
Release requests
No release request is attached to this lane yet.
PublishesFlagged discrepancies with the governing primary citation.
BlockedTreating the index as a primary source.
Public utility

Help grow the source queue

Hugin accepts public records, not accusations. A submitted URL lands in a review lane, gets source-validated, and only becomes a case anchor after the evidence rules and privacy gates are satisfied.

Review posture

What this case can prove right now

Fact-check desk
publishable claims24
source repair0
known anchors30
lead quarantine0
scout targets16
first-pass scout14
credential queue2
scout connectors16
rankmedium124 priority score
readyReady for first-pass public review24 publishable claim rows / 30 source anchors / 14 first-pass source rows
actions6 start-here rows9 total workbench action rows
blockers1 launch checks2 source-scout rows require free operator keys

Fact-check status is a review posture, not a verdict. Source-scout rows are leads until a reviewer joins them to publishable anchors; claim-ledger rows are timeline-derived and still require source validation plus no-allegation guardrails before promotion.

Source intake

Queue a public record

Public queue

Paste an official or public-record URL. Hugin classifies the lane first, keeps lead-only material quarantined, and requires source validation before anything reaches the case file.

Use an official or public-record page. Local, private, leaked, or credentialed URLs are rejected.
Queue a public source for review.
Visible queue

Latest submitted public URLs

Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.

Public queue loaded.Live queue connectedQueue hash c4f3c8718a38
No public submissions in this snapshot.When someone submits a source, this board will show the URL, lane, status, hold reason, and next review step before anything can become part of the case file.
known sources30
publishable anchors28
atlas sources27
keyless feeds23
release asks7
document jobs30
privacy triage5
lead quarantine0
01Submit URLPublic URL, label, and context enter the source queue.
02Classify laneOfficial, court, legislative, civil, state, repository, or lead quarantine.
03Validate sourcePublisher, date, scope, privacy, and duplicate checks run before promotion.
04Promote anchorOnly source-backed, privacy-cleared records can join timeline or role surfaces.
Contribution guide

Submit sources, not claims

A source is a public URL someone else can inspect. A claim is an interpretation. Hugin queues sources first and keeps claims out until a reviewed public record supports the exact wording.

Accepted

Official agency pages, court dockets, congressional releases, civil records, state updates, and public repositories with source URLs.

Publisher, date, record family, and why the URL belongs in this file.

Source URLs first. Context is welcome, but claims do not publish from submissions alone.

Not accepted

Private tips, survivor identifiers, sealed or leaked material, graphic details, and private contact data.

Screenshots or social posts without a public source URL.

Misconduct labels for living people unless the exact cited public record supports that exact statement.

What changed

Case change ledger

Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.

Change ledger loaded.Ledger hash a9014a0ff2aeCase hash a583f601ebf3
Safety posture

Locked to public records and bounded intake

Post throttleSource intake is DB-rate-limited to 6 submissions per minute per network key before a record is written.
Public URL onlyLocalhost, private networks, URL credentials, unsupported protocols, malformed URLs, and overlong fields are rejected.
No paid callsThe data export links render deterministic public-record payloads. They do not call LLMs or paid upstream APIs.
Identity minimizedSubmitter material is converted to a server-side HMAC hash, and the public queue does not return raw IPs or user agents.