How transportation service attendants are reshaped as AGI capability advances.

Only about 15% of Transportation Service Attendants 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 the grounding block provides no specific tools, work activities, or context data for this occupation, the scalar relies directly on the seeded anchor value (physical, 0.15) and the deterministic SOC code prior of 0.00, reflecting entirely hands-on transportation service work.
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.
Transportation Service Attendants is typically employed by 76 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+64 more via typicallyEmploys
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Transportation Service Attendants 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 Transportation Service Attendants reaches for already exposes 7 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.
+2 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.