Weekly reading · methodology v0.6
Window ending March 30, 2026
Harms count in full for two weeks after they are reported, then one level less every two weeks. The control floor looks at reports from March 1, 2026 through March 30, 2026. A selected catalogue of reported AI incidents, reviewed through Oct. 7, 2026. This reading describes documented harm in the records or, when none qualifies, the highest control level breached. It is not a forecast or a measure of all AI activity.
Current recalculation
20
Minor harm · Worst documented harm counting: minor. 1 record at this level.
Recalculated from the catalogue in this build. Historical backcasts were not published at the time.
Published at the time
No publication snapshot exists for this week.
This is a backcast from the current catalogue. It was not a reading published at the time.
Records behind this reading
3 selected records; 2 documented external harms counting (2 qualifying). Records and ratings below reflect the current catalogue.
2 qualifying harm records. Extent undisclosed for both.
- Documented harm
- 2
- No harm found (stated scope)
- 0
- No harm reported
- 0
- Impact unknown
- 0
- Alleged, AI role uncorroborated
- 1
- Counts toward the index
- 2
- Unverified, watching
- 0
- Alleged in court
- 1
- Control failure, tracked
- 0
- Tracked separately
- 0
Documented exclusions: 0 internal; 0 awaiting evidence review. 1 qualifying record with a bounded single-source review.
Inspect the evidence · 3 records
- PI-0048 · First wrongful-death lawsuit over Gemini alleges the chatbot coached a Florida man toward suicideAlleged, AI role uncorroborated · excluded from the harm reading
- PI-0050 · Coding agent ran an infrastructure teardown that deleted a course platform's database and snapshotsDocumented harm · qualifying harm, counting as negligible, rated minor · bounded single-source review · extent undisclosed
- PI-0051 · Internal agent posted unrequested advice that led to a two-hour internal data exposureDocumented harm · qualifying harm · extent undisclosed
Status totals cover counted records; aliases, superseded aggregates and records tracked separately are excluded. Eligibility and extent notes overlap those totals. These observations are not statistical uncertainty bounds.
- PI-0048First wrongful-death lawsuit over Gemini alleges the chatbot coached a Florida man toward suicideMarch 4, 2026 · Severe harm, alleged · Deployment
- PI-0050Coding agent ran an infrastructure teardown that deleted a course platform's database and snapshotsMarch 6, 2026 · Minor harm · counting as negligible, rated minor · Deployment
- PI-0051Internal agent posted unrequested advice that led to a two-hour internal data exposureMarch 18, 2026 · Minor harm · Deployment
Sources
These links support the records above. Source availability and conclusions may change.
- Google: Our statement on the Gavalas lawsuitCited in PI-0048
- Edelson PC: AI Lawsuits: The Cases Edelson Has Filed and Why They MatterCited in PI-0048
- CourtListener: Gavalas v. Google LLC, 5:26-cv-01849 (N.D. Cal.), docketCited in PI-0048
- U.S. District Court, N.D. California (via CourtListener RECAP): Gavalas v. Google LLC: complaintCited in PI-0048
- U.S. District Court, N.D. California (via CourtListener RECAP): Gavalas v. Google LLC: Google's motion to dismissCited in PI-0048
- PacerMonitor: Gavalas v. Google LLC et al: docketCited in PI-0048
- Semafor: A new lawsuit claims Gemini assisted in suicideCited in PI-0048
- ABC7 (Associated Press): Lawsuit alleges Google's Gemini guided man to consider 'mass casualty' event before suicideCited in PI-0048
- Alexey Grigorev / AI Shipping Labs: How I Dropped Our Production Database and Now Pay 10% More for AWSCited in PI-0050
- Tom's Hardware: Claude Code deletes developers' production setup, including its database and snapshots — 2.5 years of records were nuked in an instantCited in PI-0050
- Storyboard18: 'The agent kept deleting files': Developer says Anthropic's Claude Code wiped 2.5 years of dataCited in PI-0050
- Rootly: "Hey Claude, where's my database?": How an AI agent nuked productionCited in PI-0050
- The Information: Inside Meta, a Rogue AI Agent Triggers Security AlertCited in PI-0051
- The Decoder: A rogue AI agent caused a serious security incident at MetaCited in PI-0051
- TechCrunch: Meta is having trouble with rogue AI agentsCited in PI-0051
- The Verge: A rogue AI led to a serious security incident at MetaCited in PI-0051
- Sumsub: Rogue AI agent at Meta triggers security incidentCited in PI-0051
- Unite.AI: Meta AI agent triggers Sev 1 security incident after acting without authorizationCited in PI-0051
- AI Incident Database: AI Incident Database report 7169Cited in PI-0051
All weekly readings · How this reading is calculated · Download the weekly card
