How architectural and civil drafters are reshaped as AGI capability advances.

Roughly 85% of the work in Architectural and Civil Drafters is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: The occupation's toolset is 100% concentrated in UNSPSC segment 43 (IT/software), establishing a strong digital prior. This is strongly corroborated by its top work activity, 'Working with Computers' (importance 4.77), and a work context dominated by 'E-Mail' (4.93), 'Indoors, Environmentally Controlled' (4.67), and 'Spend Time Sitting' (4.52), placing the role firmly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Architectural and Civil Drafters engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Architectural and Civil Drafters 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.
Architectural and Civil Drafters performs 28 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+16 more via performs
Architectural and Civil Drafters is typically employed by 150 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+138 more via typicallyEmploys
Architectural and Civil Drafters is employed across 90 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+78 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Architectural and Civil Drafters 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
Architectural and Civil Drafters relies on 83 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.
+71 more via uses
The software Architectural and Civil Drafters 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.