---
id: OV-C9-POS-002
title: "Persona drives filtering, download scope, and sync rejection rules"
product: mobile
module: offline-visitation
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C9
  tsdScenario: C9.2
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C9.2; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-logged-in-online
tags:
  - mobile
  - offline-visitation
  - pjp
  - sync
  - pk144
  - staging
---
## Objective
Verify persona value consistently drives downstream behavior across connectivity states.

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

## Steps
1. Observe channel filtering, download scope, and sync rejection rules for each persona across S1/S2/S3

## Expected Result
- Then persona is used for channel list filtering & badge display (Dijadwalkan PJP only), download scope (per channel reusable / per visitation single-use), and sync rejection rules (multi-device race)
- And behavior is preserved across S1/S2/S3
- And active connectivity affects data sourcing & submission but does NOT change persona behavior

## Source Traceability
- TSD: PK144
- Section: C9 - Persona & Target Rules
- Scenario: C9.2 - Persona-driven downstream routing
- Acceptance Criteria: E2.US-3 AC1–AC5

## Evidence Required
- Behavior matrix per persona across connectivity states.

## Notes / Gaps
- No gap.