Part 3 of Retrieval-Augmented Self-Recall. Code: RE-call. Part 2: hybrid retrieval on Postgres.
Ask your agent "have we tried this filter on this market before?" when the honest answer is never. A ranking retriever hands back the three closest memos anyway — something about a different filter, on a different market — and the agent, looking at three confident results, concludes: yes, we've looked at this.
It just made a decision on a hallucination. Nothing in the stack noticed. No error was raised, because from the retriever's point of view nothing went wrong: you asked for the nearest neighbours and it gave you the nearest neighbours.
Everything in Part 2 made retrieval good. Good ranking makes this failure worse, not better — it returns confident noise faster. This post is about making retrieval honest, which for agent memory is the part that actually decides whether you can trust it.
So RE-call wraps retrieval in honesty guards — this post covers the original three, each answering a question ranking metrics never ask. (The current repo has grown that table to six, and the growth story is its own post: two of the new guards exist because readers of Part 1 pointed at exactly the weaknesses you're about to see me describe. I'll flag those spots as we go.)
