Rishav Raj

70 of 100, ranked 10 of 15 people with a score, against a cohort median of 74. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 67 is behind, ≥ 75 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 80; they score 70. That difference is carried by change discipline (75 against a cohort median of 100, worth -7.1 points) and consistency (37 against a cohort median of 54, worth -3.2 points). 2 of 6 components (completed work, infrastructure) could not be measured at all, so the remaining weights were rescaled — this score rests on 63% 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 70 − 80 = -10, 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: 194.3 hours tracked, 15 commits, 42,096 lines changed, 40.9% activity, first-pass CI 0%. 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.

• ⚑ This score describes 38% of their recorded working time

  Rule: fires below 70% coverage with at least 20 tracked days — 10 of 26 days produced a commit, review, task or infrastructure change.

  What it does not mean: The other 16 days were worked and tracked, and produced nothing any connected system records. That is meetings, support, debugging, planning and infrastructure without an AWS account mapped — work this platform is blind to, not work that did not happen. It does not lower the score; it bounds what the score is about.