How plant manager are reshaped as AGI capability advances.

About 50% of the work in Plant Manager is information-shaped and increasingly AI-deliverable, with the rest a hybrid of judgment and hands-on work. The automation frontier runs straight through the middle of this role.
Why: Lacking a known digital scalar for the parent occupation or any child components, this scalar is derived from the job type's name and description. Overseeing 'Manufacturing Operations' and 'Plant Operations' requires physical presence and site management, while the parent occupation's top activities ('Working with Computers' at 4.46, 'Making Decisions' at 4.33) reflect heavy information processing, placing this role squarely in the hybrid band.
grounded in the economy graph · digital scalar 0.50 · hybrid
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Plant Manager is staffed by 22 sources of labor — the supply that an agent workforce reshapes from headcount to earned-autonomy configuration.
+10 more via staffs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Plant Manager 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 Plant Manager reaches for already exposes 8 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.
+3 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.