Expire export artifacts and incomplete assembly objects separately
Completed exports expire after a day, but failed assembly objects remain indefinitely under a different prefix.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Retention · Resource ownership
Estimated field mix
- Privacy engineering50%
- Storage systems30%
- Site reliability20%
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
A fictional learning workspace offers a member a portable copy of their own profile, notes and activity settings. Shared documents contain contributions from other people. The product export policy specifies included fields and shared-record handling; this is an engineering exercise, not a legal portability claim.
Setup prerequisites
- Create synthetic members, private notes and shared-document contributions in a local database.
- Provide fake queue and object-storage adapters with controllable expiry and failure.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- REXPORT-101 · List exportable member fields before serializing database rows
- REXPORT-102 · Define how shared document contributions appear in a personal export
- REXPORT-103 · Bind export creation to the current authorized subject
- REXPORT-104 · Freeze the export selection without holding a long database transaction
- REXPORT-105 · Stream large note exports with bounded intermediate storage
- REXPORT-106 · Validate the export manifest before marking assembly complete
- REXPORT-107 · Issue a short-lived download capability only after subject authorization
Acceptance criteria
- Define bounded lifetimes for ready, failed and abandoned temporary artifacts.
- Recheck active assembly ownership before removing a temporary object.
- Confirm object removal separately from expired download access.
Implementation constraints
- Use an injected clock and per-operation object registry; prefix age alone cannot distinguish an active write.
Verification to include
- Advance time through each lifecycle and verify correct removal eligibility.
- Race cleanup with an active assembly lease and verify either safe retention or the declared cancellation path.
Deliverables
- Artifact cleanup policy and lifecycle race tests
Rollout and recovery
Run a scoped preview before local cleanup; retain unresolved storage outcomes for reconciliation.
Value of the work
For the engineer: Practice export scoping, consistency, streaming and expiring access without leaking other members’ data.
For the team: Create a reviewable export contract and cross-subject regression suite for an approved product policy.
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.