Sunday, October 11, 2026
Paperclip Index

Weekly reading · methodology v1.0

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. 10, 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.

Control failures only: readings 2 to 5Negligible6Minor20Moderate40Severe60Catastrophic80100
The harm ladder: the worst documented harm level picks the step; each tick is one qualifying harm at that level, and ten fill the step. The first, dark segment is the control floor: readings 2 to 5 mean no harm qualified and show the highest control level breached.

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 harms counting that week: 1 minor, 1 negligible. 3 records reported in the last 30 days.

Records behind this reading · 2

Only these records move the reading. How it is calculated

  1. PI-0048
  2. PI-0050
    Coding agent ran an infrastructure teardown that deleted a course platform's database and snapshotsMarch 6, 2026 · Minor harm · counting as negligible, rated minor · Deployment
  3. PI-0051

Sources

These links support the records above. Source availability and conclusions may change.

  1. Google: Our statement on the Gavalas lawsuitCited in PI-0048
  2. Edelson PC: AI Lawsuits: The Cases Edelson Has Filed and Why They MatterCited in PI-0048
  3. CourtListener: Gavalas v. Google LLC, 5:26-cv-01849 (N.D. Cal.), docketCited in PI-0048
  4. U.S. District Court, N.D. California (via CourtListener RECAP): Gavalas v. Google LLC: complaintCited in PI-0048
  5. U.S. District Court, N.D. California (via CourtListener RECAP): Gavalas v. Google LLC: Google's motion to dismissCited in PI-0048
  6. PacerMonitor: Gavalas v. Google LLC et al: docketCited in PI-0048
  7. Semafor: A new lawsuit claims Gemini assisted in suicideCited in PI-0048
  8. ABC7 (Associated Press): Lawsuit alleges Google's Gemini guided man to consider 'mass casualty' event before suicideCited in PI-0048
  9. Alexey Grigorev / AI Shipping Labs: How I Dropped Our Production Database and Now Pay 10% More for AWSCited in PI-0050
  10. 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
  11. Storyboard18: 'The agent kept deleting files': Developer says Anthropic's Claude Code wiped 2.5 years of dataCited in PI-0050
  12. Rootly: "Hey Claude, where's my database?": How an AI agent nuked productionCited in PI-0050
  13. The Information: Inside Meta, a Rogue AI Agent Triggers Security AlertCited in PI-0051
  14. The Decoder: A rogue AI agent caused a serious security incident at MetaCited in PI-0051
  15. TechCrunch: Meta is having trouble with rogue AI agentsCited in PI-0051
  16. The Verge: A rogue AI led to a serious security incident at MetaCited in PI-0051
  17. Sumsub: Rogue AI agent at Meta triggers security incidentCited in PI-0051
  18. Unite.AI: Meta AI agent triggers Sev 1 security incident after acting without authorizationCited in PI-0051
  19. AI Incident Database: AI Incident Database report 7169Cited in PI-0051

Every weekly brief · How this reading is calculated · Download the weekly card