An era profile identifies who drove development and what kinds of work dominated a defined period, revealing both its contributors and its day-to-day character. section 6.4
Build a profile from compact raw evidence:
- Process one era at a time rather than overwhelming the context with every commit. section 6.4
- Provide one line per commit using month, author, scope, and subject. section 6.4
- Add five landmark diffs—the first, three period peaks, and the last—to test commit-message interpretations against code. section 6.4
- Let each era generate its own work buckets instead of forcing categories across unrelated periods. section 6.4
Contrasting eras
A product lifecycle may move from founder-led prototyping to maintaining a fading bet, a chaotic pivot, and mature distributed development; each period needs a different work vocabulary. section 6.4
Figure 6.6 The four eras of a product's lifecycle as seen in its commit history: founder-led prototyping, maintaining a fading bet, a chaotic pivot, and mature, distributed development.

Use the lifecycle figure to compare how contributor patterns and work moods change across eras. section 6.4
