talk-stage2-research

To generate a verified timeline, cross-reference git archaeology metrics with changelog analysis and existing summaries. This aligns development velocity data across sources to produce a chronologically accurate narrative sequence.

Git archaeology extracts development velocity metrics by performing read-only analysis on repository commit history. It analyzes past development cycles to quantify output speed and patterns without modifying the original repository state.

Cross-referencing git commits with a changelog involves scanning documented release notes and aligning them with raw commit dates. This validates documented changes against actual repository history to ensure narrative accuracy.

This timeline analysis does not require write access because all git operations are strictly read-only. It extracts velocity metrics and generates external output files without modifying the underlying repository.

You need a Stage 1 summary path, a repository path for git access, and an optional changelog path. These inputs allow the analysis to align themes and historical data to build the verified timeline.

Combining git history and changelog analysis produces three distinct output files: git-archaeology.md, changelog-analysis.md, and timeline.md. These files provide verified metrics and sequences for downstream review.