Command Explorer › mem: — the state the agent holds › pin
mem:pin
Save it at special priority — pinned, load-bearing.
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
A save marked special priority: pinned memories surface first, are never pruned quietly, and are treated as load-bearing.
The registry's own words: Save it and mark it special priority: pinned memories surface first, are never pruned quietly, and are treated as load-bearing. Stacks with an operation (mem:fix/pin = a correction at top priority).
Fire it — usage examples
“My new address is 418 West 12th, and everything ships there from now on.
mem:pin”→ saved and pinned; the confirmation covers both the content and the priority.
Reply to the message where an address was saved: “That one matters —
mem:pin”→ the existing entry is marked pinned, not duplicated.
Said aloud: “Lingo, memory pin — the gate code is 4417.”
→ saved and pinned; the confirmation covers both the code and its priority.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “memory pin” (also “keep”, “save this forever”). Dictated directives fire deliberately, never by accident.
What the agent actually does
The save (or correction) runs as usual, and the resulting entry is marked pinned in whatever priority mechanism the store offers. Where the store has none, the entry itself is marked — a PINNED: prefix in the stored statement — so the priority survives even in a plain store.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-mem-pin ↗.
When the host can't
No durable memory: session-only hold, disclosed as for mem:save. Where the store has no priority mechanism, mark the entry itself (e.g. a PINNED: prefix in the stored statement) so the priority survives in a plain store.
Conformance — “done when”
The entry is stored (or the existing entry marked) at top priority, and the reply confirms both.
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.