memory-alignment-check

Checking implementation against project memory detects new patterns, decisions, or constraints introduced during development that are not yet present in memory. It identifies unaddressed memory items and contradictions, ensuring long-term project knowledge remains accurate after code delivery.

Run a memory consistency check immediately after a developer completes a Story and it passes QA. Activating the check at this stage ensures the new code aligns with established project patterns and decisions stored in memory before further development proceeds.

To identify new patterns and decisions missing from knowledge management memory, analyze implementation reports and selective memory entries. This comparison detects newly introduced constraints or decisions, extracting them for ingestion to update the long-term project context.

Memory alignment verification works without external dependencies, relying solely on internal references. It functions independently to analyze implementation footprints and selective memory entries, requiring only the completed Story's report and existing memory data to execute the consistency check.

A limitation of comparing implementation footprints against memory entries is that the analysis depth is intermediate, focusing on pattern, decision, and constraint detection. It relies on the accuracy of implementation reports and selective memory entries rather than scanning the entire codebase independently.