Repository snapshot and counting method
The figures in this series describe committed history in my independent game repository, inspected on November 4, 2026. The latest included commit is dated November 2. Uncommitted work and the separate assets repository are excluded.
| Endpoint comparison | Commits, including merges | Non-merge commits | Files changed between endpoints |
|---|---|---|---|
| February baseline to November 2 | 2,161 | 2,132 | 4,283 |
| July 15 endpoint to November 2 | 711 | 705 | 3,101 |
These are Git reachability and endpoint-diff measures. They include product code, tooling, documentation, experiments, and generated material. Files changed counts distinct paths in the endpoint comparison, not every file edit made along the way. The history includes multiple author identities and merges.
The fixed endpoints are:
1
2
3
February baseline: 7c88ac6c0523ae98108cc446a54c9536718c9a43
July endpoint: fbb3399dfa39bd5e4ed8f743e2c160e60925e092
November endpoint: 2729ecf785c6f944e09fbf83a9702b887d32d5d1
The February baseline is the selected commit preceding February 15. The July endpoint is the selected July 15 commit. For someone with access to the repository, these commands reproduce the primary counts:
1
2
3
git rev-list --count 7c88ac6c0523ae98108cc446a54c9536718c9a43..2729ecf785c6f944e09fbf83a9702b887d32d5d1
git rev-list --count --no-merges 7c88ac6c0523ae98108cc446a54c9536718c9a43..2729ecf785c6f944e09fbf83a9702b887d32d5d1
git diff --shortstat 7c88ac6c0523ae98108cc446a54c9536718c9a43 2729ecf785c6f944e09fbf83a9702b887d32d5d1
The repository is not presented here as a public dataset. The method is disclosed so the definitions are clear; public readers cannot independently inspect private history from these hashes alone.
These counts do not establish pull-request volume, test pass rates, releases, personal authorship of every change, customer impact, or a productivity multiplier. No employer operating metrics are included.
The historical examples in the essays concern the presence and evolution of tools and operating rules. They are not a claim that all historical changes passed every test or reached release quality.