How bridge and lock tenders are reshaped as AGI capability advances.

About 40% of the work in Bridge and Lock Tenders 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 role blends physical equipment operation with administrative tracking. While the top work activity is 'Controlling Machines and Processes' (4.11) supported by physical tools in segments 46, 27, and 41, the work is heavily coordinated via IT tools (10 tools in segment 43). High scores in 'Indoors, Environmentally Controlled' (4.47), 'Telephone Conversations' (4.32), and 'Documenting/Recording Information' (3.89) place this firmly in the hybrid band.
grounded in the economy graph · digital scalar 0.40 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Bridge and Lock Tenders engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Bridge and Lock Tenders 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.
Bridge and Lock Tenders performs 18 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+6 more via performs
Bridge and Lock Tenders is employed across 4 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.
Bridge and Lock Tenders uses 50 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.
+38 more via usesTool
Bridge and Lock Tenders 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 Bridge and Lock Tenders 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.