revise-memory-bank

Memory-bank documentation revisions can be tracked using structured evolution patterns that preserve original reasoning and provenance. This approach systematically updates decisions, assumptions, and constraints while documenting how project understanding shifts over time.

Documenting cascading impacts across memory-bank files requires linking revisions to source decisions and tracking changes across related artifacts like systemPatterns.md and techContext.md. This structured approach ensures traceability and produces auditable artifacts suitable for governance reviews.

Applying decision revision and assumption tracking patterns involves providing a step-by-step revision narrative following the Evolution Documentation pattern. This updates memory-bank files like activeContext.md and progress.md with structured provenance for each change.

Structured change-control artifacts can manage memory-bank evolution by applying systematic revision patterns for decisions, constraints, and impact analysis. This produces auditable documentation suitable for governance reviews and knowledge transfer.

Memory-bank revision management works without external dependencies by applying built-in evolution tracking patterns directly to markdown files. It systematically updates project context artifacts using prescribed templates to ensure traceable changes.

Evolution documentation patterns should be used when memory-bank updates involve complex decision revisions, constraint updates, or cascading impacts. They ensure original reasoning is preserved and changes across files like productContext.md remain auditable over time.