Robocare v02
Community care marketplace. Needs assessment drives scope, scope drives matching, and credentials are re-verified at booking rather than once at signup.
- Role in stack
- Service workflow -> verified fulfilment
- Current state
- Working product
- Best demo use
- Marketplace/workflow pattern reference, kept separate from the agentic-AI pitch
- Honest boundary
- Pre-launch; no measured usage or outcome data exists yet
Seven stages of one care request: intake with requester and care recipient held separate, structured needs assessment, scope-constrained caregiver matching, credential and KYC re-verification, an itemised quote separating caregiver earnings from platform fee, a family confirmation gate, and the issued care plan. Completing the run opens a caregiver directory filterable by type, area, and skill.
The demo is a static mock. It runs entirely in your browser on synthetic data — nothing is gated, nothing is collected.