Cooks, Institution and Cafeteria
How cooks, institution and cafeteria are reshaped as AGI capability advances.
The bottom line
Only about 15% of Cooks, Institution and Cafeteria 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 work context strongly signals physical labor, marked by 'Spend Time Standing' (score 4.72), 'Using Your Hands to Handle... Objects' (4.29), and 'Exposed to Minor Burns, Cuts' (4.23). While tools include administrative software (10 tools in segment 43), the role relies primarily on physical kitchen equipment (13 tools in segment 48). Activities like 'Inspecting Equipment, Structures, or Materials' (3.85) confirm the core value-producing work is heavily hands-on, placing this firmly in the physical band.
grounded in the economy graph · digital scalar 0.15 · physical
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Cooks, Institution and Cafeteria engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Cooks, Institution and Cafeteria involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Autonomous Agents as digital employees
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Cooks, Institution and Cafeteria performs 17 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+5 more via performs
Cooks, Institution and Cafeteria is typically employed by 207 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+195 more via typicallyEmploys
Cooks, Institution and Cafeteria is employed across 117 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+105 more via employs
Headless SaaS for Agents
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Cooks, Institution and Cafeteria uses 77 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.
+65 more via usesTool
Cooks, Institution and Cafeteria relies on 13 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.
+1 more via uses
The software Cooks, Institution and Cafeteria 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.
The problems this exposes
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
- Allergen Cross-Contamination
- Batch Cooking Consistency
- Batch Recipe Scaling
- Bulk Ingredient Spoilage
- Bulk Inventory Spoilage
- Commercial Equipment Downtime
- Food Waste Management
- High Kitchen Turnover
- Kitchen Staff Retention
- Meal Participation Rates
+3 more problems on the graph
Where Cooks, Institution and Cafeteria sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
Problems
- Food Waste Managementsupply-chain
- Kitchen Staff Retentiontalent
- Nutritional Guideline Adherencecompliance
- Batch Cooking Consistencyops
- Meal Participation Ratesdemand-gen
- Commercial Equipment Downtimecapital
- Bulk Inventory Spoilagesupply-chain
Opportunities
- Menu Compliance AutomationService-as-Software
- Dynamic Recipe ScalingAgent
- Waste Analytics EngineHeadless SaaS
- Predictive Maintenance DispatchAgent
- Spoilage Prevention RoutingHeadless SaaS