Dhiraj Ambekar

74 of 100, ranked 12 of 15 people with a score, against a cohort median of 81. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 74 is behind, ≥ 83 is leading, and this person is in the bottom 30% of people with a score this period. With every component at the cohort median this person would score 80; they score 74. That difference is carried by craft (87 against a cohort median of 98, worth -3.9 points) and infrastructure (40 against a cohort median of 50, worth -2.1 points). 2 of 6 components (completed work, review) could not be measured at all, so the remaining weights were rescaled — this score rests on 70% of the intended evidence.

A band compares this person to the 15 people who have a score in this window — nothing more. It is not a rating, it does not persist, and it moves when the cohort or the window moves.

Effect is a counterfactual, not a share: how many points this person’s score would move if that one component dropped to the cohort median for it. The effects sum to 74 − 80 = -6, where 80 is what this person would score with every one of their components at the cohort median. Negative rows are the reason the total sits where it does. A component with no data is withheld and the remaining weights are rescaled — it is never scored as zero, and it never counts against anyone.

Measured but deliberately not scored: 41.3 hours tracked, 33 commits, 12,936 lines changed, 21.4% activity. The first four measure motion rather than delivery and are trivially inflated. CI is excluded because it exists on a minority of repositories, so scoring it would rank people by which repository they work in. This score cannot see architecture, planning, mentoring, incident response or infrastructure work at all.