Skip to main content

Changes with escaped quality issues

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.

Prototype calculation — no live telemetry. The synthetic example calculates this metric; it has no network collectors.

Accepted changes with at least one confirmed post-acceptance defect during approved follow-up, split by severity.

ContractDefinition
NumeratorDistinct eligible change_ids with one or more linked confirmed defects in follow-up
DenominatorAccepted change_ids with completed predeclared follow-up horizon
ExpressionN / D * 100
Aggregationpercent
Unit%
Eligible populationAccepted changes in acceptance window whose follow-up is complete by as_of.
ExclusionsImmature changes shown separately; duplicates/unconfirmed reports excluded but counted as pending triage.
Events and sourcechange.accepted; defect.confirmed; defect tracking and acceptance evidence
Owner / cadenceQuality Engineering / Monthly mature cohorts
Missing evidenceUnknown linkage is a coverage warning; no fabricated clean outcome. Show absolute defect and severe incident counts as well.
Gaming and limitsShorten follow-up or downgrade severity; freeze horizon and rubric and independently sample defects. Descriptive signal, not causal AI productivity attribution. Source completeness, task mix and sampling limit inference; report uncertainty. Counts affected changes, not raw defects per change; no presumption defects are AI-caused.

Read the shared collection and safeguards before collecting data; see the synthetic example and limits.

Return to Skills Measurement.