Command Explorer › mem: — the state the agent holds › save

mem: (bare)

Save what this message designates, durably.

Level 2Operation axisClass: actThe bare prefix is the directive itself — no command follows the colonRequires: persistent-memoryPersistence: content-writeConfirmation in the reply: required

Directive Shorthand 3.1 · Command explorer · Assembled from the canonical spec, registry, usage guide, and implementation guide — this page adds no meanings.

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

The fact, preference, or decision your message designates is saved into persistent memory, durably.

The registry's own words: The bare form: save what this message designates — the fact, preference, or decision it names — into persistent memory as durable, and confirm exactly what was saved, in this reply. The token is the domain prefix alone (zero letters past the prefix).

Fire it — usage examples

“My sister's name is Ana. mem:”

→ saved, and the reply confirms exactly what was saved: the stored statement itself.

Quote any earlier message of yours and add mem:

→ that message's content is what gets saved.

Said aloud: “Lingo, memory — my sister's name is Ana.”

→ saved, and the stored statement confirmed back to you.

Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “memory” (also “save”, “store”). Dictated directives fire deliberately, never by accident.

What the agent actually does

A write to the memory store: one durable statement of the content, attributed to you as its source, your meaning kept exact. Before writing, the agent checks for a directly contradictory existing memory; if one exists it stores nothing yet and reports the conflict (“I have X saved; this says Y — say mem:fix if you mean to correct it”).

The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-mem-save ↗.

When the host can't

No durable memory on this host: hold the content for the current session only and say plainly that it is session-only and will not survive the session. Never claim a durable save that did not happen.

Conformance — “done when”

The designated content is durably stored (or session-held with disclosure, or the conflict reported), and the reply confirms exactly what was saved.

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.