Production hotfix
Prioritize containment, predictability, backward compatibility, observability, and rollback/roll-forward safety.
- Establish production symptom, severity, affected scope, recent changes, and trustworthy evidence. Avoid speculative edits under urgency.
- Trace the narrow failing path and confirm root cause or the safest defensible mitigation.
- Choose the smallest localized change. Preserve contracts and defaults; avoid redesign, broad dependency upgrades, formatting, and unrelated refactoring.
- Add a focused regression test when practical. Validate the failing scenario and a representative unaffected path.
- Review configuration/migration/deployment ordering and rollback implications. Ensure logs/metrics can confirm recovery without exposing sensitive data.
- Inspect the complete diff and report residual risk and any validation that production conditions prevented.
Urgency changes breadth and speed, not safety. A temporary mitigation must be clearly identified, bounded, and not silently presented as a permanent design.