How judges, magistrate judges, and magistrates are reshaped as AGI capability advances.

Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Judges, Magistrate Judges, and Magistrates engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Judges, Magistrate Judges, and Magistrates 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.
Judges, Magistrate Judges, and Magistrates performs 21 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+9 more via performs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Judges, Magistrate Judges, and Magistrates uses 13 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.
+1 more via usesTool
Judges, Magistrate Judges, and Magistrates relies on 21 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.
+9 more via uses
The software Judges, Magistrate Judges, and Magistrates 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.