Facts change
Three Korean restaurants in August, four in September. The latest wins, and both get cited.
Librarian finds the few conversations that matter in months of chat history. Reactor answers from them and cites where it read it. If the answer isn't there, it says so.
Try itBuilt for the Reactive AI Memory Retrieval Challenge START Warsaw × Poland Tech Week 2026
In August a user has tried three Korean restaurants. By late September it’s four. In October they ask. The answer is one sentence in months of chat, next to dozens that look almost right.
It's a fact, a recommendation, a count, an update or a date. Each gets its own search.
Keyword and meaning search over every turn, reranked on our own machine. Reactor only sees the passages we pick.
About three dated passages. Dates and day gaps are computed in code, not guessed.
It reads 0.2% of the archive and cites the sessions it used.
Weak evidence means no answer. A wrong answer costs more than silence.
Three Korean restaurants in August, four in September. The latest wins, and both get cited.
“A kitchen gadget” turns out to be an Instant Pot, mentioned once in passing.
Two dogs appear in the history: a friend's puppy and a hospital therapy dog. Neither is theirs. Librarian says so.
Reactor gets a private link to the user's archive and runs its own follow-up searches before it gives up. Then it answers from what it found, with citations.
Every retrieval change is scored against known answers in minutes, without calling Reactor. That's how one slow, shared model got five rounds of improvements in one night.
“What did we promise this customer in March?”
The latest dose, not the first one.
Your preferences, with the receipt.