---
id: OV-C8-POS-007
title: "Deliberate Mode Luring exit requires manual toggle (intentional friction)"
product: mobile
module: offline-visitation
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C8
  tsdScenario: C8.7
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C8.7 (exit path); pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-mode-luring-active
tags:
  - mobile
  - offline-visitation
  - mode-luring
  - pk144
  - staging
---
## Objective
Verify the deliberate exit flow from Mode Luring and the patchy-network re-fire edge case.

## Preconditions
- See [[PRE-OV-mode-luring-active]]
- And no visitation is in "Dalam Proses"

## Steps
1. Tap "Matikan" on the banner
2. Manually toggle Mode Luring OFF, then re-establish network
3. Edge: on patchy network, access a visitation without a bundle

## Expected Result
- Then tapping "Matikan" navigates to Account → Mode Luring (NOT a one-tap exit — intentional friction)
- And the employee must manually toggle Mode Luring OFF, then re-establish network connection
- And in the patchy-network edge case the "Koneksi Tidak Stabil" drawer re-fires and the employee is prompted to save data locally

## Source Traceability
- TSD: PK144
- Section: C8 - Mode Luring State Management
- Scenario: C8.7 - Deliberate exit flow
- Acceptance Criteria: E6.US-7 AC1–AC4

## Evidence Required
- Screen recording of the multi-step exit and the edge-case drawer re-fire.

## Notes / Gaps
- Blocked-exit-when-Dalam-Proses is covered by OV-C8-NEG-008 (cross-ref C2.9).