I have no clue about the state of robotics.
For software, I know that Opus 5.5 can handle more than GPT 5.6 Sol. I am willing to pay for the difference rather than use the cheaper DeepSeek Flash.
The prerequisite here is that you can trust it not to do something that gives criminals access to your bank account or allows users to consume an unlimited amount of services it costs you money to provide for free or bankrupts you through legal liability etc.
It's basically this:
"A computer can never be held accountable, therefore a computer must never make a management decision."
Notice what this is actually saying. It's not saying that the computer can't generate a given output. It's saying that if the computer makes a mistake and you don't bother to check, you're the one who has to eat it.
That's a great way of putting it. So far I always used 'you can outsource work but you can't outsource responsibility'.
Legendary quote from an internal 1979 IBM training document [1]
https://simonwillison.net/2025/Feb/3/a-computer-can-never-be...
If you can't leverage AI to build a safe and useful robot without fully understanding the implementation, the model is not good enough.
My argument is that if safety and liability make the use of AI without fully understanding the implementation impossible, the model is arguably not good enough.
No such process exists for a model to take a design seriously that can kill people.
When we manually tested nuclear power plant controlling software, each test case was printed out on paper and tested and then signed by the tester. A lot of paper was produced and archived for each software release. (Archived for as long as the software was running in any nuclear power plant).
Everyone understood, that in a case of significant accident at the nuclear power plant, accident analysis would be done and if the root cause was an software error, this could have possible legal consequences for the developers and testers. (Of course nuclear power plants have many independent and redundant hardware controlling mechanisms, but incorrectly working controlling software could damage the power plant in a very costly way).
I imagine that the requirement is that after testing, you are confident that the product is safe.
I think you're entirely wrong, and we can leave it at that, seeing that you're clearly unwilling to engage constructively.
As for the manual feedback: I want that manual feedback, but if I let it rip it will do just fine all by itself, but then I have no clue what is going on under the hood.