How sewers, hand are reshaped as AGI capability advances.

Only about 15% of Sewers, Hand 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: While the tools list includes 13 items in the software segment (seg 43) for design, the majority sit in physical segments (seg 27, 53) with a 0.00 digital prior. Top work activities like 'Controlling Machines and Processes' (4.10) and 'Handling and Moving Objects' (3.30) indicate physical execution. This is strongly reinforced by work context scores for 'Spend Time Making Repetitive Motions' (4.30), 'Pace Determined by Speed of Equipment' (3.82), and 'Spend Time Using Your Hands to Handle, Control, or Feel Objects' (3.60), placing the occupation firmly in the physical band.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Sewers, Hand engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Sewers, Hand 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.
Sewers, Hand performs 11 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
Sewers, Hand is typically employed by 10 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
Sewers, Hand is employed across 34 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+22 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Sewers, Hand uses 24 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.
+12 more via usesTool
Sewers, Hand relies on 19 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.
+7 more via uses
The software Sewers, Hand 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.
+2 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.