But, it's not immediately obvious how to train models to be better about this, because we don't really have ground truth. An idea I've been excited about which seems underexplored, and could potentially be done outside labs, is to train and evaluate models on making safety cases in domains where we *do* have ground truth, or at least where the claims can be checked mechanically.
For example, we could generate a bunch of bridge designs, test them out in a simulator to enumerate failure modes, and then train models to generate accurate safety cases / risk reports in this domain.
Then we could do the same thing for buildings, and airplanes, and so on. If we train on just bridges and buildings, do we see generalization to held-out domains like airplanes?
A particularly interesting domain is properties of complex computer programs (which have more analogies to neural networks). E.g. Ask for a case that a concurrent system deadlocks with probability < ε under a specified workload and scheduler, or that a protocol preserves an invariant. Check the claims with model checking, testing, or simulation.
The point is not that bridge or program safety cases are the same as AI safety cases. They give us checkable settings for studying decomposition, evidence selection, calibration, and transfer. And even if we don't find that the learned skills transfer to safety cases for frontier models, they may have scientific and commercial value in their own right.