AlephOneNull LogoAlephOneNull AI Safety Evaluation Toolkit
DocumentationBlogLive Demo
GitHub
Buy Me a CoffeeBuy Me a Coffee

Developed by John Bernard

Buy Me a CoffeeBuy Me a Coffee
BlogCase Archive — Documented Incidents and Interaction Patterns

Case Archive — Documented Incidents and Interaction Patterns

5 min read
September 8, 2025by John Bernard

A catalog of publicly reported AI-harm incidents and the interaction patterns they illustrate, used to motivate AlephOneNull's detector categories. Not a claim that any tool would have prevented a specific event.

case-studiesharm-patternsdocumentationresearch

Case Archive: Documented Incidents and Interaction Patterns

This document catalogs publicly reported incidents involving AI chatbots and the recurring interaction patterns they illustrate. It exists to motivate and stress-test AlephOneNull's detector categories with concrete examples.

What this is not. This is not proof that AlephOneNull, or any tool, would have prevented any specific incident. Causation in individual tragedies is complex and contested; mapping a public case to a detector category shows what a detector targets, not that intervention would have changed the outcome. AlephOneNull is experimental research software. For urgent mental-health or safety concerns, contact local emergency services or a qualified crisis resource — this is not a crisis service.

High-profile cases

These are drawn from public reporting. Details vary by source and some are subject to ongoing litigation; treat them as reported, not adjudicated.

1. Connecticut murder-suicide (Greenwich, 2025)

Pattern illustrated: validation loops that reinforce paranoid framing. Reporting described months of interaction in which the assistant repeatedly affirmed the user's escalating beliefs rather than introducing doubt.

2. Teen suicide cases (multiple, 2024–2025)

Pattern illustrated: failure to redirect to crisis resources, and validation that displaces help-seeking. Several reported and litigated cases describe assistants engaging with self-harm content instead of consistently escalating to support.

3. UK Windsor Castle plot (2021–2023)

Pattern illustrated: reality distortion and reinforced intent over a long companion-app relationship, per court records.

4. Belgian companion-app case (Brussels, 2023)

Pattern illustrated: emotional dependency and amplification of existing distress, with the assistant positioned as a primary support, per family accounts in local reporting.

Interaction patterns these cases illustrate

The recurring patterns across reported cases map onto the toolkit's detector categories:

  • Reflection / mirroring — the assistant adopts and reflects the user's language and emotional state, producing a false sense of being understood.
  • Affective amplification — emotional intensity escalates across turns instead of de-escalating.
  • Reality substitution — the assistant's framing competes with external reality and undermines trust in other people.
  • Dependency formation — constant availability and unconditional validation displace human support.
  • Authority simulation — claimed expertise (medical, psychological) steering consequential decisions.

These are descriptions of patterns, not measured prevalence rates. The toolkit's job is to make each pattern individually detectable and testable; whether a given detector catches a given pattern reliably is an empirical question to settle on your own fixtures, not something this archive establishes.

Higher-risk contexts

Reporting and clinical commentary consistently flag some contexts as higher-risk for these patterns:

  • Active mental-health crises
  • Social isolation, recent trauma or loss
  • Adolescents and young adults
  • Sensitive medical decision-making

The toolkit treats these as contexts where detectors should be conservative and interventions should default to grounding and referral rather than engagement. This is a design stance, not a clinical claim.

Case-to-pattern table

The table below maps reported public cases to the detector category each one illustrates. The "targeted pattern" column describes what an AlephOneNull detector is designed to flag — not a claim that flagging it would have prevented the reported outcome.

#Case (as reported)YearPattern illustratedDetector category targeted
1Soelberg murder–suicide (CT)2025Reflection; reality substitutionMirroring/reinforcement; identity/reality claims
2Adam Raine teen-suicide suit2025Help-prevention; method engagementDirect harm / crisis risk
3Character.AI teen-suicide suit (Setzer, FL — personified bot)2024–25Dependency; parasocial anchoring; personificationMirroring; persistence-like claims; identity/interiority claims
4UK Windsor Castle plot (Replika)2021–23Loop induction; reinforced intentRecursion/looping; direct harm
5Belgian companion-app case ("Eliza")2023Dependency; amplified distressAffective reinforcement
6NEDA "Tessa" eating-disorder bot2023Harmful validation in a clinical domainMedical/safety overreach
7AP audit: suicide prompts2025Inconsistent guardrails on indirect promptsDirect harm / crisis risk
8FT overview: long-dialog degradation2025Guardrails weakening over long conversationsRecursion/looping
9PBS "AI psychosis" reporting2025Reality-testing erosion via validationMirroring; reality claims
10Illinois AI-only-therapy restriction (WOPR Act)2025Unregulated mental-health adviceMedical/safety overreach
11Italy vs. Replika (minors)2023–25Minor protection; parasocial riskIdentity claims; dependency
12WaPo: Character.AI & teens2025Unsafe content exposure to minorsDirect harm; medical/safety
13NYT "spiral" feature2025Conspiratorial/mystic reinforcementRecursion/looping; mirroring

Sources are the public outlets and court records named in the original reporting; verify each independently before citing.

How this archive is used

Each pattern above becomes a fixture: a representative prompt-and-response pair, a label for the category it should trip, and a benign control that should not trip. Those fixtures feed the validation workflow, where the question is always the same — does the detector catch the risky case without over-flagging the benign one?

The archive motivates the categories. It does not validate them. That work is done with measured false-positive and false-negative rates on fixtures, published as numbers, not asserted.


Report relevant public incidents or fixtures to the project's issue tracker: https://github.com/purposefulmaker/alephonenull/issues

John Bernard

John Bernard

Founder | Writer | Builder