42/100

Emerging evidence

GainPublished recordLaborGood Space

US public workers are fighting to protect their jobs from AI – and some are winning

Truvace record
TRV-2026-2884raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
08fb7f374340…check it

In the shadow of Silicon Valley, workers for the city of Oakland, California, worry the region will deploy AI systems that could increase surveillance and inaccurately evaluate their performance. Pushing for protections to ensure workers won’t be laid off or disciplined by AI, their union overwhelmingly voted on 22 October to authorize a strike, with 94.1% in favor. “We just want the city administration to really be intentional about how it’s engaging with AI products,” said Julian Ware, an Oakland spatial data…

The gain

After 94.1% of Oakland city union members voted to authorize a strike on 22 October, the city agreed to a tentative three-year deal requiring it to retrain or reassign workers displaced by AI rather than fire them.

What this doesn’t fix

The Oakland agreement is only tentative, and Pennsylvania's union expects the AI issues to resurface in 2027 contract negotiations.

Sources

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

Cite this record

v1

Truvace Impact Record TRV-2026-2884, v1: “US public workers are fighting to protect their jobs from AI – and some are winning.” Truvace, 2026-11-13. /record/TRV-2026-2884 (accessed on the day you copy it). sha256 08fb7f374340105e…

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

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