# Durable memory

Use MEM for: fact/preference; why retention is useful; applicability; project/personal scope; source/date; confidence; visibility; approval state; supersession/rollback.

Example: “This workspace uses a flat neutral interface because the accepted design brief specifies it.” Source the approved brief and keep project scope. Do not turn that into a statement about every project or the owner's identity.

On recall report the record ref, status, scope and verification freshness. Use only applied/approved relevant entries. If a remembered provider version may have changed, label it stale until verified.

A historical run belongs in SES/LOG; a research conclusion in RDT; exact owner correction in FDK. Avoid keeping the same full transcript in MEM. Retention should have a reason beyond “might be useful.” Unknown/sensitive personal facts remain proposals and private-profile memory follows its separate approval process.