How hoist and winch operators are reshaped as AGI capability advances.

Only about 5% of Hoist and Winch Operators is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: The tool segment distribution is overwhelmingly physical, with 23 of 25 tools falling into material handling (seg 24), general machinery (seg 27), and construction equipment (seg 22) bearing 0.00 digital priors. Top work activities like 'Repairing and Maintaining Mechanical Equipment' (4.24) and 'Operating Vehicles, Mechanized Devices, or Equipment' (4.12) point to direct hands-on execution. Work context scores for wearing protective equipment (5.00) and using hands to handle objects (4.89) confirm this is a pure physical role.
grounded in the economy graph · digital scalar 0.05 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Hoist and Winch Operators engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Hoist and Winch Operators involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Hoist and Winch Operators performs 13 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+1 more via performs
Hoist and Winch Operators is typically employed by 29 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+17 more via typicallyEmploys
Hoist and Winch Operators is employed across 42 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+30 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Hoist and Winch Operators uses 23 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
+11 more via usesTool
Hoist and Winch Operators relies on 5 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
The software Hoist and Winch Operators reaches for already exposes 8 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
No articles yet for this entity.
No capability events for this entity yet.