High Stakes Are Strongly Typed

supo 18 points 7 comments November 19, 2026
www.motivenotes.ai · View on Hacker News

Discussion Highlights (6 comments)

JeromeM37

My p(doom) just increased. If this is how society learns lessons (and I can see why this has made sense until now) then we're waiting for a paperclip problem before we invest in a kill switch that works.

mihaichiorean

In the past some of these issues were discovered in real life - in blood. I wonder what role some kind of simulation can have in predicting and running scenarios to unlock opportunities low effort high risk. We have a lot of computational power to run this as well as make predictions of what can fail and how bad it could be.

coscreen

This is super relevant to cyber. Historically we've written rule after rule following every incident but that makes it close to impossible to catch things you haven't seen before. Nice write up!

thedracle

I wonder if decision models can help bridge the gap between prose, and schema or a lint rule. The problem with strong typing is sometimes you enforce a rule that is too rigid. A good example is with UTC: suppose you use strong typing to enforce across ALL datetime fields that they must be UTC. Then you need to store a birthday. A birthday stored as a UTC timestamp will show up a day early for users in another timezone. With Agents people are starting to enforce a lot more prose style requirements in their AGENTS.md or CLAUDE.md files, which have the advantage of being nuanced and flexible. The problem is these natural-language rules are prose, often ignored by agents, or arbitrarily applied. Perhaps a natural language rules-engine that runs everything through a decision model asking "Does this meet this criteria" has the strength of both. The validator could be enforced by a script to run on every commit, and it could instead enforce "All date fields should be stored in UTC, except for instants or local dates." It could even enforce things like "we never store PII in any field not in our secure-store," and other high-level criteria.

ryan-yc

Absolutely - the most valuable and expensive datasets to produce are catastrophic real-world failures. We need to encode _at least_ those direct patterns. We also need to extrapolate, simulate, and reinterpret those precious datapoints as the surrounding landscape changes. To the exent we fail to do so, we will be augment the world's catastrophic failure dataset with heartbreaking new datapoints. Victims and their families, such as the plaintiffs in the Boeing Max lawsuits, will want to see those datapoints encapsulated into future processes.

siamakfrey

Really good read- the bottleneck for decision making is totally a new paradigm and I struggle with it daily now.

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed