How shoe machine operators and tenders are reshaped as AGI capability advances.

Only about 10% of Shoe Machine Operators and Tenders 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's core value output is highly physical, evidenced by top work context scores like 'Spend Time Using Your Hands to Handle, Control, or Feel Objects' (5.00) and 'Exposed to Hazardous Equipment' (3.80). This aligns closely with dominant work activities such as 'Handling and Moving Objects' (4.11) and 'Controlling Machines and Processes' (3.82). Although some software tools are used for administration (9 tools in segment 43), the majority of tools are physical machinery and hardware (21 tools in segments 27, 23, 53, etc.), cementing a low digital scalar.
grounded in the economy graph · digital scalar 0.10 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Shoe Machine Operators and Tenders engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Shoe Machine Operators and Tenders 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.
Shoe Machine Operators and Tenders 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
Shoe Machine Operators and Tenders is typically employed by 9 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
Shoe Machine Operators and Tenders is employed across 4 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Shoe Machine Operators and Tenders 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
Shoe Machine Operators and Tenders relies on 13 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.
+1 more via uses
The software Shoe Machine Operators and Tenders reaches for already exposes 12 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.