Rehearse a shorter retention policy without deleting on preview
Product proposes reducing the exercise retention period from 30 to 14 days. Applying the constant immediately would make a large backlog eligible at once.
- Focused work estimate
- 5h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Change management · Retention policy
Estimated field mix
- Privacy engineering60%
- Site reliability40%
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 support service keeps uploaded diagnostic files indefinitely. The exercise policy expires attachments 30 days after case closure, while a separately authorized investigation hold pauses removal. These are invented product rules, not legal advice or compliance certification.
Setup prerequisites
- Create synthetic cases, attachment metadata and a fake object store with controllable failures.
- Use an injected UTC clock and an authorized operator fixture; no real support uploads are needed.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- RRETENTION-101 · Calculate attachment expiry from the case closure instant
- RRETENTION-102 · Inventory every storage location used by one support attachment
- RRETENTION-103 · Require scoped authority to place an attachment on investigation hold
- RRETENTION-104 · Preview the attachment purge set with stable decision reasons
- RRETENTION-105 · Recheck holds when a queued attachment purge begins
- RRETENTION-107 · Record a reopened case without silently resetting attachment history
Acceptance criteria
- Create a new policy version and produce a tenant-scoped impact preview.
- Define activation time, bounded purge batches and preserved hold semantics.
- Document that rollback can stop future deletion but cannot restore confirmed removed objects.
Implementation constraints
- Treat 14 days as a proposed fictional rule requiring review in the exercise workflow, not a real-world policy recommendation.
Verification to include
- Compare old and new decisions at activation boundaries with active holds.
- Cancel activation and verify no objects were removed by the preview; rehearse stopping after one controlled purge batch.
Deliverables
- Policy-change plan, impact report and stop procedure
Rollout and recovery
Require the explicit local activation command after review; retain previous policy and append the activation record.
Value of the work
For the engineer: Practice temporal policy, deletion races, exception authority and truthful recovery reporting.
For the team: Develop inspectable retention behavior that a company can review against its own approved data 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.