How judicial law clerks are reshaped as AGI capability advances.

Roughly 85% of the work in Judicial Law Clerks 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 recorded tools fall into UNSPSC segment 43 (IT/Software), yielding a strong digital prior. This aligns perfectly with top work activities centered entirely on knowledge work—Getting Information (4.85), Analyzing Data (4.56), Processing Information (4.01), and Working with Computers (3.94). The work context further solidifies this as a remote-capable desk role, dominated by 'Indoors, Environmentally Controlled' (4.91), 'E-Mail' (4.87), and 'Spend Time Sitting' (4.54).
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 Judicial Law Clerks engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Judicial Law Clerks 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.
Judicial Law Clerks 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
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Judicial Law Clerks 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.
Judicial Law Clerks relies on 39 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.
+27 more via uses
The software Judicial Law Clerks 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.