Clarification: what I meant is that it’s better if the rules are created in a context where there are no cases pending for the rules to bear on; ie, I’m not objecting to admitting that a rules-discussion is about a specific case that it would bear on, but to it actually being about a specific pending case.
This is how things are often done in law, tho; I think “common law” is a pretty good way to grow a body of rules. You can then abstract out principles and refactor. It’s not clear yet how much of this is about cost minimization; one of the benefits of deciding cases as they come up is you only ever need to decide as many cases as happened, which is not true if you try to decide cases before they become pending.
This is how things are often done in law, tho; I think “common law” is a pretty good way to grow a body of rules. You can then abstract out principles and refactor. It’s not clear yet how much of this is about cost minimization; one of the benefits of deciding cases as they come up is you only ever need to decide as many cases as happened, which is not true if you try to decide cases before they become pending.
On the other hand, clear systematic codes may reduce the # of cases that come up (or evaluation time per case) by reducing ambiguity.