Tracing Knowledge Lineages

Trace knowledge lineages by searching decision records, git history, and team conversations to understand why previous approaches were rejected. This reveals whether past failures apply to your current context or if circumstances have changed, preventing duplicate effort and premature dismissal of viable solutions.

Git archaeology uncovers the original problems a system solved and alternatives that were already evaluated. Understanding this lineage ensures your proposal addresses historical challenges and doesn't reinvent rejected ideas without learning from their previous incarnations.

Revival detection traces whether a proposed approach has been attempted before by examining decision records, conversations, and commit history. This surfaces lessons from its previous lifecycle and prevents wasted effort on ideas already tested under different constraints.

Maintain decision records (ADRs or similar artifacts) alongside git commit messages and collaboration notes. Structured lineage evidence enables future teams to perform decision archaeology and understand the context, trade-offs, and alternatives evaluated when the original choice was made.

Yes. Git log with full history reveals when code was removed, but decision archaeology requires pairing commit history with decision records and conversations to surface the reasoning. Git alone shows what changed; lineage tracing explains why alternatives were rejected.

Re-evaluate when context shifts—team expertise, business priorities, dependencies, or scale change. Failed attempt analysis frames when to reconsider by distinguishing fundamental flaws from constraints that no longer apply, preventing both premature abandonment and repeating mistakes under identical conditions.