Memory should hold lasting rules and terms, not every temporary project detail. When one-off notes become memory, old assumptions can influence new work long after they stopped applying.
Save durable tone, terminology, rules and templates; keep temporary facts in the current space or Scratch.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Decide which of these notes belongs in memory and which should remain only in the current project context.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to risk, review duty, privacy and later findability. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not store outdated project states as company-wide guidance.
Curated memory makes answers more consistent without making them heavier.