How dredge operators are reshaped as AGI capability advances.

Only about 10% of Dredge Operators 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: The strongest signals indicate highly physical work. Top Work Activities include 'Controlling Machines and Processes' (4.23), 'Handling and Moving Objects' (3.94), and 'Performing General Physical Activities' (3.54). The Work Context reinforces this with 'Outdoors, Exposed to All Weather Conditions' (4.45) and 'Exposed to Hazardous Equipment' (3.93). While they use some navigation/hydrographic software (segment 43), the bulk of their tools (segments 22, 41, 46, 27) are physical machinery and equipment, landing this firmly in the physical band.
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 Dredge Operators engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Dredge Operators 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.
Dredge Operators performs 6 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
Dredge Operators is typically employed by 8 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
Dredge Operators is employed across 6 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Dredge Operators uses 33 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.
+21 more via usesTool
Dredge Operators relies on 10 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.
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.