How slaughterers and meat packers are reshaped as AGI capability advances.

Only about 5% of Slaughterers and Meat Packers 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 role is intensely physical, evidenced by top Work Context attributes like wearing common protective equipment (4.84), spending time using hands to handle objects (4.66), and standing (4.34). Top Work Activities such as handling and moving objects (3.72) and performing general physical activities (3.56) strongly push the scalar down. While workers use some Segment 43 software tools for inventory and traceability, the core value-producing work relies on Segment 23 and 21 industrial machinery (cubing and dehairing machines) and manual labor.
grounded in the economy graph · digital scalar 0.05 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Slaughterers and Meat Packers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Slaughterers and Meat Packers 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.
Slaughterers and Meat Packers performs 14 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+2 more via performs
Slaughterers and Meat Packers is typically employed by 16 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+4 more via typicallyEmploys
Slaughterers and Meat Packers is employed across 13 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+1 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Slaughterers and Meat Packers uses 34 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.
+22 more via usesTool
Slaughterers and Meat Packers relies on 12 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 Slaughterers and Meat Packers 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.
No articles yet for this entity.
No capability events for this entity yet.