
About 35% of the work in Actors 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: Despite a toolset dominated by IT and communication software (23 tools in segment 43) and frequent E-Mail use (context score 4.68), the core value-producing work is heavily physical and in-person. High O*NET importance for Performing General Physical Activities (4.02), Performing for the Public (4.16), and Physical Proximity (4.80) firmly places this role in the lower-hybrid band.
grounded in the economy graph · digital scalar 0.35 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Actors engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Actors 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.
Actors 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
Actors is typically employed by 10 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
Actors is employed across 28 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+16 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Actors uses 8 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.
Actors relies on 24 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.
+12 more via uses
The software Actors 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.