How captive lime operators are reshaped as AGI capability advances.

Only about 15% of Captive Lime Operators 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 company type description explicitly lists heavily manual and machinery-driven roles such as Crusher Operator, Payloader Operator, and Maintenance Millwright. Furthermore, its core departments center on raw materials handling, kilns, and refractory maintenance, placing the value-producing work firmly in the physical domain with a low digital scalar.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Captive Lime Operators runs 1 core process — 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 Lime Operators 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 Lime Operators resolves to 8 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Captive Lime Operators 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 Lime Operators inherits.
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Captive Lime Operators uses 6 products to deliver its outcomes — the toolchain whose work an autonomous stack absorbs as the service becomes software.
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Captive Lime Operators 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 Lime Operators 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.
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.