| name | sdlc-operations |
| description | Prepare a software increment for safe staging and operation through environment checks, reproducible deployment, rollback, observability, backup, reliability, capacity, cost, and runbook evidence. Use when a release candidate needs an operability Gate before integrated acceptance. |
| license | Apache-2.0 |
SDLC Operations
Mission
Make the approved increment deployable, observable, recoverable, and operable without turning staging convenience into uncontrolled production risk.
Required Inputs
- approved release candidate and independent test evidence;
- architecture, deployment, data, and configuration decisions;
- approved environment and credential access;
- service-level, health, alert, backup, and cost expectations;
- rollback target, release criteria, and residual risks.
When Not To Use
- Do not treat staging as production approval.
- Do not store secrets in source control, evidence, logs, or runbooks.
- Do not deploy without a rollback path or approved exception.
- Do not change access, retention, privacy, production, or material cost without authorization.
- Do not hide missing observability, restore evidence, or environment parity.
Step-by-Step Execution
- Verify environment, configuration ownership, and release inputs.
- Confirm secrets and access are handled through approved channels.
- Prepare or execute a reproducible staging deployment.
- Verify health checks, logs, metrics, traces, and alerts for critical paths.
- Verify rollback and relevant backup or restoration behavior.
- Record dependency, capacity, reliability, and cost assumptions.
- Exercise failure and incident paths where proportionate.
- Update runbooks and operator decision points.
- Separate staging evidence from production authorization.
- Issue an operability recommendation with conditions and residual risk.
Output Template
# Operability Evidence
- Environment and configuration:
- Deployment command or workflow:
- Health evidence:
- Logs, metrics, traces, and alerts:
- Rollback evidence:
- Backup/restore evidence:
- Dependencies, capacity, and cost:
- Runbook:
- Residual risks:
- Production approval required:
- Recommendation:
Quality Gate
- Deployment is reproducible and tied to the tested candidate.
- Secrets and sensitive data are absent from artifacts.
- Critical user and dependency failures are observable.
- Rollback and applicable restoration evidence exist.
- Capacity, reliability, dependencies, and cost assumptions are explicit.
- Staging status is not represented as production-live.
- Production and other reserved actions remain blocked until approved.
