How brickmasons, blockmasons, and stonemasons are reshaped as AGI capability advances.

Only about 5% of Brickmasons, Blockmasons, and Stonemasons is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: The grounding data lacks specific tool or work context metrics, but provides a deterministic SOC code prior of 0.00. Guided by the occupation title and this exact prior, the value-producing work of laying brick and stone is entirely hands-on construction, placing this firmly in the physical band.
grounded in the economy graph · digital scalar 0.05 · physical
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Brickmasons, Blockmasons, and Stonemasons is typically employed by 85 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+73 more via typicallyEmploys
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Brickmasons, Blockmasons, and Stonemasons relies on 4 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 Brickmasons, Blockmasons, and Stonemasons 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.
+1 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.