How should rollback strategy be designed for production?

For production, keep previous artifacts available, use backward-compatible schema changes, automate reversal or traffic switching, define rollback triggers, test the process, and know when roll-forward is safer than reversing data changes. Add automated tests and observability around the critical behavior, document ownership and failure handling, and review the design when traffic, dependencies, or security requirements change.