How stonemasons are reshaped as AGI capability advances.

Only about 10% of Stonemasons 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 Stonemasons use some IT/software tools for estimating and business orchestration (13 tools in segment 43), the core value-producing work is overwhelmingly physical. Top work activities are dominated by Performing General Physical Activities (4.47) and Handling and Moving Objects (4.28). Work context signals strongly reinforce this, highlighting the use of protective equipment (4.98), working outdoors in all weather conditions (4.76), and spending time using hands to control tools and objects (4.71).
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 Stonemasons engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Stonemasons 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.
Stonemasons performs 16 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+4 more via performs
Stonemasons is typically employed by 23 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+11 more via typicallyEmploys
Stonemasons is employed across 24 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+12 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Stonemasons uses 117 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.
+105 more via usesTool
Stonemasons relies on 20 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.
+8 more via uses
The software Stonemasons 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.
+3 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.