---
id: OV-C1-POS-020
title: "Bundle auto-purges after 3×24h with no dependents"
product: mobile
module: offline-visitation
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK144
  tsdSection: C1
  tsdScenario: C1.12
  prd: PK144
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK144 TSD C1.12 (auto-purge branch); pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-OV-logged-in-online
tags:
  - mobile
  - offline-visitation
  - download-center
  - pk144
  - staging
---
## Objective
Verify automatic purge of an unused bundle after the 3×24h retention window.

## Preconditions
- See [[PRE-OV-logged-in-online]]
- And a downloaded bundle exists
- And no related visitation is "Dalam Proses"
- And no Perlu Dikirim queue item depends on it

## Steps
1. When 3×24 hours elapse since check-out (or last activity)

## Expected Result
- Then the bundle is auto-purged from local storage
- And the cloud-icon timestamp disappears without a page refresh
- And no notification is shown

## Source Traceability
- TSD: PK144
- Section: C1 - Bundle Lifecycle
- Scenario: C1.12 - Retention & auto-purge (3×24h)
- Acceptance Criteria: M.10 AC2, AC3, AC4

## Evidence Required
- Instrumented clock/retention evidence showing purge after the window.

## Notes / Gaps
- Testing Concern #9 (Critical): retention timer start (check-out vs no-dependent) is undefined — the exact window start is a gap; assert relative elapse, flag the trigger choice.
- Cache-clear/uninstall counterpart is OV-C1-EDGE-021.