
About 50% of the work in Spa Director 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: With no known child scalars, this value is anchored on the parent occupation 'First-Line Supervisors of Personal Service Workers' and the 'Spa Director' job type. The role mixes significant administrative knowledge work ('Working with Computers' at 4.14 importance) with on-site, in-person supervision of a physical facility and hands-on service staff, making it a clear hybrid role.
grounded in the economy graph · digital scalar 0.50 · hybrid
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Spa Director is staffed by 2 sources of labor — the supply that an agent workforce reshapes from headcount to earned-autonomy configuration.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Spa Director relies on 8 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 Spa Director reaches for already exposes 8 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.
+4 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.