How water transportation are reshaped as AGI capability advances.

Only about 15% of Water Transportation 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 the component occupations lack known digital values, the scalar is derived from the industry lens. The subsector description explicitly centers on providing 'water transportation of passengers and cargo using watercraft, such as ships, barges, and boats', which is heavily physical logistical and operational work.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Water Transportation 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 Water Transportation inherits.
Water Transportation links to 2 entities via `specializes` — a real edge on the economy graph, surfaced here so the claim stays grounded in data rather than assertion.
Water Transportation links to 15 entities via `suppliesTo` — a real edge on the economy graph, surfaced here so the claim stays grounded in data rather than assertion.
+3 more via suppliesTo
Water Transportation is itself composed of 6 parts that flow up into it — the sub-units whose work, summed, is what AGI capability re-prices here first.
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Water Transportation employs 114 occupations — the workforce whose routine, information-shaped tasks an autonomous stack can take under typed authority.
+102 more via employs
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.