2. A Day with IROA

2.0 Say it once, continue anywhere

After saying “Book my hospital visit,” the user should not have to watch a screen. A request may start on the phone, continue with a schedule choice on a watch, run through web booking in a secure execution space, be read back by a companion device, and transfer to a welfare worker when an exception appears. Each access point receives only the data and authority needed for its current step.

Stage	User experience	System responsibility
Request	Express the outcome by voice, text, touch, or switch	Reconfirm intent and constraints
Plan	Hear the work, expected time, and cost in plain language	Prefer official tools and classify risk and authority
Choose	Select among candidates or ask for a person	Do not hide or over-restrict choices
Approve	Separately confirm payment, submission, or sensitive transfer	Issue one-time task authority
Execute	Approved work can continue after the device is turned off	Manage isolation, state, and retry
Verify	Receive booking number, receipt, or official result	Verify the external outcome, not a screen change
Recover	Cancel, refund, retry, or connect to a person	Prevent duplicate action and hand off responsibly

2.1 Rehabilitation hospital booking and mobility

A user says, “Book rehabilitation next Tuesday morning and arrange an accessible taxi.” IROA confirms intent, loads only approved preferences, prefers the hospital’s official integration, and otherwise uses an isolated per-request browser. It explains schedule and cost choices, submits only after final approval, coordinates transport, and reports through the user’s chosen channel. Login problems, ambiguous questions, or failed booking trigger a bounded handoff to an approved person.

2.2 Kiosk ordering and payment

A user with hearing and motor impairments starts a session through watch or mobile QR/NFC. The kiosk temporarily applies accessibility preferences, explains suitable options in the right combination of text, image, sign-language video, or speech, and reconfirms item, quantity, price, discount, and refund terms. Payment credentials remain in the regulated payment provider’s approval flow. Personalization data and temporary tokens are deleted when the session ends.

2.3 Companion and staged check-in

The companion supports conversation and routines chosen by the user. A missed response is not immediately classified as danger. IROA retries across permitted channels, waits for the user-defined interval, then sends the minimum help request to selected family, neighbors, volunteers, or institutions. Emergency services are contacted only under a predefined emergency rule or clear immediate danger. The user can stop, change, or delete signals, timing, contact order, and conversation memory.

2.4 Welfare applications and long-running requests

Even without a smartphone or computer, a secure execution space can check current public information and compare only consented fields. It can continue within limited authority after a call ends and report through phone, watch, companion, or an approved helper. IROA distinguishes “possibly eligible,” “application accepted,” and “benefit approved.”

2.5 Booking by phone without a smartphone

The voice assistant explains minimum identity checks without requesting a full resident number, password, or OTP in conversation. If candidates are not immediately available, it calls back after secure execution completes. Final submission follows a clear read-back of time, place, and cost. Text relay, sign-language interpretation, and protected human handoff provide equivalent routes.

2.6 When execution fails

IROA explains where it stopped, clearly marks anything already sent or paid, and offers retry, another channel, or human help. A handoff carries the necessary summary and approved context—not the entire conversation. De-identified failure evidence may improve service and Node quality.