---
id: OV-C9-POS-001
title: "Persona is backend-sourced, single-value, and never inferred on mobile"
product: mobile
module: offline-visitation
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C9
  tsdScenario: C9.1
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C9.1; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-logged-in-online
tags:
  - mobile
  - offline-visitation
  - pjp
  - pk144
  - staging
---
## Objective
Verify persona is determined by backend configuration, persisted per session, and treated as a single value.

## Preconditions
- See [[PRE-OV-logged-in-online]]

## Steps
1. Inspect persona resolution at login and across offline operations

## Expected Result
- Then persona (PJP or Non-PJP) is determined by account config and backend journey-plan assignment, never inferred or overridden on mobile
- And it is fetched at login, persisted for the session, and refreshed on subsequent logins / server-side config changes
- And offline routing uses the most recently fetched persona, and offline operations are NOT blocked by stale persona data
- And persona is single-value (exactly one persona at any moment; no hybrid or per-channel persona)
- And persona is NOT displayed as a UI label — reflected through behavior only

## Source Traceability
- TSD: PK144
- Section: C9 - Multi-device Race Conditions, Persona & Target Rules
- Scenario: C9.1 - Persona identification (source of truth)
- Acceptance Criteria: E2.US-1 AC1–AC6

## Evidence Required
- Persona value source trace at login and offline.

## Notes / Gaps
- Testing Concern #34 (Critical): persona change mid-session (BE update). #35 (Critical): hybrid persona open (cross-ref C1 #4).