How fleet mechanic are reshaped as AGI capability advances.

Only about 15% of Fleet Mechanic 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 child roll-up data is sparse, the scalar is derived from the parent occupation, Automotive Service Technicians and Mechanics. The anchor's top work activities—'Operating Vehicles, Mechanized Devices, or Equipment' (4.47) and 'Repairing and Maintaining Mechanical Equipment' (4.15)—strongly indicate hands-on, manual labor. These highly physical tasks push the scalar well below 0.3, placing the job type firmly in the physical band.
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.
Fleet Mechanic is staffed by 12 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 Mechanic relies on 6 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 Mechanic 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.