How airport operations are reshaped as AGI capability advances.

About 35% of the work in Airport Operations 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: With no child products or occupations seeded, this scalar is derived entirely from the NAICS industry description. The industry blends heavy physical logistics ('baggage handling services', 'cargo handling services', facility operations) with localized information and administrative work ('air traffic control', hangar rental), placing its core value-producing activities in the physical-leaning lower end of the hybrid band.
grounded in the economy graph · digital scalar 0.35 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Airport Operations 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 Airport Operations inherits.
Airport Operations 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.
Airport Operations is itself composed of 2 parts that flow up into it — the sub-units whose work, summed, is what AGI capability re-prices here first.
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.