
Roughly 85% of the work in Archivists 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 listed for Archivists fall into UNSPSC segment 43 (IT/software), including Archivists' Toolkit and Adobe Creative Cloud, carrying a high digital prior of 0.85. The strongest work activities are entirely information-centric, led by 'Documenting/Recording Information' (4.74) and 'Working with Computers' (4.52). The work context confirms a desk-knowledge surface dominated by 'E-Mail' (4.97) and 'Spend Time Sitting' (4.03), placing this occupation firmly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Archivists engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Archivists 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.
Archivists performs 13 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+1 more via performs
Archivists is typically employed by 28 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+16 more via typicallyEmploys
Archivists is employed across 47 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+35 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Archivists uses 7 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.
Archivists relies on 36 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.
+24 more via uses
The software Archivists 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.