rebuild-core-knowledge

To keep architecture documentation synchronized, rebuild core memory bank files in proper dependency order from foundation to current state, deriving systemPatterns.md directly from code and validating cross-file consistency.

The correct dependency order for rebuilding a memory bank starts by validating the foundation (projectbrief.md), then reconstructs architecture (systemPatterns.md), updates evolution, and finally generates a fresh activeContext.md.

Memory bank documentation drifts from implementation when foundation, architecture, evolution, and current state files are updated independently without cross-file consistency checks or team sign-offs enforcing coherence with the codebase.

Generate a fresh activeContext.md by first updating the projectbrief.md foundation, rebuilding the systemPatterns.md architecture from code, and updating evolution documents to ensure the active context reflects present reality accurately.

Yes, you can use team validation sign-offs alongside cross-file consistency checks to prevent documentation drift when rebuilding memory bank files, ensuring foundation and architecture documents stay aligned with the codebase.

Avoid dependency-aware documentation rebuilding workflows when your software project lacks a foundational projectbrief.md or when the codebase is too volatile for team validation sign-offs and cross-file consistency checks to yield stable architecture insights.