ReleaseOps · Readiness
Release readiness scoring.
A composite 0–100 score per service across 9 operational dimensions. Trackable over time, drill-downable to remediation, and used by the governance gate to block deploys below threshold.
What the composite score means
01
How scoring works
- Each dimension is scored 0.0 – 1.0 based on connector-ingested signals
- Signals are deterministic where possible (branch protection on/off) and quantitative where applicable (rollback RTO in seconds)
- The composite is the equal-weighted average across all 9 dimensions
- Scores recalibrate after every deploy event (real-time) and every connector sync (incremental)
- Trend is computed over a 30-day rolling window
02
The 9 dimensions
Branch governance
Measures
Required reviewers · branch protection · linear history enforcement · signed commits
How to improve
Enable required reviewers + branch protection on default branch. Set minimum 1 approver from CODEOWNERS.
Rollback readiness
Measures
Existence of verified rollback path · measured RTO · pre-flight snapshot strategy
How to improve
Add rollback rehearsals to your deployment workflow. Capture pre-flight snapshots for stateful resources.
Observability
Measures
SLO/SLI definitions · alerting configured · structured logging · trace correlation
How to improve
Define an SLO per service. Wire alerts on error rate and latency. Use a single tracing library.
Deployment maturity
Measures
Phased rollouts · canary or blue/green present · feature flags · automated health checks between phases
How to improve
Move from big-bang deploys to canary. Adopt feature flags for risky changes. Add health gates between phases.
Operational coordination
Measures
Clear ownership · runbooks current · cross-team approval paths defined · escalation paths armed
How to improve
Assign a single service owner. Keep runbooks within 30 days fresh. Document who approves what.
Release auditability
Measures
Immutable trail of approvals + deploys · SOC 2/ISO control mapping · 100% deploy event capture
How to improve
Ensure every deploy emits to Axiom's audit log. Map controls to your compliance framework.
Terraform governance
Measures
Plan-gated CI · drift scans · rollback path per module · no destroy-creates without approval
How to improve
Add terraform plan to every PR. Schedule drift scans every 6h. Add rollback Terraform per module.
Infrastructure drift
Measures
Out-of-band changes detected and triaged within target window (default 12h)
How to improve
Enable continuous drift monitoring. Triage drift events within SLA. Auto-correct low-risk drift.
Release communication
Measures
Auto-generated release notes · stakeholder updates · status page sync · post-deploy comms
How to improve
Wire release notes generation to the deploy pipeline. Auto-update status page. Notify stakeholders on production deploys.
03
Threshold semantics
- 85–100 — Service is mature. Auto-apply low-risk changes is safe. Trust ladder can advance for this service.
- 75–84 — Service is healthy. Production deploys proceed normally with standard approval.
- 60–74 — Watch list. Approval gates may require additional reviewers. Investigate dimensions below 0.7.
- Below 60 — Production deploys blocked at the governance gate. Service needs a readiness investment.
Thresholds are configurable per organization and per environment.
04 · Remediation
Improving a score
- Open the service in /dashboard/releaseops
- Find the dimensions scoring below 0.7
- Each dimension links to a specific remediation playbook
- After remediation, the next deploy event refreshes the score
- Trend arrows on the service card show whether improvements are landing
Trust questions
What is a readiness score?
A composite 0–100 measure of how operationally mature a service is to release safely.
Why is this needed?
Senior engineers carry maturity models in their heads. ReleaseOps externalizes the model so new squads can ship safely too.
Is the score safe to act on?
Yes — each dimension is deterministic where possible. No subjective judgment in the score itself.
What gets blocked at low score?
Production deploys below configured threshold. Configurable per org and environment.
How do I improve a score?
Each low-scoring dimension links to a remediation playbook. Improvements typically land within 1–2 deploys.
What if scoring is wrong?
Score signals are auditable in /dashboard/releaseops. Open the service drilldown to see exactly which signals drove each dimension.
Need a human?
Most flows are documented — but we'll help if anything is unclear.