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-21 can ever be recovered. An empty period means “not retained”, never “nothing happened”.
Weighted points
4501
1413 scoring changes
People
11
across 7 days
Concentration
50%
held by Pankaj Kumar
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 | Pankaj Kumar | 2253 | 710 | 7 | Provisioning 211Deployment 37Access & security 126Configuration 3365 unscored | amplify cloudfront iam route53 |
| 2 | Harsh Patel | 1706 | 507 | 6 | Provisioning 161Deployment 42Access & security 125Configuration 17916 unscored | acm amplify autoscaling cloudformation +7 |
| 3 | Aziz Bohra | 181 | 74 | 2 | Provisioning 11Configuration 637 unscored | route53 ses |
| 4 | Ankur Kumar | 114 | 36 | 6 | Provisioning 5Access & security 27Configuration 44 unscored | ec2 route53 |
| 5 | Anshuman Parmar | 89 | 26 | 3 | Provisioning 10Deployment 2Access & security 3Configuration 114 unscored | autoscaling cloudformation ec2 elasticbeanstalk +1 |
| 6 | Akash Kumar | 62 | 25 | 1 | Provisioning 4Configuration 211 unscored | q route53 ses |
| 7 | Rushendra Varma Mudunuru | 45 | 16 | 4 | Access & security 13Configuration 310 unscored | ec2 iam servicequotas support |
| 8 | Jitu Prosad Saha | 26 | 10 | 1 | Provisioning 2Configuration 8 | route53 ses |
| 9 | Rushikesh Powar | 13 | 5 | 3 | Provisioning 1Configuration 4 | ec2 s3 |
| 10 | Dhiraj Ambekar | 12 | 4 | 1 | Deployment 2Configuration 22 unscored | autoscaling cloudformation elasticbeanstalk |
| 11 | Pranav Ojha | 0 | 0 | 1 | 2 unscored |
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.