# Write the rollback procedure and prove it on a preview environment

A rollback procedure that has actually been executed, not just written down and hoped for.

Category: Release, deploy, and environments
Source: https://letsship.ai/use-cases/prove-the-rollback-procedure
Published: 2026-08-25

## Goal

Write the rollback procedure and execute it against a preview environment.

## Acceptance criteria

- Every step is executed against a real environment and captured
- Time to roll back is measured
- Data migrations that cannot be reversed are called out with the alternative
- The procedure is linked from the deploy documentation

## What lands as proof

A captured execution against a real environment, with the elapsed time recorded.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Write and prove the rollback procedure

Description: Write the rollback procedure and execute it against a preview environment.

Acceptance criteria:
- Every step is executed against a real environment and captured
- Time to roll back is measured
- Data migrations that cannot be reversed are called out with the alternative
- The procedure is linked from the deploy documentation

Before you create the issue, check whether this repository has a written rollback procedure and whether anybody has run it.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: write the rollback procedure and execute it against a preview environment. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means the rollback executed and captured, not merely documented, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.