It's... a weird take. "Sure, the model makes repeatedly the same mistakes, and I could prevent that, but then it wouldn't be the same model" sounds like an exc

It's... a weird take. "Sure, the model makes repeatedly the same mistakes, and I could prevent that, but then it wouldn't be the same model" sounds like an excuse for masochism. The one small bit of truth is that yes, instructions might become outdated, and they might affect negatively how the system performs. You fix that by... updating your instructions. And if you deeply care about that potential negative impact (most models are pretty good at just ignoring long outdated issues), you run evals on model upgrades. You certainly don't refuse to use anything but the bare model. (Of course, there are also folks who refuse to write code in any way except with sed, so there we go)