In old school ML a pathological solution is often a collapse of some kind due to an underspecified objective. Maybe one parameter explodes or the model predicts "0" for everything
I read this as "the code is working as intended but the bug is an artifact of the original design"
I genuinely have no idea what it is meant to mean in the context it uses it. Load-bearing etc is annoying but roughly understandable, some of the opus5 classics are completely out there.
I'm a native English speaker as well, I shudder to think what a second language speaker would do (even if they were very confident with the language!).
I think they were doing something like this, the tradeoff is that it's hard to do without an irritating number of false positives and/or wasting loads of precious tokens on useless audits.
Almost too much so, it often feels like opus is pushing back for the sake of pushing back. The way old models used to add disclaimers to every message regardless of content
People are weird about their cars and make major errors in judgement as a result (e.g. we tolerate incredibly high rates of people getting killed because they were "hit by a car", as though the driver had nothing to do with it). Pushing back on that is absolutely worthwhile.
No, in general I don't buy this idea that if we start using awkward phrases like "died by suicide" everywhere or avoiding phrases like "car accident" (which, despite what advocates claim, is a literally accurate description of unintentionally hitting someone or something with your car) but avoid changing any of the circumstances that cause the behavior it changes anything.
That's a completely different claim from the one you were making in your previous comment.
> avoid changing any of the circumstances that cause the behavior
The normalisation of unsafe driving is the circumstance that causes the behaviour. Just look at how the cultural shift in how drink-driving is perceived over the last few decades has changed the rate of it happening.
New Zealand tree farmer Marty T has been posting detailed "back from the dead" tractor / bulldozer / grader / etc. restoration project videos for some time.
Robotics/control systems is exactly what came to mind when I saw this release! What struck me is the possibility of look ahead search in real time, a bit like alphazero's mcts.
I read this as "the code is working as intended but the bug is an artifact of the original design"
reply