Write a stale-preview support checklist
Reviewers need to know whether a broken preview is creating, expired, or awaiting cleanup.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Operational UX
Estimated field mix
- Frontend40%
- Cloud infrastructure30%
- Site reliability30%
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 product team creates preview environments for pull requests. Forgotten environments accumulate cost, and shared test data leaks between reviews.
Setup prerequisites
- Author a local environment-provider double and synthetic pull-request events; provision no external resources.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BENV-101 · Define review-environment identity independently of branch names
- BENV-102 · Set per-environment and per-team resource ceilings
- BENV-103 · Create environments through idempotent provider operations
- BENV-104 · Seed synthetic review data in isolated namespaces
- BENV-105 · Bind preview URLs and callbacks to the environment origin
- BENV-106 · Expire environments using leases rather than event delivery alone
- BENV-107 · Reconcile partially created environments after provider failure
- BENV-108 · Produce a cleanup plan that proves exact resource ownership
- BENV-109 · Compare pooled and dedicated preview dependencies
Acceptance criteria
- Expose lifecycle state and last safe failure category.
- Show owner, expiry, and review identity.
- Document scoped retry and extension behavior.
Implementation constraints
- Status contains no credentials or seed data.
Verification to include
- Diagnose an expired synthetic preview.
- Reject extension after irreversible cleanup begins.
Deliverables
- Preview support guide.
Rollout and recovery
Ship with lifecycle controls and update after state changes.
Value of the work
For the engineer: Practice resource lifecycle state machines, isolation, and reconciliation.
For the team: Make review environments predictable, isolated, and accountable to a budget.
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.