How transit and railroad police are reshaped as AGI capability advances.

About 45% of the work in Transit and Railroad Police 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: The signals show a strong hybrid split. Tool usage leans toward software (17 tools in segment 43), reflected by 'Documenting/Recording Information' (4.65) and 'E-Mail' (4.96). However, the role retains a heavy field presence, evidenced by high physical Work Activities ('Performing General Physical Activities' at 4.36) and Work Contexts ('In an Enclosed Vehicle' at 4.93, 'Outdoors' at 4.73).
grounded in the economy graph · digital scalar 0.45 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Transit and Railroad Police engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Transit and Railroad Police 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.
Transit and Railroad Police 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.
Transit and Railroad Police is employed across 2 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.
Transit and Railroad Police uses 37 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.
+25 more via usesTool
Transit and Railroad Police relies on 18 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.
+6 more via uses
The software Transit and Railroad Police 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.