Validate backup retention changes against declared recovery policy
A retention reduction removes the recovery window the application team relies on.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Recovery policy
Estimated field mix
- Site reliability60%
- Cloud infrastructure40%
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 application team manages a small database, cache, and object store. Reviewers struggle to distinguish harmless configuration changes from destructive replacements.
Setup prerequisites
- Author synthetic infrastructure plans and state snapshots; use local files only and no cloud credentials.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Compare proposed retention with the scenario requirement.
- Account for deletion of old backup generations.
- Require an explanation for incompatible changes.
Implementation constraints
- Policy requirements are explicit inputs.
Verification to include
- Accept a compatible retention update.
- Flag a shorter recovery window and missing policy.
Deliverables
- Retention plan rule.
Rollout and recovery
Review changes alongside the restore rehearsal record.
Value of the work
For the engineer: Practice infrastructure risk analysis, plan integrity, and least-privilege change workflows.
For the team: Give infrastructure reviewers concrete change scope and recovery consequences.
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.