Skip to content
Hugin
Public record case file

Federal AI Safety Governance Accountability file

Official records, court dockets, oversight reports, release reviews, and civil or state updates joined without converting association or incomplete records into misconduct claims.

60 source leads15 verified anchors13 timeline events11 public-record rolesFile fingerprint 2b432c5a957e
Connection map
timeline backed13
source links14
role links22
open queues2

Fingerprint = the first 12 characters of this file's SHA-256 content hash, used by mirrors to verify the same JSON bundle.

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.

Connection map

How the public record is joined

Graph JSON
timeline backed13
source links14
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)
2 sourceslegislative record2 linked recordsSenate hearing: Oversight of A.I. Rules for Artificial Intelligence / S. 3312 Artificial Intelligence Research, Innovation, and Accountability Act of 2024
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.

source leads60
automated probes90
verified anchors15
review backlog30
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.

Evidence standard

Publishing limits

Jul 18, 2026, 5:00 PM
Minimum source tierofficial-record, oversight-report, audit-report, legislative-record, civil-enforcement-record
Living peopleFor named officials, witnesses, or companies, publish only source-backed public roles and exact record relationships; do not infer intent, influence, or blame.
Victim protectionDo not publish private, nonpublic, or personal data; enforcement targets are alleged unless a record shows an adjudicated outcome.
Social leadsSocial posts and coverage can start a governance or enforcement lead, but published copy requires official executive, standards, oversight, legislative, court, or enforcement records.
Association firewall

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.

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 anchors15
lead quarantine0
scout targets16
first-pass scout14
credential queue2
scout connectors16
rankwatch76 priority score
readyReady for first-pass public review13 publishable claim rows / 15 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 3205b70f81e5
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 sources15
publishable anchors13
atlas sources27
keyless feeds23
release asks7
document jobs15
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 9d6a517c74e8Case hash 2b432c5a957e
Jul 29, 2025source added

GAO generative AI use and management report (GAO-25-107653)

Status
source anchor in case file
Evidence state
case anchor
Lane
oversight report

Use for oversight context about agency use and inventory management, not proof that a named system is deployed or compliant.

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