How millwrights are reshaped as AGI capability advances.

Only about 10% of Millwrights 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 Millwrights use some IT/software tools (8 tools in segment 43, prior=0.85), their toolset is dominated by physical equipment (13 tools in segment 27, prior=0.00). The top Work Activities ('Repairing and Maintaining Mechanical Equipment' at 4.77, 'Handling and Moving Objects' at 4.45) and Work Context attributes (scoring 5.00 for wearing protective equipment and 4.50 for exposure to hazardous equipment) definitively peg this as hands-on, physical labor.
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 Millwrights engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Millwrights 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.
Millwrights performs 23 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+11 more via performs
Millwrights is typically employed by 127 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+115 more via typicallyEmploys
Millwrights is employed across 89 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+77 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Millwrights uses 185 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.
+173 more via usesTool
Millwrights relies on 14 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.
+2 more via uses
The software Millwrights 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.
+7 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.