How ro-ro and auto handlers are reshaped as AGI capability advances.

Only about 25% of Ro-Ro and Auto Handlers 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: Since no child JobTypes are seeded, the scalar is derived from the company type name 'Ro-Ro and Auto Handlers' and its described roles. The core value delivery is heavily physical, relying on Lashing Foremen, Stevedores, and Equipment Maintenance to physically move and secure vehicles. While departments like Inventory Control & EDI and Yard Planning introduce digital orchestration, the primary work remains the hands-on handling of physical assets, placing this firmly in the physical band.
grounded in the economy graph · digital scalar 0.25 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Decomposed as an executable program, Ro-Ro and Auto Handlers 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.
Ro-Ro and Auto Handlers 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 Ro-Ro and Auto Handlers resolves to 6 concrete tasks. Sorted into Code / Generative / Agentic / Human, this task ledger is exactly where the automation frontier is drawn.
Ro-Ro and Auto Handlers 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 Ro-Ro and Auto Handlers inherits.
The outcomes here that AI agents now deliver directly, where revenue scales with compute, not headcount.
Ro-Ro and Auto Handlers uses 8 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.
Ro-Ro and Auto Handlers 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.
Ro-Ro and Auto Handlers 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.