Memory

Every conversation starts from nothing unless something is carried across. Memory is that carry: a short list of durable facts about how you trade, so you are not restating your risk rules in every thread. It is on by default, and nothing lands in it unless you ask for it.

What a memory is

One sentence, up to 500 characters, filed under one of seven categories. It is deliberately small: a fact, not a transcript, and not a summary of a conversation.

• Instruments — what you trade.
• Strategies — the approaches you run.
• Risk and goals — your caps, your targets, the rules you set yourself.
• Habits — how you work — when you trade, how you review.
• Patterns — something about your trading that keeps recurring.
• Accounts — facts about the accounts you run and how you use them.
• Other — anything that fits none of the six above, kept rather than forced into one that nearly fits.

How something gets stored

By asking. Tell it to remember something and it writes one row and reports back what it did. Two phrasings of the same fact collapse into one — the check ignores casing and spacing — so telling it twice does not give you two copies, and it will say as much rather than pretending it stored something new.

Each row records where it came from and which turn wrote it, so “when did it learn that?” has an answer rather than a shrug.

Reading what it has

Type / in the chat composer and pick memory. On a signed-in surface that is a real read of your own store, not a canned reply: it either lists what is there, tells you nothing is saved yet, tells you memory is switched off, or says plainly that it could not read it. It shows up to eight facts and the count.

The ceiling

A hundred facts. When it is full, the next one is refused and you are told so — the oldest row is never quietly dropped to make space. Silent eviction would leave the count reading full forever while facts disappeared behind it, which is the worst possible behaviour for a store whose whole job is to be dependable.

Forgetting, and why it sticks

A forgotten memory is genuinely deleted rather than hidden — a filtered-out row is still a fact the system holds. What survives is a one-way fingerprint of the deleted text filed under its category, never a copy of the text itself, and that fingerprint is what stops the fact being learned again by accident.

That last part is a security property rather than a convenience. Intelligence reads text you did not write for it, so a stray sentence in a trade note could otherwise re-teach it something you deliberately removed. When it meets a fact you once deleted it skips it and moves on.

Switching memory off is built to stop it being read and to delete nothing: the facts stay where they are and come back when it is switched on again. The switch is the part that is not connected yet, which is why it will not move.

Where this stands today

The store, the categories, the ceiling and the deletion rules are all built and tested on the server. What is missing is the way in: nothing in the chat can forget a fact on your behalf, and the review-and-forget page in Settings is not connected to any of it yet. So treat memory as add-only from your side for now — it will keep what you ask it to keep, and the controls to prune that list are still to come.