What this measures
Work that leaves no trace in git.
Someone who spends a week keeping servers alive produces no commits and reads as idle everywhere else in this platform. CloudTrail is the only record that the work happened and who did it.
A CloudTrail write is not a unit of work, so events are weighted rather than counted. Signing in, changing your own password and opening a CloudShell terminal are all writes, and all score zero — presence is not delivery. Creating a load balancer and toggling a notification setting are both one row, and are not worth the same.
Only 90 days exist. No CloudTrail trail is configured on this account, so nothing before 2026-09-23 can ever be recovered. An empty period means “not retained”, never “nothing happened”.
Weighted points
3220
976 scoring changes
People
9
across 7 days
Concentration
46%
held by Harsh Patel
Bus factor
2
people holding 80% of it
Invisible to every other measure
Infrastructure work in this period, and no commits at all.
This is the question the AWS ingest was built to answer. Without it each of these people reads as having delivered nothing.
Ranking
Weighted by what each change did. infra-v1.
| # | Person | Points | Changes | Days | Mix | Services |
|---|---|---|---|---|---|---|
| 1 | Harsh Patel | 1468 | 431 | 4 | Provisioning 151Deployment 35Access & security 83Configuration 16210 unscored | acm amplify autoscaling cloudformation +7 |
| 2 | Pankaj Kumar | 1242 | 370 | 5 | Provisioning 130Deployment 26Access & security 60Configuration 1542 unscored | amplify iam route53 |
| 3 | Anshuman Parmar | 166 | 50 | 4 | Provisioning 17Deployment 6Access & security 3Configuration 244 unscored | autoscaling cloudformation ec2 elasticbeanstalk +2 |
| 4 | Ankur Kumar | 106 | 33 | 6 | Provisioning 5Access & security 25Configuration 34 unscored | ec2 |
| 5 | Aziz Bohra | 86 | 34 | 1 | Provisioning 6Configuration 285 unscored | route53 ses |
| 6 | Akash Kumar | 62 | 25 | 1 | Provisioning 4Configuration 211 unscored | q route53 ses |
| 7 | Rushendra Varma Mudunuru | 60 | 21 | 5 | Access & security 18Configuration 38 unscored | ec2 iam servicequotas support |
| 8 | Jitu Prosad Saha | 26 | 10 | 1 | Provisioning 2Configuration 8 | route53 ses |
| 9 | Rushikesh Powar | 4 | 2 | 2 | Configuration 2 | ec2 |
How a change is weighted
The whole formula.
Brought infrastructure into existence or removed it — stacks, instances, load balancers, databases, apps.
Shipped a change to a running environment — builds, releases, environment rebuilds.
Changed who or what can reach something — security groups, IAM policies, keys, bucket policies.
Tuned infrastructure that already existed — attributes, scaling settings, DNS records.
Signing in, securing your own login, opening a shell. Presence, not delivery — scored at zero.
Where the work happened
AWS services touched, by change count.