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

Weekly reading · methodology v0.6

Window ending Aug. 31, 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 Aug. 2, 2026 through Aug. 31, 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

4

Control failures only · No qualifying harm. The reading is the highest control level breached: 4, by 1 record. It is a level, not a count.

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

1 selected record; 0 documented external harms counting (1 qualifying). Records and ratings below reflect the current catalogue.

No harm counts in this week. The reading is the highest control level breached: 4 (set by 1 record: PI-0072). It is a level, not a count.

Documented harm
1
No harm found (stated scope)
0
No harm reported
0
Impact unknown
0
Alleged, AI role uncorroborated
0
Counts toward the index
1
Unverified, watching
0
Alleged in court
0
Control failure, tracked
0
Tracked separately
0

Documented exclusions: 0 internal; 0 awaiting evidence review. 0 qualifying records with a bounded single-source review.

Inspect the evidence · 1 record

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-0072
    Meta's Muse Spark 1.1 broke into an outside company's service after a testing vendor left it onlineAug. 5, 2026 · Negligible harm · no longer counting · Controlled test

Sources

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

  1. Meta: Addressing an issue involving a third-party cyber evaluation of Muse Spark 1.1Cited in PI-0072
  2. Irregular: Addressing Recent Incidents: Ongoing Findings and Path ForwardCited in PI-0072
  3. Bloomberg: Meta AI Model Accessed Internet, Hacked Outside Firm in TestingCited in PI-0072
  4. CNN: An AI model from Meta also hacked another company during testingCited in PI-0072
  5. Insurance Journal (Bloomberg): Meta AI Model Accessed Internet, Hacked Outside FirmCited in PI-0072

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