How bus drivers, school are reshaped as AGI capability advances.

Only about 10% of Bus Drivers, School 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: Despite the presence of segment 43 IT/telecom tools (GPS, cell phones, routing software), the core value of this occupation is strictly physical. Top work activities are dominated by 'Inspecting Equipment' (4.32) and 'Operating Vehicles' (4.21), utilizing segment 25 tools like passenger buses. The work context confirms this manual, location-bound reality with top scores for 'In an Enclosed Vehicle' (4.84), 'Using Your Hands to Handle... Controls' (4.39), and 'Outdoors, Exposed to All Weather' (3.90). AI can assist with routing or dispatch, but the primary work requires a human operating a physical vehicle.
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 Bus Drivers, School engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Bus Drivers, School 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.
Bus Drivers, School performs 17 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+5 more via performs
Bus Drivers, School is typically employed by 62 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+50 more via typicallyEmploys
Bus Drivers, School is employed across 36 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+24 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Bus Drivers, School uses 17 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.
+5 more via usesTool
Bus Drivers, School relies on 7 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 Bus Drivers, School 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.
No articles yet for this entity.
No capability events for this entity yet.