Local prototype · open protocol · adapter-ready

Robot Care Interface

Prefer the experiential view? Enter the Future Care Room

Idle
CorePreauthorized autonomy

Configured routines execute from caregiver-authored settings.

ExceptionPause or escalate

Only configured safety exceptions interrupt the routine.

RecordAudit trail

Every command and event is logged locally with a reason.

OpenPortable protocol

Generated JSON can later map to ROS2, MQTT, HTTP, or offline care tools.

AdapterIntegration-ready contract

Future devices attach by preserving commands, exceptions, and audit records.

Live care protocol

Observe, structure, run, record

This demo shows how a caregiver-authored routine can move from context to action: environment targets, personal space, visual support, pause rules, caregiver notice, and local audit.

Care roomIdle
Light71%
Sound63%
Distance0.8m

Person

Care interface

NowIdle

Choose a scenario or start the current routine.

01 · Routine builder

Care command protocol

Care scenarios

Allowed actions

Safety exceptions

02 · Protocol panel

Preauthorized routine

ScenarioEvening transition

Move from activity to rest with a predictable, low-stimulus routine.

Step 0 of 7

1
Lower lightpreauthorized routine step: light target
2
Reduce soundpreauthorized routine step: sound target
3
Step backpreauthorized routine step: distance target
4
Pause interactionpreauthorized routine step: quiet interval
5
Offer visual cardpreauthorized routine step: routine support
6
Notify caregiverpreauthorized completion notice
7
Log observationpreauthorized local record

03 · Protocol intelligence

Generate, validate, explain, export

The local planner turns the current routine settings into an ordered, timed care protocol with adapter packets for future devices. It runs entirely on this device: no external API, and the same settings always produce the same plan.

No protocol generated yet. Configure the routine above, then generate a plan.

04 · Audit trail

Local event log

lab_ready

protocol workspace initialized for future adapter work

system

05 · Protocol export

Generated JSON

{
  "name": "Evening transition",
  "scenario": "evening_transition",
  "care_goal": "Move from activity to rest with a predictable, low-stimulus routine.",
  "visual_card": "Now: quiet room. Next: sleep routine.",
  "autonomy_level": 2,
  "mode": "protocol_first",
  "duration_minutes": 20,
  "environment": {
    "light": 35,
    "sound": 25,
    "distance": 1.5,
    "pace": "slow"
  },
  "vision_context": {
    "source": "manual_context",
    "latest_local_snapshot": null
  },
  "allowed_commands": [
    "lower_light",
    "reduce_sound",
    "step_back",
    "pause_interaction",
    "offer_visual_card",
    "notify_caregiver",
    "log_observation"
  ],
  "safety_exceptions": [
    "rejection_signal",
    "caregiver_pause",
    "timeout",
    "unknown_event"
  ],
  "audit_policy": {
    "local_only": true,
    "records": [
      "timestamp",
      "actor",
      "command",
      "reason"
    ],
    "sensitive_personal_data": false
  },
  "open_integration": {
    "contract": "care_command_protocol_v0",
    "adapter_target": "ros2",
    "adapter_label": "ROS2 robot middleware",
    "transport_note": "publish command envelopes to a local ROS2 node",
    "adapter_must_preserve": [
      "caregiver-authored routine settings",
      "allowed command list",
      "safety exception list",
      "local audit trail"
    ]
  },
  "integration_adapter": {
    "stage": "contract_design",
    "readiness": "ready_for_local_adapter_work"
  }
}