Remove one downloaded course without breaking shared assets
Deleting a course removes an image another course references. Track local references before reclaiming shared blobs.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reference counting · Storage
Estimated field mix
- Storage systems70%
- Mobile30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional learning app Birch offers synthetic text and small local media fixtures through a loopback adapter. No copyrighted course assets or network accounts are needed.
Setup prerequisites
- Create small local byte fixtures and a range-response stub.
- Simulate low storage, interruptions and stale manifests.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CDOWN-102 · Keep mobile download buttons consistent with durable state
- CDOWN-101 · Distinguish unknown course-download sizes from zero bytes
- CDOWN-103 · Validate course manifest paths before creating files
- CDOWN-104 · Resume a mobile course transfer only with matching content identity
- CDOWN-105 · Verify downloaded course bytes before exposing Open
- CDOWN-106 · Pause mobile transfers when storage reservation fails
- CDOWN-107 · Recover a course-download rename interrupted by process death
Acceptance criteria
- Unreferenced blobs are reclaimed
- Referenced blobs remain
- Failed cleanup is retryable
Implementation constraints
- Keep references scoped to verified manifests.
Verification to include
- Delete unique course
- Delete course with shared asset
Deliverables
- Reference-aware cleanup
Rollout and recovery
Disable physical reclamation while fixing reference accounting.
Value of the work
For the engineer: Practice mobile file lifecycles and background state recovery.
For the team: Inspect predictable resource usage and truthful download status.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.