Weekly reading · methodology v1.0
Window ending Feb. 17, 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 Jan. 19, 2025 through Feb. 17, 2025. 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
6
Negligible harm · Worst documented harm counting: negligible. 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
1 selected record; 1 documented external harm counting (1 qualifying). Records and ratings below reflect the current catalogue.
1 harm counting that week: 1 negligible. 1 record reported in the last 30 days.
Records behind this reading · 1
- PI-0002 · Browser agent bought groceries on a reporter's card without asking for confirmationNegligible harm, reported 1 week ago
Only these records move the reading. How it is calculated
- PI-0002Browser agent bought groceries on a reporter's card without asking for confirmationFeb. 7, 2025 · Negligible harm · Deployment
Sources
These links support the records above. Source availability and conclusions may change.
- The Washington Post: I let ChatGPT's new 'agent' manage my life. It spent $31 on a dozen eggs.Cited in PI-0002
- Anchorage Daily News: I let ChatGPT's new agent manage my life. It spent $31 on a dozen eggs (Washington Post, reprinted)Cited in PI-0002
- AI Incident Database: AI Incident Database entity: InstacartCited in PI-0002
Every weekly brief · How this reading is calculated · Download the weekly card
