How it worksVerified at 50d9f39

Memory and personalisation

For now the site remembers no visitor. The conversation lives in your browser tab and is gone when you close it. Memory comes later, off until you turn it on, as a few fields with no text in them.

Memory is the feature most likely to make an assistant useful and the one most likely to make it creepy. This site starts with none. When memory arrives it is small, opt-in and built so that it can only hold facts about which pages you opened, never a sentence and never a guess about who you are.

Nothing outlives the tab

On /ask, your browser keeps one entry in the tab's session storage. It holds the conversation, trimmed to the last 8 turns or 8 KB, and a random id that groups the turns of this conversation (ADR-0036). The id travels in the body of each request, not in a cookie, and it is not joined to anything. Close the tab and both are gone. Nothing recognises you on your next visit, so there is nothing to ask your consent for.

The server holds nothing between questions. Your browser sends the conversation it wants the assistant to see, and the agent forgets it when the answer ends (ADR-0035). If your browser blocks storage, the conversation simply does not survive moving between pages. Nothing breaks and nothing asks you to change the setting.

What adapts without memory

Some personalisation needs no memory at all (ADR-0044). The page and section you asked from are part of the question, so an ambiguous question is read in their light. How deep an answer goes is taken from the question itself and from the section it came from: a question asked from a design decision gets the reasoning. No profile of the reader is built for this, and none is guessed. Whether you are a recruiter, a CTO or a founder is never inferred into anything.

Memory, when it arrives

Cross-session memory is designed and not built. It comes with a later phase, and every part of it is opt-in.

  • Asked once, at the right moment. Not a banner on arrival. The assistant asks only inside a panel you opened, after two questions, once per visit (ADR-0048). Declining writes nothing.
  • An id that exists only after yes. A random id is created in your browser at the moment you agree and never before, and it travels in the request body, not a cookie (ADR-0045).
  • Six fields, no text. The pages you explored, as ids, at most 12; the sections you asked about, at most 3; a depth preference; how often the assistant may suggest things; whether you opened the contact form; the first and last day you were seen, as dates (ADR-0046). Every value is an id from the site or a value from a fixed list, so memory cannot carry an injected instruction because it has nowhere to put one.
  • Interests are worked out, never stored. A subject counts as an interest only when at least two pages you opened belong to it, and interests are listed alphabetically, never ranked. They are recomputed every time they are read, so there is nothing to go stale.
  • One writer, no model. Only your browser writes the record, once per visit, and the server checks it against the schema. No model reads or writes memory, and the assistant has no memory tool (ADR-0047).
  • See it, reset it, delete it. The memory view shows the record itself. Delete removes the record and the id at once and leaves no trace to restore. How long a record is kept will be on the privacy page from the day memory exists.

Memory speaks about subjects, never about behaviour. "You were interested in how accreta handles provenance" is allowed. "You've visited this page three times" is not. The difference between useful and creepy is grammatical, so it is a rule the copy can be checked against.

Why the profile is so thin

A ranked interest profile was measured before it was rejected (deep-dive 6). Over every possible visit to the pages that carry skills, the top-ranked category came out as backend or agentic delivery for 72.5% to 79.2% of visits, depending on how many pages were opened. That describes the portfolio's shape, not the visitor. Correcting for how common each category is only handed the win to whatever was rarest. The unranked set with a two-page threshold is the only version that says something about you without inventing it, and for a short visit it correctly says nothing.

Memory also changes little on the page. Static pages are the same for everyone when they load, so anything reordered afterwards would shift the layout under you. Suggestions may be reordered. A list on a page is reordered only when it can be done without visible movement, and on the markup designed so far no list qualifies (ADR-0049).

Memory and analytics are kept apart. The record of each question has no memory id and no field that could be joined to one (ADR-0056), so a deleted memory leaves nothing behind in the numbers.

How far this has been proved

  • Designed: no memory of any visitor in the first phase. Nothing is stored beyond the tab.
  • Designed, not built: everything under "Memory, when it arrives".
  • Measured: the interest profile above, over the site's own content, and the size of a full memory record as the assistant would read it, 173 tokens against a budget of 200.