How floral designers are reshaped as AGI capability advances.

About 35% of the work in Floral Designers is information-shaped and increasingly AI-deliverable, with the rest a hybrid of judgment and hands-on work. The automation frontier runs straight through the middle of this role.
Why: The UNSPSC tool distribution heavily features segment 43 (19 software tools like POS, inventory, and accounting systems), reflecting the retail management aspect of the occupation. However, core work activities and contexts highlight essential physical craftsmanship, notably 'Spend Time Using Your Hands to Handle, Control, or Feel Objects' (4.53), 'Spend Time Standing' (4.20), and 'Handling and Moving Objects' (3.41). This blend of digital retail administration and physical creation places the role in the lower-hybrid band.
grounded in the economy graph · digital scalar 0.35 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Floral Designers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Floral Designers 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.
Floral Designers performs 15 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+3 more via performs
Floral Designers is typically employed by 47 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+35 more via typicallyEmploys
Floral Designers is employed across 45 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+33 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Floral Designers uses 29 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.
+17 more via usesTool
Floral Designers relies on 17 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.
+5 more via uses
The software Floral Designers 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.
+2 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.