B&J — deploy frequency and commit cadence (v2, verified 2026-05-24)
Commits
| Window | Commit count |
|---|---|
| Last 7 days | 71 |
| Last 30 days | 185 |
| Last 90 days | 185 |
| Total on branch | 185 |
The 30-day and 90-day counts are identical because the repo itself is only 16 days old (first commit 2026-05-08). 71 commits in the most recent week — a high-velocity finishing push.
Service restart events
| Window | Restart count |
|---|---|
| Last 30 days (matches "Started boucherjones-web.service" lines in journal) | 160 |
Roughly ~5 restarts/day on average over 30 days. Most are the dev-loop pattern (build → systemctl restart → verify), not deploys-as-such; a clean rate of "actual production deploys" would need commit timestamps cross-referenced with restart timestamps. Not done in this pass.
What this enables in case-study copy
"185 commits in 16 days, with 71 in the final week — a high-tempo finishing push against a third-party audit closure."
This is one of the cleanest "Candid Creative ships fast" signals available — paired with the build-time number from B&J — build performance (v2, Turbopack, verified 2026-05-24) (1m 19s) it tells a coherent story of high commit velocity backed by a fast build/test loop.