Ankur Kumar

85 of 100, ranked 1 of 3 people with a score, against a cohort median of 85. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 80 is behind, ≥ 85 is leading, and this person is in the middle 40% of people with a score this period. With every component at the cohort median this person would score 85; they score 85. No single component moves the score by as much as a point; the position comes from the spread across all of them, not from one weak term. 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 3 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 85 − 85 = 0, where 85 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: 3.1 hours tracked, 4 commits, 1,470 lines changed, 25.1% 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.

• ⚑ Only 3 people produced code this period — too few to rank against

  Rule: relative bands need at least 4 producing people — found 3.

  What it does not mean: The component scores are still measured. What is withheld is the comparison: with a cohort this small, "leading" and "behind" are noise wearing a number.

What they actually did

• ec2 ModifySecurityGroupRules×2 · 6 pts

CloudTrail records the API call, not the intent. It cannot tell a considered change from one corrected a minute later, and it retains 90 days — so an empty earlier period means “not retained”, never “nothing happened”.

No pull requests opened or merged by this person in this window.