Explosives Workers, Ordnance Handling Experts, and Blasters

The work of Explosives Workers, Ordnance Handling Experts, and Blasters engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.

+29 more via engagesIn

Explosives Workers, Ordnance Handling Experts, and Blasters involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.

+29 more via involvesActivity

Explosives Workers, Ordnance Handling Experts, and Blasters performs 23 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.

+11 more via performs

Explosives Workers, Ordnance Handling Experts, and Blasters is typically employed by 28 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.

+16 more via typicallyEmploys

Explosives Workers, Ordnance Handling Experts, and Blasters is employed across 31 settings — the places where this role's work is done, and where digital employees first sit beside the humans.

+19 more via employs

Explosives Workers, Ordnance Handling Experts, and Blasters uses 160 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.

+148 more via usesTool

Explosives Workers, Ordnance Handling Experts, and Blasters relies on 15 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.

+3 more via uses

The software Explosives Workers, Ordnance Handling Experts, and Blasters 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.