w1n5t0n/OptMem
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

note criteria: new + important + lasting, and never redundant

Browse source
This commit is contained in:
victortaelin 2026-07-25 17:53:22 -03:00
parent 1f1ec1511e
commit c08119e701
1 changed files with 12 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
README.md
View file

@ -123,11 +123,12 @@ yet the truth.
## Writing a good memory ## Writing a good memory
A note costs one future compression, so it is not free — but an unwritten Write one the moment something happens, you learn something, or something
memory is gone forever, which is far more expensive. Write one whenever changes — if and only if it is new to you, important, and lasting in effect: a
something is genuinely worth keeping: a fact or a ruling from the user, an task worth real effort, a fact or insight the user teaches you, anything you
insight, a decision, a piece of work landing, something that failed and why. learn about their life (even indirectly), work of yours that lands. Do not log
Do not log trivia, do not narrate your own process, and do not hoard. trivia, do not narrate your own process, and never write what you already
know: a redundant memory costs a compression and buys nothing.
Compress toward facts, not prose. Keep names, numbers, dates, paths, ids and Compress toward facts, not prose. Keep names, numbers, dates, paths, ids and
decisions; drop wording. decisions; drop wording.
@ -244,11 +245,12 @@ them and run `memo wake` again.
While you work: While you work:
- `memo note "<one line, max 280 chars>"` when the user gives you a fact or - `memo note "<one line, max 280 chars>"` the moment something happens, you
a ruling, you reach a real insight, a piece of work lands, or something learn something, or something changes -- if and only if it is new to you,
fails and you learn why. Skip trivia; each note costs a future important, and lasting in effect. That covers a task worth real effort, a
compression. Do not hoard either: an unwritten memory is lost. When fact or insight the user teaches you, anything you learn about their life
unsure, write it. (even indirectly), and work of yours that lands. Never write what you
already know: no redundant memories, ever.
- If `memo note` returns a compression, do it before your next action. - If `memo note` returns a compression, do it before your next action.
- `memo recall <regex>` when a memory is too vague. - `memo recall <regex>` when a memory is too vague.
- Before your context ends, run `memo sleep` and answer each prompt until - Before your context ends, run `memo sleep` and answer each prompt until