Commit volume counts commits recorded for a project or development period. Read it as a clue to activity, not a standalone measure of health: rising, falling, and plateauing patterns need context. section 6.3
Use commit volume to ask sharper historical questions:
- Compare volume across development eras to identify stalled bets, successful pivots, and mature maintenance. section 6.3
- Compare volume before and after a product pivot to test whether activity surged or faded. section 6.3
- Pair volume with version-tag counts to distinguish continuous delivery from irregular release bursts. section 6.3
Ghost's activity arc
Ghost's eras contain approximately 8,000, 5,000, 17,000, and 15,000 commits. The dip suggests a stalled platform bet, the surge follows the memberships pivot, and the plateau indicates maturity rather than decline. section 6.3
