Weekly reading · methodology v0.6
Window ending July 21, 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 22, 2025 through July 21, 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.
This is a backcast from the current catalogue. It was not a reading published at the time.
Records behind this reading
4 selected records; 2 documented external harms counting (2 qualifying). Records and ratings below reflect the current catalogue.
2 qualifying harm records.
- Documented harm
- 3
- 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
- 1
- Tracked separately
- 0
Documented exclusions: 1 internal; 0 awaiting evidence review. 1 qualifying record with a bounded single-source review.
Inspect the evidence · 4 records
- PI-0013 · Office shop run by an AI agent lost money and the agent claimed to be a personDocumented harm · internal harm, excluded · extent undisclosed
- PI-0015 · xAI's Grok posted antisemitic content and praise of Hitler on X after a system-prompt changeImpact unknown · excluded from the harm reading
- PI-0016 · Coding agent deleted a production database during a code freeze, then misreported recovery optionsDocumented harm · qualifying harm
- PI-0017 · Command-line coding agent misplaced a user's files after a failed command, then wrongly said they were destroyedDocumented harm · qualifying harm · bounded single-source review
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-0013Office shop run by an AI agent lost money and the agent claimed to be a personJune 27, 2025 · Negligible harm · Internal research
- PI-0015xAI's Grok posted antisemitic content and praise of Hitler on X after a system-prompt changeJuly 8, 2025 · Impact unknown · Deployment
- PI-0016Coding agent deleted a production database during a code freeze, then misreported recovery optionsJuly 18, 2025 · Negligible harm · Deployment
- PI-0017Command-line coding agent misplaced a user's files after a failed command, then wrongly said they were destroyedJuly 21, 2025 · Negligible harm · Deployment
Sources
These links support the records above. Source availability and conclusions may change.
- Anthropic: Project Vend: Can Claude run a small shop?Cited in PI-0013
- Anthropic: Project Vend: Phase twoCited in PI-0013
- The Decoder: Anthropic's Claude ran a store and lost money by selling below cost and giving discountsCited in PI-0013
- Pure AI: When AI Goes Rogue in Retail: The Strange Case of Claude's Business BreakdownCited in PI-0013
- Simon Willison's Weblog: Project VendCited in PI-0013
- xAI (@grok on X): Grok account statement: xAI is removing the inappropriate posts and banning hate speech before Grok postsCited in PI-0015
- xAI (@grok on X): Grok account apology for the horrific behavior, blaming a code-path updateCited in PI-0015
- Polskie Radio: Musk pulls hateful X posts after AI chatbot lauds Hitler, curses Polish PMCited in PI-0015
- The Forward: Calling itself 'MechaHitler,' Elon Musk's AI tool spreads antisemitic conspiraciesCited in PI-0015
- AP (via Spectrum News 13): Elon Musk's AI chatbot Grok gets an update and starts sharing antisemitic postsCited in PI-0015
- NBC News (via NBC Bay Area): AI chatbot Grok issues apology for antisemitic postsCited in PI-0015
- Jason Lemkin (X): Replit goes rogue during a code freeze and shutdown and deletes our entire databaseCited in PI-0016
- Amjad Masad, Replit CEO (X): Replit CEO on the agent deleting production data: unacceptable and should never be possibleCited in PI-0016
- Replit: Introducing a safer way to Vibe Code with Replit DatabasesCited in PI-0016
- Jason Lemkin (X): So net net: it could have been a lot worse… I lost 100 hours of timeCited in PI-0016
- The Register: Vibe coding service Replit deleted user's production database, faked data, told fibs galoreCited in PI-0016
- The Register: Replit makes vibe-y promise to stop its AI agents making vibe coding disastersCited in PI-0016
- Tom's Hardware: AI coding platform goes rogue during code freeze and deletes entire company databaseCited in PI-0016
- eWeek: 'Catastrophic Failure': AI Agent Wipes Production Database, Then Lies About ItCited in PI-0016
- Jason Lemkin (SaaStr): Replit's New Release Addressed Most of The Challenges We Hit Vibe Coding…Cited in PI-0016
- GitHub: Gemini CLI 'lost' files during a failed file move operation. [Windows] (issue #4586)Cited in PI-0017
- GitHub (issue reporter): Reporter's correction: files found in the C: drive root (issue #4586 comment)Cited in PI-0017
- GitHub (issue reporter): Gemini CLI PowerShell session log attached to issue #4586Cited in PI-0017
- Slashdot: Google's Gemini CLI deletes user's files (Slashdot; repeats the pre-correction account)Cited in PI-0017
- AI Incident Database: AI Incident Database, incident 1178Cited in PI-0017
All weekly readings · How this reading is calculated · Download the weekly card
