How construction and extraction occupations are reshaped as AGI capability advances.

Only about 15% of Construction and Extraction Occupations 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: Because specific O*NET tool and activity signals are unavailable for this broad Major Group, the scalar relies on the seeded description and the deterministic SOC prior of 0.00. The anchor explicitly places this occupation within 'Electrical Contractors', 'Plumbing', and 'Residential Building Construction'—all hands-on trades requiring direct physical labor, dictating a physical band-center score.
grounded in the economy graph · digital scalar 0.15 · physical
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Construction and Extraction Occupations is typically employed by 470 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+458 more via typicallyEmploys
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Construction and Extraction Occupations relies on 4 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.
The software Construction and Extraction Occupations 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.
+11 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.