How tank car, truck, and ship loaders are reshaped as AGI capability advances.

Only about 25% of Tank Car, Truck, and Ship Loaders 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 role relies on a mix of IT tools for coordination (10 tools in segment 43, such as SAP and WMS) and heavy machinery for execution (8 tools in segment 24, including mobile shiploaders and reach trucks). While cognitive activities like 'Processing Information' score highly, the core value is physical, driven by activities like 'Operating Vehicles' (4.15) and 'Handling and Moving Objects' (4.13). The work context is intensely physical and exposed, defined by 'Wear Common Protective Equipment' (4.94), 'Outdoors, Exposed to All Weather' (4.76), and 'Exposed to Hazardous Conditions' (4.65), placing this firmly in the physical band with digital orchestration.
grounded in the economy graph · digital scalar 0.25 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Tank Car, Truck, and Ship Loaders engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Tank Car, Truck, and Ship Loaders 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.
Tank Car, Truck, and Ship Loaders performs 19 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+7 more via performs
Tank Car, Truck, and Ship Loaders 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
Tank Car, Truck, and Ship Loaders is employed across 43 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+31 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Tank Car, Truck, and Ship Loaders uses 17 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.
+5 more via usesTool
Tank Car, Truck, and Ship Loaders relies on 10 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 Tank Car, Truck, and Ship Loaders 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.