Draft article · 6 min read
A realistic readiness scale for physical AI in food service
A useful readiness scale structures evidence and uncertainty. It should not imply that capability is universal or that a timeline is guaranteed.
Draft for review. A readiness level is a planning aid, not an independent certification or vendor rating.
Score a task in a defined setting
“Kitchen work” is too broad to evaluate. Define a specific task, such as moving a standard tray from a known staging point to a dish-return area during a quiet period. State the equipment, route, load, expected quality and conditions where the assessment applies.
Separate technical evidence from operations
Technical evidence asks whether a system can perform the action, detect failure and recover safely. Operational evidence asks whether the task fits hygiene, service pace, staff routines, cleaning, maintenance and cost. A convincing demonstration may provide technical evidence without answering the operational questions.
Example levels (illustrative framework)
- Level 1 — research only: the underlying capability is being explored; key elements are not yet demonstrated for the task.
- Level 2 — component demonstration: selected actions work in controlled conditions; integration and exception handling remain open.
- Level 3 — task demonstration: the task has been shown in a relevant test setting, but not established as reliable in day-to-day service.
- Level 4 — operationally validated: performance and recovery are measured in the target context with defined human oversight.
- Level 5 — commercially proven: credible evidence exists across comparable operations for reliability, safety, support and total cost.
These descriptions need to be adapted to the customer’s task, evidence and risk appetite; a level alone does not establish suitability.
Make the next test explicit
For every rating, record supporting evidence, unknowns, assumptions and a bounded next test. For food service, that might include wet floors, hot equipment, changing loads, cross-traffic, sanitation or peak-time pressure. A “not ready” answer can save time and protect staff.
Avoid false precision in timelines
Technology readiness does not translate directly into a calendar date. A product may exist but still require local integration, approvals, training and support. If a time horizon is presented, label it as a conditional estimate and explain its source and uncertainty.