How notary public are reshaped as AGI capability advances.

Roughly 85% of the work in Notary Public 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: With no established digital prior for the parent occupation ('Office and Administrative Support Workers, All Other') and no known children to roll up, this score is based on the job type name and department context. As a 'Notary Public' working in escrow, legal administration, and corporate compliance, the core value-producing work consists of desk-bound document verification, identity checking, and administrative recording, making it a distinctly information-based, digital role. It is assigned a band-center digital scalar.
grounded in the economy graph · digital scalar 0.85 · digital
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Notary Public is staffed by 3 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.
Notary Public 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 Notary Public 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.
+3 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.