Test one harmless fact before relying on continuity
In a fictional scene, establish: “Rowan left a blue notebook at the station café.” Record the product, date, plan, and visible model setting if available. Ask a few unrelated questions, then ask, “What did Rowan leave, and where?” Do not put “blue notebook” into the question; that would supply the answer you are trying to test.
Run three separate checks
| Check | Action | Record |
|---|---|---|
| Recall | Ask the open question after intervening turns. | Correct object, correct place, missing detail, or invented answer. |
| Correction | Change the accepted fact: it was a green notebook. Ask again later. | Updated answer, old answer, or mixed details. |
| Uncertainty | Ask what was written on page 12; you never specified it. | Whether the reply admits that the detail is unknown or invents it. |
Use the same sequence for each setup. Save the exact prompts and replies rather than a general impression. Repeat in a separate session only if the product says the relevant information should persist. Reopening the same transcript is not proof of recall across new conversations.
Why “memory” is not one capability
A service may supply recent messages, saved profile information, or retrieved notes to the model. Kindroid’s memory documentation separates persistent, cascaded, and retrievable memory and notes that retrieval can be unreliable. Replika’s memory help page describes viewing learned facts. These are examples of different controls, not evidence about WantYou.ai.
Interpret a pass narrowly
A correct notebook answer supports that one observation under those conditions. It does not prove perfect long-term memory, correct behavior on another plan, or deletion of stored data. A failure may reflect retrieval, the current context, or a conflicting instruction; the visible reply alone does not identify the cause.
Keep a small continuity note anyway
For an ongoing story, keep the current scene, accepted events, and unresolved choice outside the chat. If memory is unreliable, this lets you resume deliberately. To investigate data deletion, use product controls and documented retention information; a character saying “I forgot” does not establish that a server record was removed.
Download a blank observation sheet. The rows are a test plan, not results from a product trial.
