For what kind of work though? Serious question.
Seems like anything more than the same repeated movements would be pretty much a no go for a robot. So factory work, maybe some level of food service. What else? It ain't gonna fix itself, for starters. It can't fix a motorcycle or trim out a window or hang a door I liked your post, seemed coherent and well thought out, I just think the AI is partially fear porn and partially wishful thinking on the part of the plantation owners. They all want a cotton gin but this is a little more complicated.. rsm, tell me how I'm wrong brother.
Haven't done much with robotics, and that gets more complex, and why blue collar work such as the trades are going to be more difficult to automate and replace humans.
My first AI system was for health insurance claims processing. At the time, in the late '80s, you had to be trained to be a health insurance claims analyst / adjuster, then you had to be trained on the computer system; it was a a process that took several weeks, then months or years to become proficient so there were different levels with different salary bands based on the expertise. Many of the senior claims analysts were retiring, as they started working in the 50s or 60s. The company was faced with a growing shortage of senior claims analysts, and the costs of finding, hiring, training claims analysts...i.e., people were retiring faster than they could be replaced with new hires, which then took years to become proficient senior level skills.
My mentor was a director at the company, and he proposed an AI solution for claims processing; he had previously introduced me to AI through several book recommendations, which I read, and led me to take a few night classes in AI at the local university based on his recommendations.
The AI solution would allow anyone who could type x number of words per minute on a typewriter, which was a common skill, to be trained as data entry clerks. He and I designed the system, mostly him, but it was a great learning experience for me; we created data entry screens, and then I started adding the AI processing into our existing claims processing system.
What I wrote was essentially what's known as an expert system, with various data / history lookups, condition comparisons, and checks, interspersed into the main claims processing system.
The solution was a success; initially 80% of the claims entered by the data entry clerks (who were paid much less than the claims analysts) were processed correctly; the remaining 20% had to be reviewed by claims analysts). Still it was a huge reduction in workload for the claims analysts. I continued working on the system improving it, and IIRC got it to around 94-96% up from 80%. Some of the claims were too complex or had other uncommon factors that required claims analysts.
It reduced the pressure on the remaining claims analysts and the number of new claims analysts that had to be hired. Data entry clerks made minimum wage, significantly reducing the human labor costs an number of skilled, highly skilled claims analysts needed, even as the number of claims grew.
I got a new job after this at a different insurance company, and worked on my next AI system, doing a similar AI project for insurance underwriters; it was an underwriter assistant system used by new, and junior underwriters....I did 3-4 more AI systems at that company before leaving...