55/100

Moderate evidence

ProblemPublished recordPolicyProblem Space

Staff at the US center for AI safety are reporting to the White House, raising independence concerns

Truvace record
TRV-2026-2439raw data (JSON)
Version
v1Published
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
742e68bd72ff…check it

With public anxiety growing over mounting reports about out-of-control artificial intelligence agents, the tiny U.S. government division charged with assessing the safety of new AI offerings lacks a permanent leader and has stopped publishing its research. SAN FRANCISCO (AP) — With public anxiety growing over mounting reports about out-of-control artificial intelligence agents, the tiny U.S. government division charged with assessing the safety of new AI offerings lacks a permanent leader and has stopp

The problem

The Commerce Department's AI safety center, funded at $10 million a year, has gone without a permanent director since the summer, stopped publishing its safety reports and been asked to report informally to a White House office, which critics say weakens independent checks.

What this doesn’t fix

The reporting on the White House reporting arrangement relies on two anonymous former officials, and the White House did not respond to specific questions about CAISSI.

Sources

1 on file
  1. WIS10wistv.com
    Journalism2026-11-08

Cite this record

v1

Truvace Impact Record TRV-2026-2439, v1: “Staff at the US center for AI safety are reporting to the White House, raising independence concerns.” Truvace, 2026-11-09. /record/TRV-2026-2439 (accessed on the day you copy it). sha256 742e68bd72ff8f9b…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1742e68bd72ff…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2439 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.