How transportation security screeners are reshaped as AGI capability advances.

Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Transportation Security Screeners engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Transportation Security Screeners 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.
Transportation Security Screeners performs 26 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+14 more via performs
Transportation Security Screeners is typically employed by 4 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
Transportation Security Screeners is employed across 8 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Transportation Security Screeners uses 18 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.
+6 more via usesTool
Transportation Security Screeners relies on 12 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 Transportation Security Screeners 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.
No articles yet for this entity.
No capability events for this entity yet.