
Roughly 80% of the work in Curators is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: All 30 tools used by Curators fall into UNSPSC segment 43 (IT/software), setting a strong digital baseline (prior=0.85). This is reinforced by top work activities focused on knowledge work, such as 'Documenting/Recording Information' (4.50), 'Getting Information' (4.44), and 'Working with Computers' (3.99). Additionally, the top work contexts like 'E-Mail' (4.73), 'Telephone Conversations' (4.64), and 'Indoors, Environmentally Controlled' (4.47) confirm a primarily desk-based, information-centric environment, placing this role securely in the digital band.
grounded in the economy graph · digital scalar 0.80 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Curators engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Curators 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.
Curators performs 15 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+3 more via performs
Curators is typically employed by 13 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+1 more via typicallyEmploys
Curators is employed across 31 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+19 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Curators uses 19 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.
+7 more via usesTool
Curators relies on 48 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.
+36 more via uses
The software Curators 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.