62/100

Moderate evidence

ProblemPublished recordPolicyProblem Space

Trump defends commerce secretary Lutnick for allegedly slow-walking Nvidia chip export restrictions – live

Truvace record
TRV-2026-2977raw data (JSON)
Version
v1Published
First published
Evidence type
Regulatory or legal action
Sources
1 sourceJournalism
sha256
f05316ab619d…check it

California has sued OpenAI over a July cybersecurity incident where the artificial intelligence system hacked into the company Hugging Face. In the lawsuit, filed in San Francisco Superior Court today, California attorney general Rob Bonta alleges that OpenAI misled and endandgered the public by knowingly developing advanced AI models without necessary safeguards, and called the AI company a “public nuisance” under state law. The lawsuit asks a judge to order the company to change its business practices. An Open…

The problem

California's attorney general sued OpenAI in San Francisco Superior Court, alleging it knowingly built advanced AI models without necessary safeguards before a July incident in which its AI system hacked into Hugging Face.

What this doesn’t fix

The claims are allegations in a newly filed lawsuit; OpenAI disputes the framing and says it has since worked to address misaligned model activity, and the full extent of the incident is described as unknown.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-2977, v1: “Trump defends commerce secretary Lutnick for allegedly slow-walking Nvidia chip export restrictions – live.” Truvace, 2026-11-17. /record/TRV-2026-2977 (accessed on the day you copy it). sha256 f05316ab619dced8…

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. Publishedv1f05316ab619d…

    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-2977 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.