# Rollback decision card

## Trigger

- Affected release:
- Customer impact:
- Error/latency evidence:
- Decision owner:
- Why rollback is safer than forward recovery:

## Compatibility gate

- [ ] Previous artifact retained by digest
- [ ] Required binding and configuration schema available
- [ ] Database changes are backward compatible
- [ ] Messages and object formats remain readable
- [ ] External side effects have a compensation plan

## Restore

- Previous known-good release:
- Traffic strategy:
- Readiness check:
- Critical transaction check:

## Verify and preserve

- [ ] Runtime reports the restored release
- [ ] Customer-impact signal recovered
- [ ] Failed artifact and evidence retained
- [ ] Forward-recovery owner assigned
- [ ] Incident record updated