
Only about 10% of Barbers 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: Work Context strongly highlights physical attributes like Spend Time Using Your Hands to Handle Objects (4.92), Physical Proximity (4.79), and Spend Time Standing (4.62). Work Activities emphasize Working Directly with the Public (4.67) and Performing General Physical Activities (3.85). While they use some segment 43 software for scheduling and point-of-sale, the core value-producing work relies completely on manual handling of physical tools, placing this firmly in the physical band.
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 Barbers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Barbers 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.
Barbers 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
Barbers is employed across 9 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.
Barbers uses 25 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.
+13 more via usesTool
Barbers relies on 11 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 Barbers 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.