Command Explorer › mem: — the state the agent holds › fix
mem:fix
Correct an existing memory: replace old with new.
In the mem: domain
mem: — Save what this message designates, durably.mem:pin — Save it at special priority — pinned, load-bearing.mem:fix — Correct an existing memory: replace old with new.mem:recall — Answer from memory first, provenance shown.mem:forget — Remove the designated memory — guarded, confirmed.What it does
An existing memory is replaced by the corrected version you give — replaced, not appended, so the old version stops competing as fact.
The registry's own words: This message corrects an existing memory: replace the old version with this one, and confirm what changed.
Fire it — usage examples
“Correction — Ana spells it with one n now.
mem:fix/pi”→ the stored fact is replaced, marked pinned, and the reply confirms the change: old → new.
“My clinic moved me to Dr. Rao — update that.
mem:fi”→ the stored entry names Dr. Rao now, and the confirmation shows the old name replaced by the new one.
Said aloud: “Lingo, memory fix — one n in Ana.”
→ the correction applied and confirmed.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “memory fix” (also “correct”). Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent finds the entry the correction is about, replaces it, and confirms what changed. If no entry matches, it changes nothing and says so (and offers to save the content as new instead). If several could match, it names them and asks which — it never guess-replaces.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-mem-fix ↗.
When the host can't
No durable memory: apply the correction to session memory and disclose that scope. If no existing entry matches the correction, change nothing and say so plainly.
Conformance — “done when”
The prior entry is replaced by the corrected one and the change confirmed — or the no-match / ambiguity is reported with nothing changed.
Persistence class: content-write. Execution report in the reply: required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.