
Only about 10% of Dancers 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 using software tools for choreography and promotion (14 tools in segment 43), the value-producing work is entirely bodily. Top work activities are dominated by 'Performing General Physical Activities' (4.51) and 'Performing for or Working Directly with the Public' (3.95). Furthermore, work context attributes like 'Physical Proximity' (4.91), 'Spend Time Bending or Twisting Your Body' (4.55), and 'Keeping or Regaining Balance' (4.25) confirm the work is intensely physical.
grounded in the economy graph · digital scalar 0.10 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Dancers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Dancers 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.
Dancers performs 14 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+2 more via performs
Dancers is typically employed by 20 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+8 more via typicallyEmploys
Dancers is employed across 24 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+12 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Dancers uses 26 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.
+14 more via usesTool
Dancers relies on 16 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.
+4 more via uses
The software Dancers 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.