An open problem, and it isn't ours
Hand-tune your inner loops. Know your register pressure. Count cycles. Every one of those was correct, and every one was quietly conditional on something a compiler later removed. The people who worked out which wisdom had expired wrote the next thirty years of software.
A great deal of what this profession knows about distributed systems has the same shape. Real-time media rides UDP — because a late frame is worse than a lost one, which is true when you have no better way to shed load. Cache invalidation is hard — when a cache is a copy held at a distance from the authority. APIs must be versioned — when the producer owes a shape contract to named consumers. None of those is wrong. Each is downstream of a premise, and the premise is message passing.
Name a law in your own field. Recover the assumption that made it true. Check whether this substrate still supplies it.
That audit needs no licence, no install, and nothing from us. Not every law expires — reads scale by replication, and one elected host is a serialization point, which is a ceiling. The coherence win and the scaling cost are the same fact. Anyone doing this honestly will find laws that are still laws, and that is what makes it research rather than advocacy.