Design with the person using it
Select a concrete journey: entering, requesting an action or receiving a notification. Agree on interaction methods and device permissions. Users should recognise what the system understood and how it responded. Adaptation follows experience rather than an externally imposed profile.
What the system contributes
Argos receives authorized signals, maintains environment state, detects relevant change and applies defined protocols. When evidence is missing or an action exceeds permissions, it escalates the decision.
The manual alternative must also be accessible
Connection or interpretation failure must not leave someone without a way forward. Alternatives are prepared and tested with the user. A demonstration may not work in the actual space, so light, sound, placement and devices belong in acceptance testing.
The same signal does not work for everyone
An audible alert may not help one person; a small screen may hinder another. Deployment reviews presentation and suitable devices. Disability is not inferred from observation: preferences and needs are defined with the person and responsible supporters where appropriate.
Evaluate independence through real situations
Trials examine whether a person can complete the journey, understand alerts and regain control. Errors, repeated requests and device failures are included. Usefulness is assessed with the user, without promising one system can resolve every need.