How grounds maintenance workers are reshaped as AGI capability advances.

Only about 15% of Grounds Maintenance 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 grounding block lacks specific O*NET tools, work activities, or context data for this occupation. Relying on the seeded anchor prior provided in the subject (physical, 0.15) and the occupation name, 'Grounds Maintenance Workers' perform inherently hands-on, outdoor labor where AI can only assist in orchestration.
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.
Grounds Maintenance Workers is typically employed by 321 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+309 more via typicallyEmploys
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Grounds Maintenance Workers relies on 5 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 Grounds Maintenance Workers 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.
+4 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.