4. IROA Service and Product System

IROA product system connecting a tablet request to protected AI planning, verified execution, human support, and proof of completion

IROA is a product family that shares request state, identity, consent, and accessibility policy. Users choose the access point suited to the moment without losing request continuity.

Component	User-facing role	Core responsibility
IROA AI Assistant	Request work and check progress conversationally	Planning, tool choice, risk, outcome verification
IROA Mobile	Rich personal settings, approval, and results	Local credentials, profile, biometric approval
IROA Watch	Nearby request, confirmation, and alert	Haptic or voice approval, daily signals, kiosk link
Secure Execution Space	Continue long tasks after a device turns off	Isolation, one-time authority, result and deletion receipts
IROA Kiosk	Complete ordering, booking, and payment on site	Adaptive flow, exception handling, staff handoff
IROA Companion	Conversation, routines, check-ins, and connection	User-defined memory, retry, relationship connection
IROA Robot	Remote presence and bounded physical help	Local safety, stop controls, staged validation
IROA Support Network	Link institutions, stores, helpers, and Nodes	Trust levels, quality, settlement, disputes, audit

4.1 Daily-request AI assistant

The assistant converts a spoken request into a plan containing goals, constraints, services, and approval points. Supported categories may include bookings, accessible transport, ordering, store payment assistance, welfare preparation, hospital visit preparation, routines, helper calls, and cancellation or refund support.

4.2 Personalized accessibility assistant

Settings reflect actual preference and ability: text size and density, speech speed and repetition, touch area and switch input, captions and vibration, sign or pictorial explanation, number of choices, plain language, fatigue-aware simplification, and helper permissions. The user device is the default store; external environments receive minimum temporary settings.

4.3 Human-help network

People participate when a call or field judgment is needed, legal representation is required, or the user chooses not to automate. Roles and information access are granular. Identity and role are verified, and every performed request leaves a reviewable record.

4.4 Companion and check-in assistant

Users set when it may initiate, retry limits, avoided topics, allowed memory, and whom to contact. It supports conversation, chosen routines, scheduled human connection, staged non-response checks, immediate stop and deletion, and explicitly prohibits diagnosis or prediction of unattended death.

4.5 Proof of outcome

IROA distinguishes understanding, search, selection, submission attempt, service receipt, payment approval, final confirmation, and completed cancellation or refund. Where possible, it verifies official API responses, booking identifiers, payment approval, and official notifications.

4.6 Service catalog and responsibility

Each service card states supported country, official integration or screen execution, required identity, confirmation points, expected time and cost, cancellation, human handoff, and retention. Unsupported work is labeled unsupported, under review, or human help available—never disguised as a result.