
Only about 5% of Fallers 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: Despite the presence of some software tools (segment 43) for mapping and tracking, the core of this role is overwhelmingly physical. Top work activities are heavily manual, including Performing General Physical Activities (4.34) and Controlling Machines and Processes (4.33). The work context confirms a rugged, outdoor environment, scoring extremely high for Outdoors, Exposed to All Weather Conditions (4.94), Exposed to Hazardous Equipment (4.88), and Wearing Common Protective Equipment (4.97).
grounded in the economy graph · digital scalar 0.05 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Fallers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Fallers 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.
Fallers 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
Fallers is typically employed by 18 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+6 more via typicallyEmploys
Fallers is employed across 7 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.
Fallers uses 64 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.
+52 more via usesTool
Fallers relies on 17 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.
+5 more via uses
The software Fallers 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.