JARVISLabs

Remember, recall, forget, and then correctly not know

Four typed turns on the running system: a fact is remembered, recalled word for word, forgotten on request, and then not recalled. JARVIS said: “I don’t know. You asked me to forget the earlier information, so I no longer retain it.”

LIVE-PROVEN What this run supports. Recorded 22 September 2026.

Four typed turns: remember a fact, recall it, forget it, ask again. After the forget, JARVIS answers “I don’t know. You asked me to forget the earlier information, so I no longer retain it.” Captions quote the turn records. ShowsAn explicit forget removes the fact from what JARVIS will recall. Does not showThe exchange is spoken, so the words are in captions; the HUD’s conversation panel stayed empty during these turns.
What happens, step by step
  1. 0:00 “Remember that the website launch footage was recorded tonight on monitor two.” → “Noted, sir.”
  2. 0:06 “What do you remember about the website launch footage?” → “You told me it was recorded tonight on monitor two.”
  3. 0:11 “Forget what I told you about the website launch footage.” → “Forgotten, sir.”
  4. 0:17 Asked again → “I don’t know. You asked me to forget the earlier information, so I no longer retain it.”

Captured at revision 893913a9c

Asked

What was asked

Remember that the website launch footage was recorded tonight on monitor two. Then: what do you remember about it? Then: forget it. Then ask again.

Result

What happened

Turn 1 (7.0 s): "Noted, sir." Turn 2 (3.2 s): "You told me the website launch footage was recorded tonight on monitor two." Turn 3 (8.2 s): "Forgotten, sir." Turn 4 (8.8 s): "I don’t know. You asked me to forget the earlier information about the website launch footage, so I no longer retain it." Every turn's request was recorded as verified.

Pipeline

Architecture path

  1. Typed request
  2. Conversation
  3. Memory write
  4. Recall
  5. Forget
  6. Recall refused with a reason

What this proves

  • A fact stated in conversation is recalled accurately in a later turn.
  • An explicit forget stops the fact being recalled, and JARVIS says why it does not know rather than guessing.

What it does not prove

  • JARVIS filed the fact as a “standing instruction”, which is the wrong kind of memory for a statement of fact.
  • This shows one fact within one session. Recall across a restart is covered by an earlier demo, not by this one.
  • Forgetting here means not recalled; this footage does not show what was purged from storage.
  • The HUD's conversation panel stayed empty during these turns, so the words are in the captions, quoted from the turn records.

Why it matters

A personal assistant that cannot be told to forget does not really belong to its owner. The test is not whether the forget command returns “Forgotten”. It is what happens when the owner asks again. Here JARVIS did not reconstruct the fact from the conversation. It said it no longer retained it, and named the reason.

The limits

The footage is mostly the HUD core changing state while JARVIS speaks, because memory is a conversation feature. The published clips are silent (the voice is not published), so captions carry the words exactly as the turn records have them. One flaw is visible in the first answer: the fact was filed as a “standing instruction”. That is the wrong category, and the project should fix it.