memory-alignment-check

Code verification against project memory involves analyzing modified files, new modules, and applied patterns against indexed long-term entries to report confirmations, contradictions, and new knowledge candidates.

Memory alignment checking is a post-QA verification process that ensures a completed story's implementation footprint matches established architectural decisions and patterns stored in long-term memory, preventing knowledge base drift.

Check for contradictions by running a memory alignment verification after QA passes, which compares specific implementation changes against relevant memory entries using scope tags to highlight discrepancies and new patterns.

You need to run a memory alignment check after a story's Quality Assurance passes, ensuring the newly implemented feature footprint is validated against existing indexed memory before finalizing the task.

Yes, memory alignment checking operates on specific artefact reports and selective memory entries based on scope tags, allowing targeted verification of relevant code patterns and technical decisions.

Automated memory consistency reporting relies on existing indexed memory entries and accurate scope tags to identify confirmations and contradictions, meaning unindexed or improperly tagged technical decisions may be missed during footprint analysis.