# Recovery ticket template

Open this as a **new** ticket when a production breaks partway through. Do not edit the
original production ticket in place: keep the incident record separate from the plan, and
link the two together.

```markdown
## Recovery for: <link to the original production ticket>

Production: <what is being produced, e.g. "long-form documentary, Kinoboard request 112">
Opened: <date>
Reason: <what triggered this ticket, e.g. "release date passed with nothing published">

## Step inventory

Total steps in the production graph: <N>

| Step ID | Type | Status | Notes |
|---|---|---|---|
| <id> | <e.g. ConcatVideo> | Done / Waiting / Failed | <why, if failed> |

## Failure summary

- <count> steps failed because <specific, verified cause>.
- <count> steps are blocked waiting on the failed steps above.
- <count> steps are blocked waiting on something outside the pipeline (quota, dependency).

## Dependencies

- <step or group> depends on <upstream step or external condition>.

## Retry scope

Steps to retry: <exact list, not "everything">
Steps to preserve untouched: <count, and why they are excluded from the retry>
Steps to wait on: <condition and expected resume trigger>

## Retry criterion

This recovery is considered resolved when:
- [ ] every step in the retry scope reaches Done
- [ ] the merge/assembly chain downstream of the retried steps completes
- [ ] the output passes the master QC checklist
- [ ] a human approval is recorded before publish
```

## Real example (redacted)

- Opened 17 August, one day after a release date passed with nothing published.
- Step inventory: roughly 300 steps across image generation, clip generation, a merge cascade,
  final assembly, quality gate, publish, and callback.
- Failure summary: 8 merge steps failed because of a clip orientation mismatch; 11 clips were
  blocked behind 11 failed images.
- Retry scope: 18 clips + 11 images. Preserved untouched: 89 clips + 107 images.
- Retry criterion: merge cascade complete, final assembly succeeds, output passes the master
  QC checklist, owner approves after watching the finished cut.
