A health number is only as good as the data behind it. Confidence Scoring tells you how much to trust each one, using a transparent rubric rather than a black box.
The rubric
Confidence is scored across eight criteria, including CI stability, deploy integration, clear ownership, dependency health, sync freshness, recent incidents, and the ratio of blocked work. The score is simply the number of criteria met out of eight.
It degrades honestly
When a signal is missing, the criterion is not silently skipped. It scores zero and records a reason, so the confidence number drops and tells you why. A low confidence score is a prompt to connect another integration, not a failure.
One reserved criterion
The Sentry error-spike criterion is a reserved slot. It is part of the rubric but currently always scores zero with an explanatory reason, pending Sentry ingestion into this path. We call that out rather than letting it look like a passing check.