How captive automotive forge plants are reshaped as AGI capability advances.

Only about 10% of Captive Automotive Forge Plants 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: With no child JobTypes seeded, the score relies on the company type name 'Captive Automotive Forge Plants', its parent industry 'Iron and Steel Forging', and the description. The listed roles (Forge Press Operator, Heavy Industrial Millwright) and departments (Forge Shop, Heat Treat) denote heavy industrial manufacturing, placing this firmly in the physical band.
grounded in the economy graph · digital scalar 0.10 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Captive Automotive Forge Plants runs 11 core processes — each a candidate for the Code / Generative / Agentic / Human split, with the agentic and code-shaped steps the first to come off human headcount.
Captive Automotive Forge Plants is organized into 8 departments. Read as functions of one executable business, each department is a unit of work whose back-office share is increasingly delivered by earned-autonomy digital labor.
The operating model of Captive Automotive Forge Plants resolves to 7 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Captive Automotive Forge Plants sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Captive Automotive Forge Plants inherits.
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Captive Automotive Forge Plants uses 8 products to deliver its outcomes — the toolchain whose work an autonomous stack absorbs as the service becomes software.
Captive Automotive Forge Plants is served by 1 offering on the graph — demand that an executable-function provider can capture as the outcome turns into software.
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Captive Automotive Forge Plants staffs 8 job types — the roles that, decomposed to tasks, are first in line to run as supervised-then-autonomous digital labor.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Captive Automotive Forge Plants relies on 8 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.
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.