For the specific conflicts your store surfaces, before you hard-code a global rule.
My memory store has two conflicting facts about the same entity: [fact A, with date] and [fact B, with date]. Propose a resolution strategy (recency-wins, confidence-wins, ask-user, keep-both-with-provenance) and justify which fits this case.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.