memory-update

To update a changed fact across markdown memory files, you cascade the change by searching every relevant file, editing each matching reference consistently, and verifying no old values remain to eliminate stale or contradictory facts.

Keeping client status and pricing consistent in linked markdown documents requires cascading the changed detail across all memory files in one pass, then rechecking to confirm the old value no longer appears anywhere relevant.

You can verify no old references remain after editing memory files by rechecking the memory set post-edit to confirm fact consistency, ensuring outdated values are successfully eliminated from all relevant markdown documents.

You need to cascade updates across memory files when a repeated key detail changes, such as client status changes, pricing updates, shifted launch dates, or project state transitions from pending to closed.

This approach works for updating project state transitions by targeting memory registries and strategy notes together. It searches every linked markdown memory document to edit matching references, ensuring the new project state is reflected everywhere consistently.