NavMantra home / Resources
Field guide · DevOps
Release-readiness checklist for small application teams.
A repeatable release needs more than a successful build: ownership, configuration, observation, rollback, and recovery must also be clear.
Reviewed 2 August 2026 · NavMantra operating guidance
Before the release
- The exact source revision and dependency versions are known.
- Secrets and environment configuration are separated from code.
- Database changes have a reviewed forward and recovery path.
- The responsible person and approval boundary are explicit.
- A recent backup exists when the change can affect durable data.
During the release
- Deployment output is retained.
- Health checks cover the application and its critical dependencies.
- One person owns the go/no-go decision.
- Rollback criteria are defined before symptoms appear.
After the release
- The live route and a representative workflow are tested.
- Errors, latency, queues, and background workers are checked where applicable.
- The deployed revision is recorded.
- The runbook is updated when reality differed from the plan.
What “ready” means
Release readiness does not mean failure is impossible. It means the team can identify what changed, observe whether it works, stop when risk exceeds the agreed boundary, and restore service through a tested path.