How fleet maintenance technician are reshaped as AGI capability advances.

Only about 10% of Fleet Maintenance Technician 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 lens parent occupation, 'Bus and Truck Mechanics and Diesel Engine Specialists', is defined by heavily hands-on core activities like 'Repairing and Maintaining Mechanical Equipment' (4.62) and 'Inspecting Equipment, Structures, or Materials' (4.39). Since maintaining physical fleet assets requires direct physical labor that AI cannot natively execute, the scalar sits firmly in the physical band.
grounded in the economy graph · digital scalar 0.10 · physical
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Fleet Maintenance Technician is staffed by 7 sources of labor — the supply that an agent workforce reshapes from headcount to earned-autonomy configuration.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Fleet Maintenance Technician 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 Fleet Maintenance Technician 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.