At Least 13 People Died by Suicide Amid U.K. Post Office Scandal, Report Says
Scandal, human cost, and context
- Commenters emphasise the scale: hundreds of ruined lives, bankruptcies, family breakdown, social ostracism and at least a dozen suicides.
- Some argue these were effectively deaths by state torture: people cornered by wrongful prosecutions, debts and stigma. Others insist they remain suicides in a strict sense, but agree the Post Office and state bear heavy causal responsibility.
Who is responsible: software vs management vs state
- Strong consensus that Horizon’s bugs were a trigger, but not the main cause; the decisive harm came from Post Office management, lawyers, and compliant courts.
- Fujitsu is repeatedly described as deeply complicit: knowing about bugs, remote data edits, misleading courts about system reliability and access, and coaching witnesses.
- Some want criminal charges (perjury, corporate manslaughter) for senior engineers who testified Horizon was sound while internal tickets showed otherwise, and for Post Office executives who drove prosecutions and cover‑ups.
Legal and institutional failures
- A key structural failure: the Post Office’s power to bring private prosecutions, acting as victim, investigator and prosecutor at once.
- Courts relied on a common-law presumption that computer systems are correct unless proven otherwise, which was almost impossible for individual defendants lacking access to code or logs.
- Defence lawyers often abandoned software lines of argument after being told “no other branches have problems”; this was later shown false.
- Commenters link this to a wider pattern of a dehumanised, rules‑driven UK state that treats citizens as presumptive offenders (tax, benefits, speeding enforcement).
Technical and software-engineering lessons
- Horizon’s failures were systemic, not a single bug: non‑transactional distributed design, missing idempotency, poor auditability, UI causing mis-entries, failing touchscreens, byzantine failures on hardware replacement, and unaudited direct DB edits.
- Several argue Horizon should join or replace Therac‑25 in software ethics curricula: an “ordinary” retail/accounting system with non‑obvious but catastrophic safety impact.
- Lessons highlighted: event/audit-driven design, strict separation of prod data from developer access, double-entry accounting, robust migration strategies (double‑writing, verification, and human forensic review before criminal referrals).
Language and suicide: agency vs blame
- Long debate over “died by suicide” vs “committed suicide” vs “driven to suicide”.
- One camp sees “died by suicide” as necessary, less-criminalising language; another finds it euphemistic and agency-erasing, especially when third parties clearly contributed.
- Some prefer formulations that foreground causality (“driven to suicide by false accusations”) without erasing the person’s act or overstating inevitability.
Class, race, media, and culture
- Multiple comments stress a class dimension: leadership allegedly saw one‑shop owner‑operators as inherently suspect—“buying a job” implied they must be stealing.
- Racist abuse in at least one case (a pregnant postmistress of colour) is noted as part of the social damage once tabloids and communities branded people thieves.
- UK tabloids are condemned for sensationalising convictions and helping destroy reputations; some want tighter defamation or harassment enforcement, others warn against state censorship.
Role of journalism and dramatization
- Investigative work by niche outlets and trade press (notably a satirical magazine and an IT journal) is credited with keeping the issue alive for years.
- The TV drama “Mr Bates vs The Post Office” is widely seen as the turning point for public and political attention, though formal inquiries and litigation predated it.
- This leads to broader concern that many complex injustices only gain traction once turned into compelling narrative media.
Broader implications and comparisons
- Commenters draw parallels to other systemic miscarriages of justice based on opaque “expert” evidence: shaken-baby syndrome, forensic DNA software, benefit-fraud algorithms.
- Some fear future repeats as courts increasingly trust opaque digital and AI systems; others point to ongoing reviews of how software-generated evidence should be treated.
- For CS and engineering, many argue for mandatory ethics education tied to real accountability: developers and architects must be prepared to whistleblow when systems hurt people.