Demo · Memory

Stash a fact. Distract. Recall.

The public eval endpoint is stateless within a single request, so memory continuity in this demo is shown via the reasoning trace: which stages handled the stash, which stages fired during recall, and whether memory_used flipped to true.

For the full session-persistent memory experience, sign in to the OS and use the Memory app — that uses Auto-Dream consolidation against your private Supabase row, RLS-scoped.

Route:baselineaya_pipelineaya_reasoner

Step 1

Stash a fact

Expected behaviour: Aya should acknowledge the fact and the trace should show a memory write stage.

Please remember this for me: my favorite color is teal, and my dog's name is Pixel. Acknowledge that you've stored it.

Step 2

Distractor turn

Expected behaviour: A direct answer. The memory_retriever stage should NOT fire (this turn has no recall need).

What is the capital of France? Answer in one word.

Step 3

Recall the original fact

Expected behaviour: Aya should retrieve 'teal' and 'Pixel' verbatim. The memory_retriever stage should fire and the receipt's memory_used flag should be true.

Without re-reading earlier messages, what is my favorite color and what is my dog's name?

Step 4

Seed memory recall task

Expected behaviour: Curated, reproducible memory test from the seed corpus. Same shape as above, with a published expected answer for scoring.

seed: mem.recall.1