Define review-environment identity independently of branch names
Renamed branches orphan their original preview resources.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Lifecycle modeling
Estimated field mix
- Cloud infrastructure60%
- Platform engineering40%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Use stable repository and change identities.
- Keep branch names as mutable labels.
- Record owner and expiry explicitly.
Implementation constraints
- Use fictional repositories and no real webhook subscription.
Verification to include
- Rename a synthetic branch without creating another environment.
- Reject conflicting repository identity reuse.
Deliverables
- Environment identity model.
Rollout and recovery
Adopt identity recording before resource creation.
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.