Deployment frequency
Target operating model — recommended contracts, not installed collection. All owner and cadence entries below are proposals to confirm before the pilot, not assigned responsibilities or approved schedules.
Unimplemented metric — no live telemetry. This is a prospective contract, not an implemented calculation or collector.
Distinct successful logical production deployments per complete service-day of observation.
| Contract | Definition |
|---|---|
| Numerator | Distinct service_id+deployment_id successful production deployments in window |
| Denominator | Observed service-days in window |
| Expression | N / D |
| Aggregation | ratio |
| Unit | deployments/service-day |
| Eligible population | Declared production services and complete UTC observation days; report each service before pooled views. |
| Exclusions | Test/staging, failed attempts without production effect, duplicate callbacks and retries of the same rollout. |
| Events and source | deployment.completed; authoritative deployment service |
| Owner / cadence | Platform & IT / Weekly per service |
| Missing evidence | Missing feed periods not zero; report coverage and no unqualified overall rate when period incomplete. |
| Gaming and limits | Split deployments without value; pair with success, rework and failure measures. Descriptive signal, not causal AI productivity attribution. Source completeness, task mix and sampling limit inference; report uncertainty. More deployments alone do not establish better performance; affected unsuccessful changes remain in change-fail population. |
Read the shared collection and safeguards before collecting data; see the synthetic example and limits.
Return to Skills Measurement.