Resident Missed Morning Routine, Day 2.
Pattern, not event. The duty carer is told before lunch, with context, not an alarm.
Care is the hardest Physical AI domain because the failure mode is not throughput — it is liability, family trust, and a person who didn’t consent to being a test subject. The runtime enforces escalation discipline as a system, not a fallback.
A resident’s day is built from small rituals, small medications, small interactions — and small deviations that matter clinically. A robot that does not understand the person, the schedule, and the safe boundary of its own role is dangerous.
Care robotics fails when it tries to act in ambiguity. The runtime treats escalation as a first move, not a last one — with the right person, the right context, and the right timing.
Pattern, not event. The duty carer is told before lunch, with context, not an alarm.
Memory of the night carries to the incoming carer. Six hours of context, not a clipboard.
Not yet a fall. The runtime escalates with a structured summary, not a generic alert.
Every interaction logged with reason, override, and outcome. Available to family, clinician, regulator. Without this, there is no programme.
“The family lost trust after one ambiguous alert. We pulled the robot out of that room. That was the programme for them.”Care directorCare home · NL
“Carers won’t hand off to something that can’t tell them what happened during the last six hours of the shift.”Head nurseGeriatric ward · DE
A resident skips morning routine for the second day. Speech is slower. Movement is less confident. No alarm has fired — but the baseline has shifted.
Persistent memory of the individual — routine, preferences, medication, baseline behaviour.
Patient turn-taking, careful proximity, calm language. The robot reads the moment.
Auditable behaviour, deterministic safety boundaries, evidence trail for every decision.
Knowing when to stop and call a human is a feature, not a fallback.
Elderly care · Outcome
A robot that earns the right to be in the room.