1. Actors & Onboarding

(a) Business requirements

Three actor types: customer (the family member / payer), nurse (the independent caregiver / seller), and admin (Balinyaar back-office staff: support, finance, moderation, super-admin).
Phone number is the primary login credential. Authentication is phone-OTP (one-time code by SMS). Email is optional/secondary (required only for admin accounts).
The patient (care recipient) is a first-class entity distinct from the customer, because the payer (an adult child, a spouse) is frequently not the patient (an elderly parent, a newborn, a post-surgical adult). A customer may register multiple patients.
KYC timing is role- and risk-staged, not up-front-for-everyone:
- A customer can register and browse with only a verified phone (OTP). National-ID KYC for customers is anti-fraud only and is deferred at launch.
- A nurse must complete the full verification pipeline (Section 2) before any of their service variants become bookable. national_id is populated only after the identity step passes.
- An admin is provisioned internally with RBAC roles.
Each successful login creates a refresh-token session that can be revoked (logout, stolen-token detection).

Phone-OTP is the dominant Iranian login norm and is also the anchor for Shahkar SIM↔national-ID binding (Section 2).
Storing national_id only post-KYC matches the reality that identity is verified through gated vendor APIs, not collected casually at signup.
Cultural reality: the booking flow must let a family member act on behalf of a patient who cannot self-advocate (infant, dementia, post-anesthesia). The customer/patient split is essential, not cosmetic.

MVP: phone-OTP login; customer/nurse/admin roles; customer→patient (1:N); session management; admin RBAC; nurse onboarding gated on verification.
DEFERRED: customer national-ID KYC (customer_profiles.national_id_verified_at exists but is optional/unused at launch); push notifications; social login; nursing-company (organization) self-onboarding.

users, user_sessions, roles, user_roles, nurse_profiles, customer_profiles, patients, customer_addresses.

Related: Data model — Identity & Access.