Engineering a Safer World: Risk Modelling – and Safety Engineering? – For AI Lo
The article discusses the importance of systems thinking in safety engineering, particularly in the context of AI. It highlights Nancy Leveson's book, 'Engineering a Safer World', which emphasizes that safety is a systemic property rather than a result of a single cause. The author reflects on their experiences with risk modeling and the need for a comprehensive understanding of interrelated systems to prevent disasters.
- ▪Nancy Leveson's book, 'Engineering a Safer World', is recommended for its insights into safety science and systems thinking.
- ▪The author emphasizes that safety is a system property and that disasters often result from systemic failures rather than isolated incidents.
- ▪The article draws on the author's experience with risk modeling at the UK government's AI Safety/Security Institute and the Future of Life Foundation.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,511 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Lesswrong |
| Canonical URL | https://www.lesswrong.com/posts/mL5asdegoa56CkqgJ/engineering-a-safer-world-risk-modelling-and-safety |
| Publication time | Sun, 17 May 2026 17:00:56 +0000 |
| Retrieval time | 2026-05-17T17:08:20.797Z |
| Last seen | 2026-05-17T17:08:21.369Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Zd81QRKA5pK5 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Engineering a safer world.I, and I imagine many of my readers, are eager to contribute to that effort[1].It's also, conveniently, the title of a book!Engineering a safer world, by Nancy LevesonIt's not a book by me… but nevertheless I recommend it. You should consider reading it, especially the first chapters. You can find it online free from MIT. It's by MIT professor Nancy Leveson, computer scientist turned innovator in safety science, safety engineering, and software safety.Generally, this book is a particularly approachable and competent example of systems thinking or what I might call a cybernetic perspective — applied to safety science. This essay is in part a brief book review of Leveson's Engineering a Safer World.I care about this systems perspective in part because...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Lesswrong.
Discussion
0 commentsMore from Lesswrong
