Inspect & edit

Memory is yours to see and overrule — by hand in the app, or programmatically.

Salience is a good default, not a verdict. Every keyword is visible and editable. Pinning by hand is identical to reinforcing by repetition — it just skips the wait; forgetting is immediate and final.

In the app

Under Memory, the keywords are listed by tier — pinned, fading (with days remaining), and recently dropped. From there you can pin a fading item, forget anything, or promote a one-off before its timer runs out.

From the CLI

shell

yuzu memory ls              # all keywords, by tier
yuzu memory ls --fading     # only what's on a timer
yuzu memory pin "I trade on Base only"
yuzu memory forget "liked the frost tone"
yuzu memory show "promise:base"  # notes under one keyword

From the API

Call	Does
GET /v1/memory	Lists keywords with tier, weight, and days remaining.
POST /v1/memory/pin	Pins a keyword. Body: `{ "key": "…" }`. Idempotent.
DELETE /v1/memory/{key}	Forgets immediately. Cannot be undone.

Full schemas in API · Memory & wallet.

Patterns worth knowing

Seed at raise time.The founding instruction is the first pin. Add a few more ("always-remember" list) in Preferences rather than waiting for repetition.
Forget > correct. If a wrong fact pinned, forgetting the keyword is cleaner than arguing it into a contradiction.
Audit before automations. A standing intent acts on memory; glance at memory ls before handing it real money — see Standing intents.

Editing memory is the one place you reach inside the presence directly. It is also the fastest way to fix a presence that has "learned" something you didn't mean — sooner than waiting seven days for it to fade.