How should release approvals be designed for production?

For production, use approvals where risk justifies them, automate evidence collection, separate duties for sensitive environments, record who approved what, and avoid making routine low-risk releases depend on unnecessary manual gates. 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.