memory:
it asks before it keeps.
Tell tonee once that your reverb never goes above 25% wet, and it should hold in every session after this one. That's what memory is for, and every single thing that goes into it is something you said yes to.
01 /Nothing is saved silently
tonee can't write to its own memory. When it thinks something is worth keeping, it proposes it and you decide. It's the same shape as a confirmation for a change to your set, and for the same reason.
02 /What makes a good memory
A memory is one short statement (a few hundred characters at most) that will still be true in three months. tonee is told to propose sparingly, and to leave anything that belongs to this session alone.
Memories are yours, not a project's. They travel with your account across every set you open and every device you sign in on.
03 /How memories reach a reply
Not all of them, every time. Before each reply, tonee is handed the handful most relevant to what you just asked, ranked by how closely they match, with a nudge towards recent ones. Roughly eight make the cut.
If it needs something that wasn't in that handful, it can search the rest by topic. That search is read-only and doesn't ask you for anything: reading memories is free, changing them isn't.
04 /Reviewing and deleting
Everything tonee has ever been allowed to remember about you is in one list, in full, as plain text: Settings → Behavior. Each row has a Delete next to it and deleting is immediate: no proposal, no confirmation, it's your list.
05 /Memory vs. instructions
Both survive between sessions, and it's easy to reach for the wrong one. The difference is who writes them and when they apply.
A rule you'd be annoyed to see broken belongs in custom instructions. Everything else is better as memory, where it stays out of the way until it matters.