
Only about 15% of Cashiers 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: With no specific tool, activity, or context data available in the grounding block, I rely on the occupation name and the provided deterministic SOC code prior of 0.05. Cashiers perform hands-on, location-bound transactional work, securely placing the role in the physical band with a band-center scalar.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Cashiers 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.
Cashiers is typically employed by 301 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+289 more via typicallyEmploys
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Cashiers relies on 7 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.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
+2 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.