Thursday, October 8, 2026 · Week 41 Reading for Oct. 8 · Last entry Oct. 6
Paperclip Index

Weekly reading · methodology v0.6

Window ending July 28, 2025

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 June 29, 2025 through July 28, 2025. 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

9

Negligible harm · Worst documented harm counting: negligible. 2 records 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 qualifying harm records.

Documented harm
2
No harm found (stated scope)
0
No harm reported
0
Impact unknown
1
Alleged, AI role uncorroborated
0
Counts toward the index
2
Unverified, watching
1
Alleged in court
0
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

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.

  1. PI-0015
  2. PI-0016
  3. PI-0017

Sources

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

  1. xAI (@grok on X): Grok account statement: xAI is removing the inappropriate posts and banning hate speech before Grok postsCited in PI-0015
  2. xAI (@grok on X): Grok account apology for the horrific behavior, blaming a code-path updateCited in PI-0015
  3. Polskie Radio: Musk pulls hateful X posts after AI chatbot lauds Hitler, curses Polish PMCited in PI-0015
  4. The Forward: Calling itself 'MechaHitler,' Elon Musk's AI tool spreads antisemitic conspiraciesCited in PI-0015
  5. AP (via Spectrum News 13): Elon Musk's AI chatbot Grok gets an update and starts sharing antisemitic postsCited in PI-0015
  6. NBC News (via NBC Bay Area): AI chatbot Grok issues apology for antisemitic postsCited in PI-0015
  7. Jason Lemkin (X): Replit goes rogue during a code freeze and shutdown and deletes our entire databaseCited in PI-0016
  8. Amjad Masad, Replit CEO (X): Replit CEO on the agent deleting production data: unacceptable and should never be possibleCited in PI-0016
  9. Replit: Introducing a safer way to Vibe Code with Replit DatabasesCited in PI-0016
  10. Jason Lemkin (X): So net net: it could have been a lot worse… I lost 100 hours of timeCited in PI-0016
  11. The Register: Vibe coding service Replit deleted user's production database, faked data, told fibs galoreCited in PI-0016
  12. The Register: Replit makes vibe-y promise to stop its AI agents making vibe coding disastersCited in PI-0016
  13. Tom's Hardware: AI coding platform goes rogue during code freeze and deletes entire company databaseCited in PI-0016
  14. eWeek: 'Catastrophic Failure': AI Agent Wipes Production Database, Then Lies About ItCited in PI-0016
  15. Jason Lemkin (SaaStr): Replit's New Release Addressed Most of The Challenges We Hit Vibe Coding…Cited in PI-0016
  16. GitHub: Gemini CLI 'lost' files during a failed file move operation. [Windows] (issue #4586)Cited in PI-0017
  17. GitHub (issue reporter): Reporter's correction: files found in the C: drive root (issue #4586 comment)Cited in PI-0017
  18. GitHub (issue reporter): Gemini CLI PowerShell session log attached to issue #4586Cited in PI-0017
  19. Slashdot: Google's Gemini CLI deletes user's files (Slashdot; repeats the pre-correction account)Cited in PI-0017
  20. AI Incident Database: AI Incident Database, incident 1178Cited in PI-0017

All weekly readings · How this reading is calculated · Download the weekly card