diff --git a/product/business/01-actors-and-onboarding.html b/product/business/01-actors-and-onboarding.html
index 0e804c3..59153e7 100644
--- a/product/business/01-actors-and-onboarding.html
+++ b/product/business/01-actors-and-onboarding.html
@@ -30,6 +30,7 @@
 </li>
 <li>Each successful login creates a refresh-token session that can be revoked (logout, stolen-token detection).</li>
 <li><strong>As-built decisions (backend-phase-2):</strong> each refresh <strong>rotates</strong> the session (old revoked, new pair issued); a refresh token presented against an already-revoked session is treated as <strong>stolen-token reuse → all of the user's sessions are revoked and the call returns 401</strong>. Logout rotates the security stamp, so every outstanding access token dies (other devices recover by refreshing). OTP request/verify never reveal whether a phone already has an account; one OTP per phone per resend window (<code>auth_otp_resend_seconds</code>), and after <code>auth_otp_max_attempts</code> wrong codes verification refuses until a fresh OTP. <code>customer</code>/<code>nurse</code> are the only self-selectable roles (a user may hold both; grants audited via <code>granted_by</code>/<code>granted_at</code>); any admin sub-role self-assign attempt returns <strong>403</strong> — admin provisioning is internal-only.</li>
+<li><strong>As-built decisions (frontend-phase-2 — onboarding UI):</strong> the "who is care for?" onboarding step captures the patient's <strong>relation to the payer</strong> as a stable enum — <code>parent</code> | <code>spouse</code> | <code>child</code> | <code>self</code> (the <code>self</code> case still creates a distinct patient row; the customer is never collapsed into the patient). It also collects optional <strong>condition</strong> chips (<code>elderly</code>/<code>post_surgery</code>/<code>diabetes</code>/<code>mobility</code>/<code>dementia</code>). Neither <code>relation</code> nor <code>conditions</code> exists on the <code>patients</code> table yet — they are carried client-side and requested for the backend as <strong>REQ-005</strong> (frontend <code>requests/for-backend.md</code>); confirm/adjust the enum values when persisting.</li>
 </ul>
 <h2 id="b-iran-specific-considerations">(b) Iran-specific considerations <a class="anchor" href="#b-iran-specific-considerations" aria-hidden="true">#</a></h2>
 <ul>