PR Degradation Rate
per Pillar
% of PRs evaluated that contain at least one failing Lens under a given pillar.
This page describes the intended design. No PR-to-Pillar degradation tracking exists yet. It doesn't appear on your dashboard yet, and no org currently has a live value for it.
÷ total PRs evaluated)
× 100
What it signals
PCR measures the pass rate of individual Lens evaluations. PDRP measures how broadly a pillar's failures are distributed across PRs. A high PDRP means many different contributors are diverging from this pillar's intent — not just one team failing repeatedly.
This distinction drives the remediation. If PDRP is high but failures are concentrated in a small set of teams, the problem is a one-team enablement gap. If PDRP is high and failures are spread across many teams and contributors, the problem is systemic — either a training gap, a tooling gap, or Lenses that no longer reflect the org's actual architectural intent.
A VP Eng asking "is this one team or everyone?" is asking the PDRP question. An architect asking "before I recalibrate these Lenses, how widely is this actually failing?" is also asking the PDRP question. PCR and PDRP together give both the rate and the reach of a pillar's conformance problems.
How rkito produces it
Who this metric is for
PDRP answers the first triage question after a pillar's PCR drops: is this concentrated in one team, or distributed across the org? Concentrated PDRP with low breadth points to an enablement problem with a known owner. Distributed PDRP points to systemic drift that requires a different response.
A low PCR with a high PDRP means failures are spread widely across contributors — which can indicate Lenses firing on benign patterns before it indicates teams failing at architecture. PDRP gives the architect the evidence to confirm whether a Lens recalibration is warranted before initiating a CHI.
How this metric gets misread
PDRP at >40% almost always indicates miscalibrated Lenses before it indicates teams that are fundamentally bad at architecture. A Lens that fires on benign code patterns generates high PDRP without reflecting real conformance problems — the broad distribution of failures across many different contributors is itself a signal that the Lens may be misfiring.
Before escalating high PDRP to engineering leadership: verify with the pillar owner that the Lenses are correctly scoped. A Lens that was accurate when authored may no longer reflect current architectural intent as the codebase evolves. Escalating a miscalibration problem as a team behaviour problem destroys trust in the governance system.
What to do at each threshold
Step-by-step response playbook for each signal state.
Pillar failures are contained. Fewer than one in five PRs is touching this pillar's intent. No immediate action required.
Monitor on a monthly cadence. Confirm the trend is stable or improving before standing down.
Failures are spreading. Identify whether this is a concentrated or distributed problem before choosing a response.
Navigate to /changecontrols/designaudits, filter by FAIL, identify which teams are submitting the failing PRs.
Failures concentrated in one team: run a targeted enablement session with that team and the pillar owner.
Failures distributed across many teams: initiate a Lens recalibration review with the pillar owner before assuming the problem is behavioural.
More than four in ten PRs are triggering failures under this pillar. Convene the pillar owner immediately — but diagnose before escalating.
Open each failing Lens at /steerings/lenses — determine if the prompt still accurately reflects current architectural intent.
Miscalibrated Lenses get updated via CHI. Do not escalate to engineering leadership until miscalibration has been ruled out.
Genuine drift confirmed: run an awareness campaign across contributing teams and escalate to engineering leadership with the audit evidence.
The pass rate of individual Lens evaluations under this pillar. PCR measures frequency; PDRP measures reach. Read them together.
The directional signal for a pillar over time. A rising PDRP with a negative PDT confirms the problem is worsening, not stabilising.
The org-level aggregate conformance score. A high PDRP on a major pillar will drag DCS down — PDRP is where you diagnose what DCS summarises.
Is your pillar drift concentrated or systemic?
rkito computes PDRP per pillar automatically from your first design audit. Know whether you have a team problem or a systemic one within minutes.