How laundry and dry-cleaning workers are reshaped as AGI capability advances.

Only about 15% of Laundry and Dry-Cleaning Workers 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 top Work Activities ('Handling and Moving Objects', 'Performing General Physical Activities', 'Controlling Machines and Processes') and top Work Contexts ('Spend Time Standing', 'Pace Determined by Speed of Equipment', 'Spend Time Using Your Hands') all point to highly hands-on, equipment-driven labor. While there are 11 tools in the IT/software segment (seg 43) for POS and scheduling, the core value-producing work is heavily manual, anchoring the scalar firmly in the physical band.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Laundry and Dry-Cleaning Workers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Laundry and Dry-Cleaning Workers 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.
Laundry and Dry-Cleaning Workers 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
Laundry and Dry-Cleaning Workers is typically employed by 100 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+88 more via typicallyEmploys
Laundry and Dry-Cleaning Workers is employed across 84 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+72 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Laundry and Dry-Cleaning Workers uses 38 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.
+26 more via usesTool
Laundry and Dry-Cleaning Workers relies on 15 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.
+3 more via uses
The software Laundry and Dry-Cleaning Workers 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.
No articles yet for this entity.
No capability events for this entity yet.