Skip to content
Hugin
Public Record Case File · Updated Dec 22, 2025

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.

Public RecordOpen File29F03F64
Updated
Dec 22, 2025
Source Anchors
17 verified
Timeline
13 events
Roles
11 public-record
Fingerprint
29F0 3F64 7C35
Connection map

How the public record connects

Graph JSON

This shows the case file's most significant public-record connections only — see the Role Web and Timeline tabs for the full set. A line means a record connects two points; it is not a finding about conduct.

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
29F0 3F64 7C35
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 backed13
source links15
role links22
open queues2
Source groups
7 sourcesofficial record7 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)
3 sourcescivil enforcement record3 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 26, 2023 / officialNIST releases the AI Risk Management Framework1 linked recordA voluntary framework does not establish whether any agency or vendor met it.
May 16, 2023 / officialSenate holds Oversight of A.I. hearing1 linked recordHearing testimony reflects witnesses' views and is not a government finding.
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 Innovation1 linked recordReconstituted 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 anchors17
timeline events13
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 joins26
release joins0
Wired lanes5Computed from the source tiers and joined to live records, roles, and releases.
WiredExecutive-order and AI Action Plan status monitor
8 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.

timeline7
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
7 sources

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

timeline7
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
4 sources

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

timeline2
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
3 sources

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

timeline2
roles1
release asks0
Connected roles
Government Accountability Office
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
2 sources

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

timeline2
roles3
release asks0
Connected roles
Senate Judiciary Subcommittee on Privacy, Technology, and the LawSenate Committee on Commerce, Science, and TransportationGovInfo (U.S. Government Publishing Office)
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 claims13
source repair0
known anchors17
lead quarantine0
scout targets16
first-pass scout14
credential queue2
scout connectors16
rankwatch78 priority score
readyReady for first-pass public review13 publishable claim rows / 17 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 9c1ee6091c6d
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 sources17
publishable anchors15
atlas sources27
keyless feeds23
release asks7
document jobs17
privacy triage4
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 012de4e22c5bCase hash 29f03f647c35
Dec 22, 2025source added

FTC reopens and sets aside the Rytr final order

Status
source anchor in case file
Evidence state
case anchor
Lane
civil enforcement record

An agency reversing its own administrative order is a disposition change, not a finding that the original allegations were false or that the conduct occurred. Retrieved directly 2026-08-05; an earlier note in this file described the FTC newsroom as CDN-blocked to automated fetch, which is no longer accurate for this page.

Next: Keep source-linked timeline and role claims limited to the extracted facts.4821811f54c6
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.