How passenger attendants are reshaped as AGI capability advances.

Only about 20% of Passenger Attendants 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: Although 9 of the 26 tools are in IT/software (segment 43), the remaining 17 tools fall into physical segments with a 0.00 prior (e.g., mechanical lifts, parking cones, light trucks). Work contexts like 'Physical Proximity' (4.70), 'Exposed to Very Hot or Cold Temperatures' (3.83), and 'In an Enclosed Vehicle or Operate Enclosed Equipment' (3.44) firmly anchor this role in the physical world. Work activities such as 'Assisting and Caring for Others' and 'Establishing and Maintaining Interpersonal Relationships' highlight in-person human interaction over digital information transformation, keeping the scalar low.
grounded in the economy graph · digital scalar 0.20 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Passenger Attendants engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Passenger Attendants involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Passenger Attendants performs 12 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
Passenger Attendants is typically employed by 48 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+36 more via typicallyEmploys
Passenger Attendants is employed across 30 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+18 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Passenger Attendants uses 20 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
+8 more via usesTool
Passenger Attendants relies on 10 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.
The software Passenger Attendants reaches for already exposes 12 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
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.